# Twg

> >

- **Type:** Skill
- **Install:** `agentstack add skill-atlassian-twg-cli-twg`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [atlassian](https://agentstack.voostack.com/s/atlassian)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [atlassian](https://github.com/atlassian)
- **Source:** https://github.com/atlassian/twg-cli/tree/main/skills/twg
- **Website:** https://teamwork-graph.atlassian.com/cli/install

## Install

```sh
agentstack add skill-atlassian-twg-cli-twg
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# twg

TWG routing: use typed commands for anchors. If uncertain, inspect `twg help `,
`twg help describe `, or `twg help discover-skills ""`.

## Overview

Load the narrowest workflow skill:

- `twg-status-rollups` for status and decision-readiness; load it before
  `twg-engineering-work` for PR rollups.
- `twg-context-discovery` for dependencies, graphs, repos, and catch-ups.
- `twg-agentic-search` for fuzzy cross-product Rovo/company-knowledge research.
- `twg-responsibility-routing` for owners, experts, approvers, and escalation.
- `twg-engineering-work` for code search, PRs, contributors, and hot areas.
- `twg-jira-resolve-merged-work` for stale Jira work backed by merged PRs.
- `twg-operational-health` for handoffs, incidents, Assets, staffing, meetings, and risk.
- `twg-bench-lite` for read-only single-prompt A/B comparisons.

## Invocation And Output

Run `twg `. On shell `command not found`, use `$HOME/.local/bin/twg`
(macOS/Linux) / `$env:LOCALAPPDATA\Programs\twg\bin\twg.exe` (PowerShell), then
tell user to add that directory to PATH. Do not treat auth or command errors as
PATH failures.

Do not add per-command env prefixes unless requested; hosts may set `TWG_AGENT_DEFAULTS=1`.

Use `stdout_inline` first when present. Outside benchmark lanes, inspect `output_files.compact`
only when inline evidence is incomplete; full stdout is the last resort.

In TWG-only benchmark lanes, run only `twg`. Never use shell utilities or pipelines
(`jq`, `rg`, `date`). Use compact/inline output, the prompt's timezone and window, and report
gaps. Match the intent to the narrowest companion skill. Let that skill determine the typed route.

## Auth/Setup Guard

Do not run setup, login, install, update, upkeep, or credential commands unless
explicitly requested for setup/auth/repair. Otherwise report remediation and wait for user direction.

## Sandboxed Pipeline Logs

Pipeline logs can redirect to S3. If a sandboxed `twg bb pipeline get`, `wait`, `grep`, or
`tail` log request has a network-blocked message, S3 hostname, or log-only HTTP 403 while
metadata succeeds, treat it as a sandbox restriction, not an authentication failure.

Request an approved unsandboxed retry of that command only. If unavailable, give the user the
exact terminal command; never request credentials or tokens.

## Bounded Evidence Loop

Converge; prefer typed or product-native evidence.

1. Classify the anchor: person, team, project, goal, workitem, page, repo, service, asset, or topic.
2. Resolve once; fetch evidence that changes status, risk, decision, relationship, or action.
3. Rank candidates, hydrate representative items, then synthesize.
4. Stop after the first policy denial; stop after the same auth, ACL, contract, or backend error twice.

## Command Discovery

- Use familiar command families: `resolve`, `rovo search`,
  `user`, `org-tree`, `work query`, `work search`, `pull-requests`, `jira`,
  `confluence`, `docs`, `context`, `responsibility`, `goals`, `projects`,
  `assets`, and `trello`.
- Use `twg rovo search "" [--limit ]` for top-K discovery; explicit `--app` preflights.
- For fuzzy Trello discovery, use `twg trello search "" --limit 20`; no workspace scope.
- For Rovo connectors, use `twg rovo list-apps -o json` (`list-connectors` alias), then explicit `twg rovo search ... --app `; follow its auth action or `twg rovo auth `.
- Keep document relationship history and fuzzy discovery separate:
  - `twg docs query --since  [--account-id ] [--first ]` is user activity history, not title/content search.
  - `twg docs search "" [--limit ]` is fuzzy Rovo discovery across Confluence and ready document connectors.
  - Never pass topic text to `docs query`; route that intent to `docs search`.
- Keep user activity and fuzzy work discovery separate:
  - `twg work query` defaults to seven days of authored work; other activity requires `--activity` / `--include-viewed`.
  - `twg work search ""` is tenant-wide; use `docs search` for documents. Prefer it directly when fuzzy text reaches `work query`.
- Use live help—`twg help ` then `twg help describe `—before guessing grammar; namespace help is not executable.
- Resolve URLs, keys, ARIs, names, and people, then hydrate stable IDs.
- Jira: `jira workitem search ` for Jira fuzzy text, `jira workitem query --jql ` for structured JQL, and `rovo search  --app jira` for semantic discovery.
- Command shape guardrails:
  - Known Jira/Atlas keys are positional for `jira workitem get`, `goals get`, and `projects get`; `--key` is compatibility only.
  - `work query` is user activity (`--scope me|user`), never `--scope global`; use `work search` for topics and advertised filters such as `--types`.
  - For inferred teams (`ari:cloud:graph::jiraTeam/...` or `ari:cloud:graph-store::inferred-team/...`), see `references/inferred-teams.md` and use explicit `--include-inferred`.
- Use `search-code`; omit `--app` so all available indexed SCM surfaces are searched; use `--repo` only as a discovery anchor; widen after generated-doc or incomplete hits.

## Assets / CMDB graph

Traversal (object↔owner/team, Jira↔object) → `assets graph`; see
`references/ASSETS_GRAPH.md`. No hop → `assets search` / `assets query --aql` /
`assets object get`.

## Load The Narrowest Companion

Use a concrete key, URL, ARI, slug, account ID, name, topic, `me`, or window.

- `../twg-jira/SKILL.md` for Jira; `../twg-confluence/SKILL.md` for Confluence edits.
- `../twg-status-rollups/SKILL.md` for status; `../twg-context-discovery/SKILL.md`
  for context, dependencies, and graphs.
- `../twg-agentic-search/SKILL.md` for fuzzy Rovo/company-knowledge search.
- `../twg-responsibility-routing/SKILL.md` for ownership, approval, and escalation.
- `../twg-engineering-work/SKILL.md` for code search, PRs, and reviews;
  `../twg-jira-resolve-merged-work/SKILL.md` for stale Jira work backed by merged PRs.
- `../twg-operational-health/SKILL.md` for handoffs, reliability, incidents, assets, staffing, and risk.

## Rules

- Never guess IDs, flags, slugs, ARIs, object IDs, or mutation contracts.
- For product writes, load the product skill and follow live help.
- Avoid local inspection, caches, schema probes, or diagnostics unless local state is requested.
- For writes, read current state and state the mutation unless execution was requested.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [atlassian](https://github.com/atlassian)
- **Source:** [atlassian/twg-cli](https://github.com/atlassian/twg-cli)
- **License:** Apache-2.0
- **Homepage:** https://teamwork-graph.atlassian.com/cli/install

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-atlassian-twg-cli-twg
- Seller: https://agentstack.voostack.com/s/atlassian
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.