Update to Atlassian Teamwork Graph CLI
Snapshot Oct 24, 2026 · 13:12 UTC · version 1.0.6
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for twg-setup
Skill instructions — Now says: Use `twg skills list` to check saved quarantine policy. Quarantined skills keep fresh content but have no global discovery links. Refresh does not clear this...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Sep 30, 2026 · 23:13 UTC
- Use `twg work query` and `twg collaborators` to brief me on my last 7 days: top three workstreams, key people involved, blockers, and next actions. - I was out for [N days]. Catch me up on [topic]: material changes, decisions, blockers...
Oct 24, 2026 · 13:12 UTC
Use `twg skills list` to check saved quarantine policy. Quarantined skills keep fresh content but have no global discovery links. Refresh does not clear this policy. Restore only when the user asks to enable the skill: twg skills restore...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -96,6 +96,15 @@ twg skills install --yes ``` +Use `twg skills list` to check saved quarantine policy. +Quarantined skills keep fresh content but have no global discovery links. +Refresh does not clear this policy. +Restore only when the user asks to enable the skill: + +```bash +twg skills restore <exact-name> --yes +``` + After a skill install or refresh, start a new Codex thread. Summarize any remaining issue in one line. @@ -109,8 +118,8 @@ Only when the user's request was setup alone, offer a few useful TWG prompts: -- Use `twg work query` and `twg collaborators` to brief me on my last 7 days: top three workstreams, key people involved, blockers, and next actions. -- I was out for [N days]. Catch me up on [topic]: material changes, decisions, blockers, conversations I should respond to, and my top three next actions. +- Summarize my last 7 days: workstreams, key people, blockers, next actions. Use `twg work query` and `twg collaborators`. +- I was away for [N days]. Catch me up on [topic]: updates, decisions, blockers, replies, next actions. - Who should I talk to about [topic]? Identify the owner and up to three experts, explain why each is relevant, and tell me whom to contact first. - What's the latest status of [project]? Include the owner, last update, blockers or risks, and next milestone. - Find the three most useful current design docs or PRDs for [topic]. Explain what each establishes and flag stale or conflicting guidance.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: twg-setup\ndescription: Install, upgrade, authenticate, or repair `twg` for Codex, including missing CLI or skills and doctor/auth follow-up. TWG gives Codex grounded work context across Jira, Confluence, Bitbucket, JSM, Assets, Slack, Google Drive, and more, so it can connect tickets, docs, code, people, and decisions; surface risks and dependencies; summarize progress; and keep work moving.\nallowed-tools: Bash\n---\n\n# TWG Setup\n\nRecognized installer hosts: `claude-code`, `codex`, `copilot`, `cursor`, `devin`, `gemini`, `hermes`, `intellij`, `opencode`, `pi`, `qoder`, `vscode`.\n\n## Unix / macOS\n\n**Installer command — run in your terminal**\n\n```bash\ncurl -fsSL --retry 2 https://teamwork-graph.atlassian.com/cli/install | bash -s -- --plugin codex\n```\n\n**Inspect**\n\n```bash\nTWG_BIN=\"$(command -v twg || true)\"\nif [ -z \"$TWG_BIN\" ] && [ -x \"$HOME/.local/bin/twg\" ]; then\n TWG_BIN=\"$HOME/.local/bin/twg\"\nfi\nif [ -z \"$TWG_BIN\" ]; then\n echo \"twg was not found at the standard launcher path; install TWG or add its directory to PATH.\" >&2\nfi\n[ -n \"$TWG_BIN\" ] && \"$TWG_BIN\" doctor || true\n```\n\n## Windows PowerShell\n\n**Installer command — run in PowerShell**\n\n```powershell\ncurl.exe -fsSL https://teamwork-graph.atlassian.com/cli/install.ps1 -o \"$env:TEMP\\twg-install.ps1\"\npowershell -ExecutionPolicy Bypass -File \"$env:TEMP\\twg-install.ps1\" -Plugin codex\n```\n\n**Inspect**\n\n```powershell\n$twgCommand = Get-Command twg -ErrorAction SilentlyContinue\n$TWG_BIN = if ($twgCommand) { $twgCommand.Path } else { $null }\nif (-not $TWG_BIN -and $env:LOCALAPPDATA) {\n $fallback = Join-Path $env:LOCALAPPDATA \"Programs\\twg\\bin\\twg.exe\"\n if (Test-Path -LiteralPath $fallback -PathType Leaf) { $TWG_BIN = $fallback }\n}\nif (-not $TWG_BIN) {\n Write-Warning \"twg was not found; use the installer command above.\"\n}\nif ($TWG_BIN) {\n & $TWG_BIN doctor\n}\n```\n\n## Common flow\n\nInfer the current host from runtime context; never ask the user to identify it. Use its\nplugin argument when recognized; omit it only when the host is genuinely unknown. Do not\nnarrate the plugin argument or describe attribution or analytics to the user.\n\n1. Run the OS-specific **Inspect** block.\n2. If the CLI is missing, give the user the OS-specific installer command with the plugin\n argument for a recognized host. Do not execute it, even in an interactive terminal. End with\n `When it finishes, reply done.` Do not include `doctor` or another follow-up command.\n3. After the user replies `done`, run the OS-specific **Inspect** block yourself so `doctor`\n verifies the installation. Never ask the user to run `doctor` or paste its output, and never\n reinstall for auth, permission, or command errors.\n\nPut every installer or remediation command handed to the user in a fenced `bash` or `powershell`\nblock. Use raw URLs; never render a command inline or as a Markdown link. The user completes\nagreements, browser authentication, optional connections, and secret entry in their own terminal.\nNever request or expose tokens, passwords, API keys, 2FA/OTP codes, or OAuth `device_code`.\n\n## Doctor remediation\n\nUse this section only for a pre-existing install or after the user replies `done`. Run only the\nreported fix.\n\n- Give interactive auth and setup fixes to the user; never execute them yourself. Put the command\n in the matching fenced block, end with `When it finishes, reply done.`, and rerun `doctor`\n yourself after that reply.\n- Run noninteractive fixes, including skill refresh, directly, then rerun `doctor`.\n- OAuth: `twg login --force`.\n- Initial/general setup: `twg setup`.\n- Optional Bitbucket: `twg setup bitbucket`.\n\n### Skill refresh\n\nIf doctor reports a skill issue or Codex cannot see TWG skills, refresh them at\n`~/.agents/skills`:\n\n```text\ntwg skills install --yes\n```\n\nAfter a skill install or refresh, start a new Codex thread.\n\nSummarize any remaining issue in one line.\n\n## Continue The Original Request\n\nWhen `doctor` is healthy, resume and complete the user's original request. Do not stop\nat setup or ask the user to choose a new task.\n\n## Things To Try\n\nOnly when the user's request was setup alone, offer a few useful TWG prompts:\n\n- Use `twg work query` and `twg collaborators` to brief me on my last 7 days: top three workstreams, key people involved, blockers, and next actions.\n- I was out for [N days]. Catch me up on [topic]: material changes, decisions, blockers, conversations I should respond to, and my top three next actions.\n- Who should I talk to about [topic]? Identify the owner and up to three experts, explain why each is relevant, and tell me whom to contact first.\n- What's the latest status of [project]? Include the owner, last update, blockers or risks, and next milestone.\n- Find the three most useful current design docs or PRDs for [topic]. Explain what each establishes and flag stale or conflicting guidance.\n""---\nname: twg-setup\ndescription: Install, upgrade, authenticate, or repair `twg` for Codex, including missing CLI or skills and doctor/auth follow-up. TWG gives Codex grounded work context across Jira, Confluence, Bitbucket, JSM, Assets, Slack, Google Drive, and more, so it can connect tickets, docs, code, people, and decisions; surface risks and dependencies; summarize progress; and keep work moving.\nallowed-tools: Bash\n---\n\n# TWG Setup\n\nRecognized installer hosts: `claude-code`, `codex`, `copilot`, `cursor`, `devin`, `gemini`, `hermes`, `intellij`, `opencode`, `pi`, `qoder`, `vscode`.\n\n## Unix / macOS\n\n**Installer command — run in your terminal**\n\n```bash\ncurl -fsSL --retry 2 https://teamwork-graph.atlassian.com/cli/install | bash -s -- --plugin codex\n```\n\n**Inspect**\n\n```bash\nTWG_BIN=\"$(command -v twg || true)\"\nif [ -z \"$TWG_BIN\" ] && [ -x \"$HOME/.local/bin/twg\" ]; then\n TWG_BIN=\"$HOME/.local/bin/twg\"\nfi\nif [ -z \"$TWG_BIN\" ]; then\n echo \"twg was not found at the standard launcher path; install TWG or add its directory to PATH.\" >&2\nfi\n[ -n \"$TWG_BIN\" ] && \"$TWG_BIN\" doctor || true\n```\n\n## Windows PowerShell\n\n**Installer command — run in PowerShell**\n\n```powershell\ncurl.exe -fsSL https://teamwork-graph.atlassian.com/cli/install.ps1 -o \"$env:TEMP\\twg-install.ps1\"\npowershell -ExecutionPolicy Bypass -File \"$env:TEMP\\twg-install.ps1\" -Plugin codex\n```\n\n**Inspect**\n\n```powershell\n$twgCommand = Get-Command twg -ErrorAction SilentlyContinue\n$TWG_BIN = if ($twgCommand) { $twgCommand.Path } else { $null }\nif (-not $TWG_BIN -and $env:LOCALAPPDATA) {\n $fallback = Join-Path $env:LOCALAPPDATA \"Programs\\twg\\bin\\twg.exe\"\n if (Test-Path -LiteralPath $fallback -PathType Leaf) { $TWG_BIN = $fallback }\n}\nif (-not $TWG_BIN) {\n Write-Warning \"twg was not found; use the installer command above.\"\n}\nif ($TWG_BIN) {\n & $TWG_BIN doctor\n}\n```\n\n## Common flow\n\nInfer the current host from runtime context; never ask the user to identify it. Use its\nplugin argument when recognized; omit it only when the host is genuinely unknown. Do not\nnarrate the plugin argument or describe attribution or analytics to the user.\n\n1. Run the OS-specific **Inspect** block.\n2. If the CLI is missing, give the user the OS-specific installer command with the plugin\n argument for a recognized host. Do not execute it, even in an interactive terminal. End with\n `When it finishes, reply done.` Do not include `doctor` or another follow-up command.\n3. After the user replies `done`, run the OS-specific **Inspect** block yourself so `doctor`\n verifies the installation. Never ask the user to run `doctor` or paste its output, and never\n reinstall for auth, permission, or command errors.\n\nPut every installer or remediation command handed to the user in a fenced `bash` or `powershell`\nblock. Use raw URLs; never render a command inline or as a Markdown link. The user completes\nagreements, browser authentication, optional connections, and secret entry in their own terminal.\nNever request or expose tokens, passwords, API keys, 2FA/OTP codes, or OAuth `device_code`.\n\n## Doctor remediation\n\nUse this section only for a pre-existing install or after the user replies `done`. Run only the\nreported fix.\n\n- Give interactive auth and setup fixes to the user; never execute them yourself. Put the command\n in the matching fenced block, end with `When it finishes, reply done.`, and rerun `doctor`\n yourself after that reply.\n- Run noninteractive fixes, including skill refresh, directly, then rerun `doctor`.\n- OAuth: `twg login --force`.\n- Initial/general setup: `twg setup`.\n- Optional Bitbucket: `twg setup bitbucket`.\n\n### Skill refresh\n\nIf doctor reports a skill issue or Codex cannot see TWG skills, refresh them at\n`~/.agents/skills`:\n\n```text\ntwg skills install --yes\n```\n\nUse `twg skills list` to check saved quarantine policy.\nQuarantined skills keep fresh content but have no global discovery links.\nRefresh does not clear this policy.\nRestore only when the user asks to enable the skill:\n\n```bash\ntwg skills restore <exact-name> --yes\n```\n\nAfter a skill install or refresh, start a new Codex thread.\n\nSummarize any remaining issue in one line.\n\n## Continue The Original Request\n\nWhen `doctor` is healthy, resume and complete the user's original request. Do not stop\nat setup or ask the user to choose a new task.\n\n## Things To Try\n\nOnly when the user's request was setup alone, offer a few useful TWG prompts:\n\n- Summarize my last 7 days: workstreams, key people, blockers, next actions. Use `twg work query` and `twg collaborators`.\n- I was away for [N days]. Catch me up on [topic]: updates, decisions, blockers, replies, next actions.\n- Who should I talk to about [topic]? Identify the owner and up to three experts, explain why each is relevant, and tell me whom to contact first.\n- What's the latest status of [project]? Include the owner, last update, blockers or risks, and next milestone.\n- Find the three most useful current design docs or PRDs for [topic]. Explain what each establishes and flag stale or conflicting guidance.\n"Full snapshot data
{
"description": "Install, upgrade, authenticate, or repair `twg` for Codex, including missing CLI or skills and doctor/auth follow-up. TWG gives Codex grounded work context across Jira, Confluence, Bitbucket, JSM, Assets, Slack, Google Drive, and more, so it can connect tickets, docs, code, people, and decisions; surface risks and dependencies; summarize progress; and keep work moving.",
"included_files": [],
"name": "twg-setup",
"skill_md_contents": "---\nname: twg-setup\ndescription: Install, upgrade, authenticate, or repair `twg` for Codex, including missing CLI or skills and doctor/auth follow-up. TWG gives Codex grounded work context across Jira, Confluence, Bitbucket, JSM, Assets, Slack, Google Drive, and more, so it can connect tickets, docs, code, people, and decisions; surface risks and dependencies; summarize progress; and keep work moving.\nallowed-tools: Bash\n---\n\n# TWG Setup\n\nRecognized installer hosts: `claude-code`, `codex`, `copilot`, `cursor`, `devin`, `gemini`, `hermes`, `intellij`, `opencode`, `pi`, `qoder`, `vscode`.\n\n## Unix / macOS\n\n**Installer command — run in your terminal**\n\n```bash\ncurl -fsSL --retry 2 https://teamwork-graph.atlassian.com/cli/install | bash -s -- --plugin codex\n```\n\n**Inspect**\n\n```bash\nTWG_BIN=\"$(command -v twg || true)\"\nif [ -z \"$TWG_BIN\" ] && [ -x \"$HOME/.local/bin/twg\" ]; then\n TWG_BIN=\"$HOME/.local/bin/twg\"\nfi\nif [ -z \"$TWG_BIN\" ]; then\n echo \"twg was not found at the standard launcher path; install TWG or add its directory to PATH.\" >&2\nfi\n[ -n \"$TWG_BIN\" ] && \"$TWG_BIN\" doctor || true\n```\n\n## Windows PowerShell\n\n**Installer command — run in PowerShell**\n\n```powershell\ncurl.exe -fsSL https://teamwork-graph.atlassian.com/cli/install.ps1 -o \"$env:TEMP\\twg-install.ps1\"\npowershell -ExecutionPolicy Bypass -File \"$env:TEMP\\twg-install.ps1\" -Plugin codex\n```\n\n**Inspect**\n\n```powershell\n$twgCommand = Get-Command twg -ErrorAction SilentlyContinue\n$TWG_BIN = if ($twgCommand) { $twgCommand.Path } else { $null }\nif (-not $TWG_BIN -and $env:LOCALAPPDATA) {\n $fallback = Join-Path $env:LOCALAPPDATA \"Programs\\twg\\bin\\twg.exe\"\n if (Test-Path -LiteralPath $fallback -PathType Leaf) { $TWG_BIN = $fallback }\n}\nif (-not $TWG_BIN) {\n Write-Warning \"twg was not found; use the installer command above.\"\n}\nif ($TWG_BIN) {\n & $TWG_BIN doctor\n}\n```\n\n## Common flow\n\nInfer the current host from runtime context; never ask the user to identify it. Use its\nplugin argument when recognized; omit it only when the host is genuinely unknown. Do not\nnarrate the plugin argument or describe attribution or analytics to the user.\n\n1. Run the OS-specific **Inspect** block.\n2. If the CLI is missing, give the user the OS-specific installer command with the plugin\n argument for a recognized host. Do not execute it, even in an interactive terminal. End with\n `When it finishes, reply done.` Do not include `doctor` or another follow-up command.\n3. After the user replies `done`, run the OS-specific **Inspect** block yourself so `doctor`\n verifies the installation. Never ask the user to run `doctor` or paste its output, and never\n reinstall for auth, permission, or command errors.\n\nPut every installer or remediation command handed to the user in a fenced `bash` or `powershell`\nblock. Use raw URLs; never render a command inline or as a Markdown link. The user completes\nagreements, browser authentication, optional connections, and secret entry in their own terminal.\nNever request or expose tokens, passwords, API keys, 2FA/OTP codes, or OAuth `device_code`.\n\n## Doctor remediation\n\nUse this section only for a pre-existing install or after the user replies `done`. Run only the\nreported fix.\n\n- Give interactive auth and setup fixes to the user; never execute them yourself. Put the command\n in the matching fenced block, end with `When it finishes, reply done.`, and rerun `doctor`\n yourself after that reply.\n- Run noninteractive fixes, including skill refresh, directly, then rerun `doctor`.\n- OAuth: `twg login --force`.\n- Initial/general setup: `twg setup`.\n- Optional Bitbucket: `twg setup bitbucket`.\n\n### Skill refresh\n\nIf doctor reports a skill issue or Codex cannot see TWG skills, refresh them at\n`~/.agents/skills`:\n\n```text\ntwg skills install --yes\n```\n\nUse `twg skills list` to check saved quarantine policy.\nQuarantined skills keep fresh content but have no global discovery links.\nRefresh does not clear this policy.\nRestore only when the user asks to enable the skill:\n\n```bash\ntwg skills restore <exact-name> --yes\n```\n\nAfter a skill install or refresh, start a new Codex thread.\n\nSummarize any remaining issue in one line.\n\n## Continue The Original Request\n\nWhen `doctor` is healthy, resume and complete the user's original request. Do not stop\nat setup or ask the user to choose a new task.\n\n## Things To Try\n\nOnly when the user's request was setup alone, offer a few useful TWG prompts:\n\n- Summarize my last 7 days: workstreams, key people, blockers, next actions. Use `twg work query` and `twg collaborators`.\n- I was away for [N days]. Catch me up on [topic]: updates, decisions, blockers, replies, next actions.\n- Who should I talk to about [topic]? Identify the owner and up to three experts, explain why each is relevant, and tell me whom to contact first.\n- What's the latest status of [project]? Include the owner, last update, blockers or risks, and next milestone.\n- Find the three most useful current design docs or PRDs for [topic]. Explain what each establishes and flag stale or conflicting guidance.\n"
}SHA-256 of public snapshot: c23aac99e584b8ccf1010e626ebdcf3d3c14b06305b148d90987f9919436524a