[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-atlassian-twg-status-rollups":3,"mdc-uli5o6-key":40,"related-repo-atlassian-twg-status-rollups":578,"related-org-atlassian-twg-status-rollups":687},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":35,"sourceUrl":38,"mdContent":39},"twg-status-rollups","generate status rollups and appraisal evidence","Use with root `twg` for status rollups, personal work summaries, and decision-readiness or go\u002Fno-go briefs. Routes to `pr-tree`, `org-tree`, `work-tree`, or `workitem-tree`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"atlassian","Atlassian","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fatlassian.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Productivity","productivity","tag",{"name":17,"slug":18,"type":15},"Management","management",{"name":20,"slug":21,"type":15},"Reporting","reporting",{"name":9,"slug":8,"type":15},6,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Ftwg-cli","2026-07-25T05:31:48.288054",null,0,[29,8,30,31,32,33,34],"agents","claude","cli","codex","teamwork-graph","twg",{"repoUrl":24,"stars":23,"forks":27,"topics":36,"description":37},[29,8,30,31,32,33,34],"Public home for Atlassian Teamwork Graph CLI users, release notes, issue tracking, agent skills, and marketplace plugin integration notes.","https:\u002F\u002Fgithub.com\u002Fatlassian\u002Ftwg-cli\u002Ftree\u002FHEAD\u002Fskills\u002Ftwg-status-rollups","---\nname: twg-status-rollups\ndescription: >\n  Use with root `twg` for status rollups, personal work summaries, and\n  decision-readiness or go\u002Fno-go briefs. Routes to `pr-tree`, `org-tree`,\n  `work-tree`, or `workitem-tree`.\n---\n\n# twg-status-rollups\n\nUse with the root `twg` skill. Get exact command grammar from live `twg help`,\n`twg help \u003Cterms>`, or `twg help describe \u003Cpath>`.\n\n## CLI launcher fallback\n\nRun `twg \u003Ccommand>`. On shell `command not found`, use `$HOME\u002F.local\u002Fbin\u002Ftwg`\n(macOS\u002FLinux) \u002F `$env:LOCALAPPDATA\\Programs\\twg\\bin\\twg.exe` (PowerShell), then\ntell user to add that directory to PATH. Do not treat auth or command errors as\nPATH failures.\n\n## Use When\n\n- \"What did I\u002Fperson\u002Fteam\u002Forg work on?\" or weekly personal update\n- Short-window personal update, standup, handoff, or restart after time away\n- \"Status of project\u002Fgoal\u002Ftopic\u002Ffocus area\"\n- \"Is this project ready to launch?\" or go\u002Fno-go decision brief\n- Leadership, monthly, annual, cycle, appraisal, or goal-alignment readout\n- Org bottlenecks, priorities, stale goals, or project risks\n\n## First Move\n\nResolve scope before retrieval:\n\n- Person\u002Fteam\u002Forg: resolve identity, roster, or org-tree groups.\n- Project, goal, focus area, or topic: resolve native key, ARI, URL, name, or\n  central project\u002Fpage\u002Fworkitem anchors.\n\nEstablish the time window. If absent, ask when precision matters; otherwise use\na recent bounded window and state it. Keep personal summaries to 1 year or less.\n\n## Tree Routing Matrix\n\n- `pr-tree`: merged\u002Fopen PRs, reviews, shipped work, or repo momentum by manager\n  or team. Default for PR-constrained evidence.\n- `org-tree`: manager chain, roster, and reporting structure; use for grouping,\n  not delivery evidence.\n- `workitem-tree`: Jira issue load and active\u002Fdone movement by org tree.\n- `work-tree`: multi-surface org counts across Jira, PRs, goals, projects, docs,\n  or videos. Not for PR-only or Jira-only asks.\n\n## Fast Path: PR-Based Leadership Rollup\n\nFor PR-based leadership prompts:\n\n1. Preserve the requested scope and window; for \"last 2 weeks,\" use\n   `--since 14d`.\n2. Use `pr-tree` first. It groups by reporting-tree `directReports`; add\n   `org-tree` only for hierarchy context.\n3. If option shape is uncertain, inspect `twg help describe \"pr-tree\"` before\n   the data call; do not probe incompatible flag combinations.\n4. Start count-first, then make at most one supported sampling\u002Ffull-fetch pass\n   for repo or theme evidence. Synthesize at manager\u002Fteam level from that tree.\n   Do not issue per-person queries merely to populate every group; use one\n   targeted PR follow-up only when a material theme lacks representative proof.\n5. Add one secondary surface only for a named gap.\n\nTarget 2-4 calls.\n\n## Evidence Policy\n\n- Match evidence to prompt constraints; merged-PR-only conclusions require PR\n  evidence.\n- Start count-first on tree surfaces; hydrate examples only for themes, risks,\n  or owner attribution.\n- Rank broad lists before minimal hydration.\n- Distinguish authored delivery from review, coordination, and influence.\n- Stop when evidence is sufficient. After two identical backend failures, stop\n  that path and report the gap.\n\n## Recipe Cards\n\n### Person Or Personal Update\n\nResolve the person, then pull recent Jira work, PRs, docs\u002Fpages, meetings, and\nproject\u002Fgoal involvement. Load `references\u002Fpersonal-work-summary.md` for exact\nsubject, notification, PR hydration, and outcome-first rules.\nSeparate delivery, review, docs\u002Fstrategy, coordination, and influence.\n\n### Short-Window Personal Update \u002F Standup\n\nLoad `references\u002Fpersonal-work-summary.md`. Resolve the person, preserve the\nrequested project and window, prioritize material work, and distinguish\nevidence gaps from confirmed blockers.\n\n### Team Or Org Leadership Readout\n\nResolve org-tree first. Group before per-person details. Use org-level signals,\nthen hydrate only outliers that change momentum, blockers, review load, or\nownership.\n\n### Project Or Goal Status\n\nFetch the native project\u002Fgoal first. Include owner, state, update,\nlinks, dates, and recency. Hydrate only risk, progress, or dependency evidence.\n\n### Decision Readiness \u002F Go-No-Go\n\nLoad `references\u002Fdecision-readiness.md`. Resolve the native project or decision\nanchor first and keep explicit links as the scope boundary. Identify the gates,\nthen give the requested decision or recommendation with confidence, gaps, and\nchange conditions. Do not infer owners.\n\n### Topic Status\n\nResolve\u002Fsearch once, select central project, goal, page, or workitem anchors,\nthen hydrate those before using broad work\u002Factivity queries.\n\n## References\n\n- `references\u002Fpersonal-work-summary.md` - standups, catch-ups, and broader\n  personal status evidence\n- `references\u002Fdecision-readiness.md` - cross-domain go\u002Fno-go and approval evidence\n\n### Appraisal \u002F Performance Evidence\n\nResolve person and horizon. Separate delivery, review, collaboration,\ndocs\u002Fstrategy, project\u002Fgoal impact, and stakeholder signals. Avoid count-only\nranking; add caveats when evidence is weak.\n\n## Output Shape\n\n- Executive summary first, with 3-6 high-signal observations.\n- Table with owner\u002Fteam\u002Fworkstream, positive signals, risk signals, current\n  focus, confidence, and evidence.\n- Risks and leadership attention ranked by impact and owner.\n- Confidence and gaps, including stale updates, missing product coverage, ACL\n  gaps, or sampled evidence boundaries.\n\n## Anti-Patterns\n\n- Do not make a status report a list of every artifact.\n- Do not infer goal\u002Fproject health from issue counts alone.\n- Do not fan out across every org member if manager\u002Fteam-level grouping answers\n  the prompt.\n- Do not use search snippets as final evidence for status or risk.\n- Start explicit merged\u002Fopen PR rollups with `pr-tree`, not the other trees.\n",{"data":41,"body":42},{"name":4,"description":6},{"type":43,"children":44},"root",[45,52,90,97,134,140,175,181,186,199,204,210,257,263,268,334,339,345,373,379,386,399,405,417,423,428,434,439,445,457,463,468,474,497,503,508,514,537,543],{"type":46,"tag":47,"props":48,"children":49},"element","h1",{"id":4},[50],{"type":51,"value":4},"text",{"type":46,"tag":53,"props":54,"children":55},"p",{},[56,58,64,66,72,74,80,82,88],{"type":51,"value":57},"Use with the root ",{"type":46,"tag":59,"props":60,"children":62},"code",{"className":61},[],[63],{"type":51,"value":34},{"type":51,"value":65}," skill. Get exact command grammar from live ",{"type":46,"tag":59,"props":67,"children":69},{"className":68},[],[70],{"type":51,"value":71},"twg help",{"type":51,"value":73},",\n",{"type":46,"tag":59,"props":75,"children":77},{"className":76},[],[78],{"type":51,"value":79},"twg help \u003Cterms>",{"type":51,"value":81},", or ",{"type":46,"tag":59,"props":83,"children":85},{"className":84},[],[86],{"type":51,"value":87},"twg help describe \u003Cpath>",{"type":51,"value":89},".",{"type":46,"tag":91,"props":92,"children":94},"h2",{"id":93},"cli-launcher-fallback",[95],{"type":51,"value":96},"CLI launcher fallback",{"type":46,"tag":53,"props":98,"children":99},{},[100,102,108,110,116,118,124,126,132],{"type":51,"value":101},"Run ",{"type":46,"tag":59,"props":103,"children":105},{"className":104},[],[106],{"type":51,"value":107},"twg \u003Ccommand>",{"type":51,"value":109},". On shell ",{"type":46,"tag":59,"props":111,"children":113},{"className":112},[],[114],{"type":51,"value":115},"command not found",{"type":51,"value":117},", use ",{"type":46,"tag":59,"props":119,"children":121},{"className":120},[],[122],{"type":51,"value":123},"$HOME\u002F.local\u002Fbin\u002Ftwg",{"type":51,"value":125},"\n(macOS\u002FLinux) \u002F ",{"type":46,"tag":59,"props":127,"children":129},{"className":128},[],[130],{"type":51,"value":131},"$env:LOCALAPPDATA\\Programs\\twg\\bin\\twg.exe",{"type":51,"value":133}," (PowerShell), then\ntell user to add that directory to PATH. Do not treat auth or command errors as\nPATH failures.",{"type":46,"tag":91,"props":135,"children":137},{"id":136},"use-when",[138],{"type":51,"value":139},"Use When",{"type":46,"tag":141,"props":142,"children":143},"ul",{},[144,150,155,160,165,170],{"type":46,"tag":145,"props":146,"children":147},"li",{},[148],{"type":51,"value":149},"\"What did I\u002Fperson\u002Fteam\u002Forg work on?\" or weekly personal update",{"type":46,"tag":145,"props":151,"children":152},{},[153],{"type":51,"value":154},"Short-window personal update, standup, handoff, or restart after time away",{"type":46,"tag":145,"props":156,"children":157},{},[158],{"type":51,"value":159},"\"Status of project\u002Fgoal\u002Ftopic\u002Ffocus area\"",{"type":46,"tag":145,"props":161,"children":162},{},[163],{"type":51,"value":164},"\"Is this project ready to launch?\" or go\u002Fno-go decision brief",{"type":46,"tag":145,"props":166,"children":167},{},[168],{"type":51,"value":169},"Leadership, monthly, annual, cycle, appraisal, or goal-alignment readout",{"type":46,"tag":145,"props":171,"children":172},{},[173],{"type":51,"value":174},"Org bottlenecks, priorities, stale goals, or project risks",{"type":46,"tag":91,"props":176,"children":178},{"id":177},"first-move",[179],{"type":51,"value":180},"First Move",{"type":46,"tag":53,"props":182,"children":183},{},[184],{"type":51,"value":185},"Resolve scope before retrieval:",{"type":46,"tag":141,"props":187,"children":188},{},[189,194],{"type":46,"tag":145,"props":190,"children":191},{},[192],{"type":51,"value":193},"Person\u002Fteam\u002Forg: resolve identity, roster, or org-tree groups.",{"type":46,"tag":145,"props":195,"children":196},{},[197],{"type":51,"value":198},"Project, goal, focus area, or topic: resolve native key, ARI, URL, name, or\ncentral project\u002Fpage\u002Fworkitem anchors.",{"type":46,"tag":53,"props":200,"children":201},{},[202],{"type":51,"value":203},"Establish the time window. If absent, ask when precision matters; otherwise use\na recent bounded window and state it. Keep personal summaries to 1 year or less.",{"type":46,"tag":91,"props":205,"children":207},{"id":206},"tree-routing-matrix",[208],{"type":51,"value":209},"Tree Routing Matrix",{"type":46,"tag":141,"props":211,"children":212},{},[213,224,235,246],{"type":46,"tag":145,"props":214,"children":215},{},[216,222],{"type":46,"tag":59,"props":217,"children":219},{"className":218},[],[220],{"type":51,"value":221},"pr-tree",{"type":51,"value":223},": merged\u002Fopen PRs, reviews, shipped work, or repo momentum by manager\nor team. Default for PR-constrained evidence.",{"type":46,"tag":145,"props":225,"children":226},{},[227,233],{"type":46,"tag":59,"props":228,"children":230},{"className":229},[],[231],{"type":51,"value":232},"org-tree",{"type":51,"value":234},": manager chain, roster, and reporting structure; use for grouping,\nnot delivery evidence.",{"type":46,"tag":145,"props":236,"children":237},{},[238,244],{"type":46,"tag":59,"props":239,"children":241},{"className":240},[],[242],{"type":51,"value":243},"workitem-tree",{"type":51,"value":245},": Jira issue load and active\u002Fdone movement by org tree.",{"type":46,"tag":145,"props":247,"children":248},{},[249,255],{"type":46,"tag":59,"props":250,"children":252},{"className":251},[],[253],{"type":51,"value":254},"work-tree",{"type":51,"value":256},": multi-surface org counts across Jira, PRs, goals, projects, docs,\nor videos. Not for PR-only or Jira-only asks.",{"type":46,"tag":91,"props":258,"children":260},{"id":259},"fast-path-pr-based-leadership-rollup",[261],{"type":51,"value":262},"Fast Path: PR-Based Leadership Rollup",{"type":46,"tag":53,"props":264,"children":265},{},[266],{"type":51,"value":267},"For PR-based leadership prompts:",{"type":46,"tag":269,"props":270,"children":271},"ol",{},[272,284,311,324,329],{"type":46,"tag":145,"props":273,"children":274},{},[275,277,283],{"type":51,"value":276},"Preserve the requested scope and window; for \"last 2 weeks,\" use\n",{"type":46,"tag":59,"props":278,"children":280},{"className":279},[],[281],{"type":51,"value":282},"--since 14d",{"type":51,"value":89},{"type":46,"tag":145,"props":285,"children":286},{},[287,289,294,296,302,304,309],{"type":51,"value":288},"Use ",{"type":46,"tag":59,"props":290,"children":292},{"className":291},[],[293],{"type":51,"value":221},{"type":51,"value":295}," first. It groups by reporting-tree ",{"type":46,"tag":59,"props":297,"children":299},{"className":298},[],[300],{"type":51,"value":301},"directReports",{"type":51,"value":303},"; add\n",{"type":46,"tag":59,"props":305,"children":307},{"className":306},[],[308],{"type":51,"value":232},{"type":51,"value":310}," only for hierarchy context.",{"type":46,"tag":145,"props":312,"children":313},{},[314,316,322],{"type":51,"value":315},"If option shape is uncertain, inspect ",{"type":46,"tag":59,"props":317,"children":319},{"className":318},[],[320],{"type":51,"value":321},"twg help describe \"pr-tree\"",{"type":51,"value":323}," before\nthe data call; do not probe incompatible flag combinations.",{"type":46,"tag":145,"props":325,"children":326},{},[327],{"type":51,"value":328},"Start count-first, then make at most one supported sampling\u002Ffull-fetch pass\nfor repo or theme evidence. Synthesize at manager\u002Fteam level from that tree.\nDo not issue per-person queries merely to populate every group; use one\ntargeted PR follow-up only when a material theme lacks representative proof.",{"type":46,"tag":145,"props":330,"children":331},{},[332],{"type":51,"value":333},"Add one secondary surface only for a named gap.",{"type":46,"tag":53,"props":335,"children":336},{},[337],{"type":51,"value":338},"Target 2-4 calls.",{"type":46,"tag":91,"props":340,"children":342},{"id":341},"evidence-policy",[343],{"type":51,"value":344},"Evidence Policy",{"type":46,"tag":141,"props":346,"children":347},{},[348,353,358,363,368],{"type":46,"tag":145,"props":349,"children":350},{},[351],{"type":51,"value":352},"Match evidence to prompt constraints; merged-PR-only conclusions require PR\nevidence.",{"type":46,"tag":145,"props":354,"children":355},{},[356],{"type":51,"value":357},"Start count-first on tree surfaces; hydrate examples only for themes, risks,\nor owner attribution.",{"type":46,"tag":145,"props":359,"children":360},{},[361],{"type":51,"value":362},"Rank broad lists before minimal hydration.",{"type":46,"tag":145,"props":364,"children":365},{},[366],{"type":51,"value":367},"Distinguish authored delivery from review, coordination, and influence.",{"type":46,"tag":145,"props":369,"children":370},{},[371],{"type":51,"value":372},"Stop when evidence is sufficient. After two identical backend failures, stop\nthat path and report the gap.",{"type":46,"tag":91,"props":374,"children":376},{"id":375},"recipe-cards",[377],{"type":51,"value":378},"Recipe Cards",{"type":46,"tag":380,"props":381,"children":383},"h3",{"id":382},"person-or-personal-update",[384],{"type":51,"value":385},"Person Or Personal Update",{"type":46,"tag":53,"props":387,"children":388},{},[389,391,397],{"type":51,"value":390},"Resolve the person, then pull recent Jira work, PRs, docs\u002Fpages, meetings, and\nproject\u002Fgoal involvement. Load ",{"type":46,"tag":59,"props":392,"children":394},{"className":393},[],[395],{"type":51,"value":396},"references\u002Fpersonal-work-summary.md",{"type":51,"value":398}," for exact\nsubject, notification, PR hydration, and outcome-first rules.\nSeparate delivery, review, docs\u002Fstrategy, coordination, and influence.",{"type":46,"tag":380,"props":400,"children":402},{"id":401},"short-window-personal-update-standup",[403],{"type":51,"value":404},"Short-Window Personal Update \u002F Standup",{"type":46,"tag":53,"props":406,"children":407},{},[408,410,415],{"type":51,"value":409},"Load ",{"type":46,"tag":59,"props":411,"children":413},{"className":412},[],[414],{"type":51,"value":396},{"type":51,"value":416},". Resolve the person, preserve the\nrequested project and window, prioritize material work, and distinguish\nevidence gaps from confirmed blockers.",{"type":46,"tag":380,"props":418,"children":420},{"id":419},"team-or-org-leadership-readout",[421],{"type":51,"value":422},"Team Or Org Leadership Readout",{"type":46,"tag":53,"props":424,"children":425},{},[426],{"type":51,"value":427},"Resolve org-tree first. Group before per-person details. Use org-level signals,\nthen hydrate only outliers that change momentum, blockers, review load, or\nownership.",{"type":46,"tag":380,"props":429,"children":431},{"id":430},"project-or-goal-status",[432],{"type":51,"value":433},"Project Or Goal Status",{"type":46,"tag":53,"props":435,"children":436},{},[437],{"type":51,"value":438},"Fetch the native project\u002Fgoal first. Include owner, state, update,\nlinks, dates, and recency. Hydrate only risk, progress, or dependency evidence.",{"type":46,"tag":380,"props":440,"children":442},{"id":441},"decision-readiness-go-no-go",[443],{"type":51,"value":444},"Decision Readiness \u002F Go-No-Go",{"type":46,"tag":53,"props":446,"children":447},{},[448,449,455],{"type":51,"value":409},{"type":46,"tag":59,"props":450,"children":452},{"className":451},[],[453],{"type":51,"value":454},"references\u002Fdecision-readiness.md",{"type":51,"value":456},". Resolve the native project or decision\nanchor first and keep explicit links as the scope boundary. Identify the gates,\nthen give the requested decision or recommendation with confidence, gaps, and\nchange conditions. Do not infer owners.",{"type":46,"tag":380,"props":458,"children":460},{"id":459},"topic-status",[461],{"type":51,"value":462},"Topic Status",{"type":46,"tag":53,"props":464,"children":465},{},[466],{"type":51,"value":467},"Resolve\u002Fsearch once, select central project, goal, page, or workitem anchors,\nthen hydrate those before using broad work\u002Factivity queries.",{"type":46,"tag":91,"props":469,"children":471},{"id":470},"references",[472],{"type":51,"value":473},"References",{"type":46,"tag":141,"props":475,"children":476},{},[477,487],{"type":46,"tag":145,"props":478,"children":479},{},[480,485],{"type":46,"tag":59,"props":481,"children":483},{"className":482},[],[484],{"type":51,"value":396},{"type":51,"value":486}," - standups, catch-ups, and broader\npersonal status evidence",{"type":46,"tag":145,"props":488,"children":489},{},[490,495],{"type":46,"tag":59,"props":491,"children":493},{"className":492},[],[494],{"type":51,"value":454},{"type":51,"value":496}," - cross-domain go\u002Fno-go and approval evidence",{"type":46,"tag":380,"props":498,"children":500},{"id":499},"appraisal-performance-evidence",[501],{"type":51,"value":502},"Appraisal \u002F Performance Evidence",{"type":46,"tag":53,"props":504,"children":505},{},[506],{"type":51,"value":507},"Resolve person and horizon. Separate delivery, review, collaboration,\ndocs\u002Fstrategy, project\u002Fgoal impact, and stakeholder signals. Avoid count-only\nranking; add caveats when evidence is weak.",{"type":46,"tag":91,"props":509,"children":511},{"id":510},"output-shape",[512],{"type":51,"value":513},"Output Shape",{"type":46,"tag":141,"props":515,"children":516},{},[517,522,527,532],{"type":46,"tag":145,"props":518,"children":519},{},[520],{"type":51,"value":521},"Executive summary first, with 3-6 high-signal observations.",{"type":46,"tag":145,"props":523,"children":524},{},[525],{"type":51,"value":526},"Table with owner\u002Fteam\u002Fworkstream, positive signals, risk signals, current\nfocus, confidence, and evidence.",{"type":46,"tag":145,"props":528,"children":529},{},[530],{"type":51,"value":531},"Risks and leadership attention ranked by impact and owner.",{"type":46,"tag":145,"props":533,"children":534},{},[535],{"type":51,"value":536},"Confidence and gaps, including stale updates, missing product coverage, ACL\ngaps, or sampled evidence boundaries.",{"type":46,"tag":91,"props":538,"children":540},{"id":539},"anti-patterns",[541],{"type":51,"value":542},"Anti-Patterns",{"type":46,"tag":141,"props":544,"children":545},{},[546,551,556,561,566],{"type":46,"tag":145,"props":547,"children":548},{},[549],{"type":51,"value":550},"Do not make a status report a list of every artifact.",{"type":46,"tag":145,"props":552,"children":553},{},[554],{"type":51,"value":555},"Do not infer goal\u002Fproject health from issue counts alone.",{"type":46,"tag":145,"props":557,"children":558},{},[559],{"type":51,"value":560},"Do not fan out across every org member if manager\u002Fteam-level grouping answers\nthe prompt.",{"type":46,"tag":145,"props":562,"children":563},{},[564],{"type":51,"value":565},"Do not use search snippets as final evidence for status or risk.",{"type":46,"tag":145,"props":567,"children":568},{},[569,571,576],{"type":51,"value":570},"Start explicit merged\u002Fopen PR rollups with ",{"type":46,"tag":59,"props":572,"children":574},{"className":573},[],[575],{"type":51,"value":221},{"type":51,"value":577},", not the other trees.",{"items":579,"total":686},[580,592,609,624,639,652,672],{"slug":34,"name":34,"fn":581,"description":582,"org":583,"tags":584,"stars":23,"repoUrl":24,"updatedAt":591},"execute Atlassian work-data tasks","Root TWG CLI skill for Atlassian work-data tasks. Use typed commands for known anchors; use live `twg help` only when command shape or output contract is uncertain.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[585,586,589],{"name":9,"slug":8,"type":15},{"name":587,"slug":588,"type":15},"Automation","automation",{"name":590,"slug":31,"type":15},"CLI","2026-07-25T05:31:49.287124",{"slug":593,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":23,"repoUrl":24,"updatedAt":608},"twg-agentic-search","perform iterative enterprise knowledge search","Use with root `twg` for deep iterative enterprise\u002Fcompany knowledge search and internal research with Rovo Search across connected apps\u002Fconnectors including Confluence, Jira, Drive, Slack, Bitbucket, and GitHub.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[598,599,602,605],{"name":9,"slug":8,"type":15},{"name":600,"slug":601,"type":15},"Enterprise Search","enterprise-search",{"name":603,"slug":604,"type":15},"Knowledge Management","knowledge-management",{"name":606,"slug":607,"type":15},"Research","research","2026-07-25T05:56:27.582838",{"slug":610,"name":610,"fn":611,"description":612,"org":613,"tags":614,"stars":23,"repoUrl":24,"updatedAt":623},"twg-bench-lite","run A\u002FB comparisons of Atlassian context","Run a lightweight single-prompt A\u002FB comparison of free Atlassian\u002Flocal MCP context vs TWG CLI graph context using paired read-only agent sessions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[615,618,619,622],{"name":616,"slug":617,"type":15},"A\u002FB Testing","a-b-testing",{"name":9,"slug":8,"type":15},{"name":620,"slug":621,"type":15},"MCP","mcp",{"name":606,"slug":607,"type":15},"2026-07-22T05:36:16.491486",{"slug":625,"name":625,"fn":626,"description":627,"org":628,"tags":629,"stars":23,"repoUrl":24,"updatedAt":638},"twg-confluence","manage Confluence content and hierarchy","Use with root `twg` for Confluence content, spaces, hierarchy, authoring, editing, comments, versions, permissions, exports, and CQL. Applies Confluence semantics and safe write rules.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[630,631,634,637],{"name":9,"slug":8,"type":15},{"name":632,"slug":633,"type":15},"Confluence","confluence",{"name":635,"slug":636,"type":15},"Documents","documents",{"name":603,"slug":604,"type":15},"2026-07-25T05:31:47.271484",{"slug":640,"name":640,"fn":641,"description":642,"org":643,"tags":644,"stars":23,"repoUrl":24,"updatedAt":651},"twg-context-discovery","discover project context and dependencies","Use with root `twg` for deep context, dependency maps, related entities, project-to-repo discovery, OOO catch-ups, and \"catch me up\" requests around a concrete anchor.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[645,646,647,648],{"name":9,"slug":8,"type":15},{"name":603,"slug":604,"type":15},{"name":606,"slug":607,"type":15},{"name":649,"slug":650,"type":15},"Search","search","2026-07-25T05:31:51.299922",{"slug":653,"name":653,"fn":654,"description":655,"org":656,"tags":657,"stars":23,"repoUrl":24,"updatedAt":671},"twg-engineering-work","analyze engineering work and pull requests","Use with root `twg` for code search, repositories using an API\u002Fpackage, implementation and reverse-dependency discovery, PR status and reviews, repo contributors, hot areas, and issue-to-PR lookups.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[658,659,662,665,668],{"name":9,"slug":8,"type":15},{"name":660,"slug":661,"type":15},"Code Review","code-review",{"name":663,"slug":664,"type":15},"Engineering","engineering",{"name":666,"slug":667,"type":15},"GitHub","github",{"name":669,"slug":670,"type":15},"Pull Requests","pull-requests","2026-07-25T05:31:52.317362",{"slug":673,"name":673,"fn":674,"description":675,"org":676,"tags":677,"stars":23,"repoUrl":24,"updatedAt":685},"twg-jira","manage Jira work items and projects","Use with root `twg` for Jira workitems, projects, boards, sprints, fields, transitions, comments, links, and administration. Applies Jira semantics and safe mutation rules.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[678,679,682],{"name":9,"slug":8,"type":15},{"name":680,"slug":681,"type":15},"Jira","jira",{"name":683,"slug":684,"type":15},"Task Management","task-management","2026-07-25T05:31:46.279241",11,{"items":688,"total":854},[689,704,718,735,746,757,772,789,804,816,830,840],{"slug":690,"name":690,"fn":691,"description":692,"org":693,"tags":694,"stars":701,"repoUrl":702,"updatedAt":703},"capture-tasks-from-meeting-notes","create Jira tasks from meeting notes","Analyze meeting notes to find action items and create Jira tasks for assigned work. When an agent needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[695,696,697,700],{"name":587,"slug":588,"type":15},{"name":680,"slug":681,"type":15},{"name":698,"slug":699,"type":15},"Meetings","meetings",{"name":683,"slug":684,"type":15},848,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fatlassian-mcp-server","2026-07-12T07:58:45.323861",{"slug":705,"name":705,"fn":706,"description":707,"org":708,"tags":709,"stars":701,"repoUrl":702,"updatedAt":717},"generate-status-report","generate project status reports for Confluence","Generate project status reports from Jira issues and publish to Confluence. When an agent needs to: (1) Create a status report for a project, (2) Summarize project progress or updates, (3) Generate weekly\u002Fdaily reports from Jira, (4) Publish status summaries to Confluence, or (5) Analyze project blockers and completion. Queries Jira issues, categorizes by status\u002Fpriority, and creates formatted reports for delivery managers and executives.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[710,711,712,713,716],{"name":9,"slug":8,"type":15},{"name":632,"slug":633,"type":15},{"name":680,"slug":681,"type":15},{"name":714,"slug":715,"type":15},"Project Management","project-management",{"name":20,"slug":21,"type":15},"2026-07-12T07:58:38.457696",{"slug":719,"name":719,"fn":720,"description":721,"org":722,"tags":723,"stars":701,"repoUrl":702,"updatedAt":734},"jira-sprint-dashboard","create Jira sprint dashboards","Create a visual Jira sprint dashboard from Jira project, space, sprint, board, filter, JQL, work item keys, or Jira URL data. Use when the user asks for a Jira sprint dashboard, standup dashboard, sprint review, delivery review, engineering manager dashboard, WIP review, planning view, closeout view, or a visual snapshot of Jira work that is more useful than a flat report. Use the richest dashboard format supported by the current agent, such as Cursor Canvas, an interactive artifact, HTML, or Markdown.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[724,727,730,731],{"name":725,"slug":726,"type":15},"Agile","agile",{"name":728,"slug":729,"type":15},"Dashboards","dashboards",{"name":680,"slug":681,"type":15},{"name":732,"slug":733,"type":15},"Sprint Planning","sprint-planning","2026-07-12T07:58:41.031798",{"slug":736,"name":736,"fn":737,"description":738,"org":739,"tags":740,"stars":701,"repoUrl":702,"updatedAt":745},"search-company-knowledge","search internal company knowledge bases","Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[741,742,743,744],{"name":632,"slug":633,"type":15},{"name":600,"slug":601,"type":15},{"name":680,"slug":681,"type":15},{"name":603,"slug":604,"type":15},"2026-07-12T07:58:39.684132",{"slug":747,"name":747,"fn":748,"description":749,"org":750,"tags":751,"stars":701,"repoUrl":702,"updatedAt":756},"spec-to-backlog","convert Confluence specifications to Jira backlogs","Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[752,753,754,755],{"name":725,"slug":726,"type":15},{"name":632,"slug":633,"type":15},{"name":680,"slug":681,"type":15},{"name":714,"slug":715,"type":15},"2026-07-12T07:58:37.200385",{"slug":758,"name":758,"fn":759,"description":760,"org":761,"tags":762,"stars":701,"repoUrl":702,"updatedAt":771},"triage-issue","triage bug reports in Jira","Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket with proper context, or (5) Add information to an existing ticket. Searches Jira for similar issues, identifies duplicates, checks fix history, and helps create well-structured bug reports.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[763,766,767,768],{"name":764,"slug":765,"type":15},"Debugging","debugging",{"name":680,"slug":681,"type":15},{"name":714,"slug":715,"type":15},{"name":769,"slug":770,"type":15},"Triage","triage","2026-07-12T07:58:33.007343",{"slug":773,"name":773,"fn":774,"description":775,"org":776,"tags":777,"stars":786,"repoUrl":787,"updatedAt":788},"forge-app-builder","build and deploy Atlassian Forge apps","Guides building, deploying, troubleshooting, and installing Atlassian Forge apps — custom extensions built with the Forge CLI (forge create, forge deploy, forge install). Use when the user wants to create a Forge app (issue panels, dashboard gadgets, Confluence macros, global pages), is encountering Forge CLI errors or deployment issues (e.g. forge install failures, environment errors), or needs help with Forge-specific concepts like resolvers, UI Kit, manifest scopes, or developer spaces. Do not use for general Jira configuration, automation rules, JQL queries, or Atlassian REST API usage outside of a Forge app context.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[778,779,780,783],{"name":9,"slug":8,"type":15},{"name":590,"slug":31,"type":15},{"name":781,"slug":782,"type":15},"Deployment","deployment",{"name":784,"slug":785,"type":15},"Plugin Development","plugin-development",14,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fforge-skills","2026-07-12T07:58:52.007851",{"slug":790,"name":790,"fn":791,"description":792,"org":793,"tags":794,"stars":786,"repoUrl":787,"updatedAt":803},"forge-app-review","review Atlassian Forge app readiness","Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest\u002Fmodule wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks \"review my Forge app\", \"pre-deploy check\", \"is this app ready to ship\", \"review manifest\", \"general app review\", \"release readiness\", or asks for a broad quality pass. Do not use for deep security audits\u002FSAST\u002Fexploitability review, cost optimization, or diagnosing a known broken app; route those to forge-security-review, forge-cost-optimizer, or forge-debugger respectively.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[795,796,799,800],{"name":9,"slug":8,"type":15},{"name":797,"slug":798,"type":15},"Code Analysis","code-analysis",{"name":781,"slug":782,"type":15},{"name":801,"slug":802,"type":15},"QA","qa","2026-07-12T07:58:50.744672",{"slug":805,"name":805,"fn":806,"description":807,"org":808,"tags":809,"stars":786,"repoUrl":787,"updatedAt":815},"forge-connector","build Atlassian Forge Teamwork Graph connectors","Guides building and deploying Atlassian Forge Teamwork Graph connector apps that ingest external data into Atlassian's Teamwork Graph, making it searchable in Rovo Search and surfaced in Rovo Chat. Use when the user wants to build a Forge connector, ingest external data into Atlassian, connect a third-party tool (e.g. Google Drive, ServiceNow, Salesforce) to Atlassian, make external content searchable in Rovo, build a graph:connector module, use the @forge\u002Fteamwork-graph SDK, or implement onConnectionChange \u002F validateConnection functions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[810,813,814],{"name":811,"slug":812,"type":15},"API Development","api-development",{"name":663,"slug":664,"type":15},{"name":600,"slug":601,"type":15},"2026-07-12T07:58:48.520248",{"slug":817,"name":817,"fn":818,"description":819,"org":820,"tags":821,"stars":786,"repoUrl":787,"updatedAt":829},"forge-cost-optimizer","optimize Atlassian Forge platform costs","Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's \"Optimise Forge platform costs\" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve scheduled triggers, reduce KVS writes, move work to the frontend, use bridge APIs, batch API calls, add caching, or evaluate Forge Remote trade-offs. By default, perform an audit first and offer to make the recommended changes after presenting the audit. Only modify files immediately when the user explicitly asks the agent to implement or apply optimizations.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[822,823,826],{"name":9,"slug":8,"type":15},{"name":824,"slug":825,"type":15},"Cost Optimization","cost-optimization",{"name":827,"slug":828,"type":15},"Operations","operations","2026-07-12T07:58:53.557299",{"slug":831,"name":831,"fn":832,"description":833,"org":834,"tags":835,"stars":786,"repoUrl":787,"updatedAt":839},"forge-debugger","diagnose and fix Atlassian Forge apps","Diagnoses and fixes issues in Atlassian Forge apps. Use this skill whenever a Forge app has errors, crashes, shows blank UI, fails to deploy, doesn't appear after installation, has permission issues, or produces unexpected output. Trigger on any mention of forge logs, forge deploy errors, resolver errors, blank panels, missing scopes, Custom UI not rendering, production vs dev discrepancies, or any Jira\u002FConfluence app that \"stopped working\". Also trigger when the user asks to debug, troubleshoot, investigate, or fix a Forge app issue — even if they haven't used the word \"Forge\" but describe a Jira panel or Confluence macro acting up.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[836,837,838],{"name":9,"slug":8,"type":15},{"name":764,"slug":765,"type":15},{"name":781,"slug":782,"type":15},"2026-07-12T07:58:47.226713",{"slug":841,"name":841,"fn":842,"description":843,"org":844,"tags":845,"stars":786,"repoUrl":787,"updatedAt":853},"forge-security-review","perform security reviews for Forge apps","Performs a white-box security review of Atlassian Forge apps using structured, Forge-specific security rules and evidence-driven reporting. Use when the user asks for a Forge security review, security audit, vuln assessment, pentest-style code review, authz review, tenant isolation analysis, web trigger hardening, or static analysis execution for a Forge app.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[846,849,850],{"name":847,"slug":848,"type":15},"Audit","audit",{"name":797,"slug":798,"type":15},{"name":851,"slug":852,"type":15},"Security","security","2026-07-12T07:58:54.806538",24]