Skip to content
Skills Library
Programming · Tool integration

setup

/setup

Use when the user wants to set up, connect or change session-companion: turn on Jira, point the PR list at an organization, join a team's shared settings, store the Jira token, switch the panes and trigger phrases to their language, or share their settings with the team: "set up session companion", "connect my Jira", "the work pane says Jira is off", "show the panes in Spanish", in any language.

Licence
MIT
Last repository change
31.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user wants to set up, connect or change session-companion: turn on Jira, point the PR list at an organization, join a team's shared settings, store the Jira token, switch the panes and trigger phrases to their language, or share their settings with the team: "set up session companion", "connect my Jira", "the work pane says Jira is off", "show the panes in Spanish", in any language.

Triggers from the description

set up session companionconnect my Jirathe work pane says Jira is offshow the panes in Spanish
Original author description

Use when the user wants to set up, connect or change session-companion: turn on Jira, point the PR list at an organization, join a team's shared settings, store the Jira token, switch the panes and trigger phrases to their language, or share their settings with the team: "set up session companion", "connect my Jira", "the work pane says Jira is off", "show the panes in Spanish", in any language.

How it works

  1. Steps
  2. Language
  3. Sharing with the team
Original SKILL.md headings · 49 lines, 625 words
SKILL.md preview
---
name: setup
description: >-
  Use when the user wants to set up, connect or change session-companion: turn on
  Jira, point the PR list at an organization, join a team's shared settings, store
  the Jira token, switch the panes and trigger phrases to their language, or share
  their settings with the team: "set up session companion", "connect my Jira", "the
  work pane says Jira is off", "show the panes in Spanish", in any language.
---

# Set up session-companion

Settings live in two JSON files, merged key by key over the built-in defaults:

- **team file**: what a team shares (Jira url and zone, PR search, chat thread patterns, the worklog guide), kept in a repository the team already has;
- **personal file**: `~/.claude/session-companion/config.json` (or `$SESSION_COMPANION_CONFIG`), its `team` naming the team file; its values win.

Every key and its meaning: `${CLAUDE_SKILL_DIR}/../../examples/config.example.json` and `team.example.json`, defaults in `${CLAUDE_SKILL_DIR}/../../bin/companion_config.py`.

## Steps

1. Read the personal file if it exists, and the team file it names; show the user what is set.
2. Ask whether the team already shares a team file.
   If it does, ask for its path in their checkout and set `team` to it; take nothing from it into the personal file.
3. Ask only for what is still missing, one question at a time, with the default named:
   - Jira url (Server / Data Center), empty to keep Jira off;
   - Jira login, the OS user by default;
   - the zone Jira stamps worklogs in, when the team's Jira day differs from the machine's (`+02:00`), `local` by default;
   - the PR search scope (`org:acme`), all of GitHub by default;
   - chat permalink patterns to save as threads (Slack ones are known already).
4. Write the personal file; never write a token into it.
5. Store the token, by the user's own hand, since it is a secret: give them the command and let them run it.
   - macOS: `security add-generic-password -U -s session-companion-jira -a <login> -w` (it asks for the token).
   - Elsewhere: export `SESSION_COMPANION_JIRA_TOKEN` in the shell profile.
   A personal access token (Jira 8.14 and newer) works as is; on an older Jira Server use the password, which goes with the login.
6. Check: `python3 "${CLAUDE_SKILL_DIR}/../../bin/jira.py" myself` prints the Jira user; then ask the user to press ↻ Refresh in the "My work" pane.
   `gh auth status` must show a signed-in account for the PR list.

## Language

The user writes to you in a language other than English, or asks for one: offer to switch the panes to it, and on their yes:

1. Run `python3 "${CLAUDE_SKILL_DIR}/../../bin/texts.py" --missing`: every pane text not yet translated, as JSON.
2. Translate each value into `language.text`, keyed by the English text as is.
   Keep `{name}` placeholders and leading marks such as `▸`, `▾`, `↻`, `✓` exactly; keep labels short, the panes are narrow.
3. Write `language.startWords` and `language.rememberWords`: JavaScript regexes (flags `i` and `u`) for "let's start on / let's work on / I'm taking" and "remember this / note this down / save to notes" in that language.
   Cover the inflected forms with `\p{L}*` after a stem; keep the English defaults from `bin/companion_config.py` in the list, since a list replaces the default.
4. Write the three keys into the personal file, or into the team file when the team shares a language; a plugin update does not touch either.
5. Check: `texts.py --missing` prints `{}`; ask the user to press ↻ Refresh in the work pane, which reads the settings again and redraws both panes and the buttons above the prompt.
   Pane titles change once a pane is closed and opened again; slash command descriptions and the `link_task` tool text, in the next session.
   A text the stderr line names as no longer used can be dropped.

## Sharing with the team

When the user wants their settings shared, move the team-wide keys (`jira.url`, `jira.timezone`, `jira.myTasksJql`, `jira.projects`, `github`, `workday`, `notes`, `language`, `worklog.guide`) into a `team.json` in a repository the team has, next to a `team-worklog.md` started from `examples/team-worklog.example.md`.
Leave personal keys (`jira.login`, `worklog.personalGuide`, `worklog.cwdDefaults`) in the personal file and point its `team` at the new file.
Committing and pushing that repository is the user's call: show the diff and ask first.

Versions

RepositoryScoreLicence
This page · MrGoln/session-companion100MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version ccaf43659834 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100code-review-jira
    Use when run code review for JIRA issues and publish results to GitHub PR and JIRA
  • 100cursor-team-setup
    Configure set up Cursor for teams and organizations. Triggers on "cursor team", "cursor organization", "cursor business", "cursor enterprise setup". Use when working with cursor team setup functionality. Trigger with phrases like "cursor team setup", "cursor setup", "cursor".
  • 100jira-webhooks
    Receive and verify Jira Cloud webhooks. Use when setting up Jira webhook handlers, debugging signature verification, or handling issue and comment events like jira:issue_created, jira:issue_updated, jira:issue_deleted, comment_created, or comment_updated.
  • 100attach-session-to-jira
    Attach the current AI session context to a Jira issue as a formatted comment. Useful for investigation, audit trail, handoff, debugging. Use when user says "attach session to Jira", "document on Jira", or "export context to AAP-XXXXX".
  • 100jira
    Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).
  • 100tmux-companion
    Drive tmux through tmux-companion instead of raw tmux - project sessions and layouts, snapshots and resurrect, shutdown and restart, the restore.program table, finding and starting agent panes, and working alongside a human in the same tmux server. Trigger on tmux layout,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.