[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-atlassian-twg-operational-health":3,"mdc-ciob43-key":43,"related-repo-atlassian-twg-operational-health":482,"related-org-atlassian-twg-operational-health":591},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":38,"sourceUrl":41,"mdContent":42},"twg-operational-health","manage operational health and incident response","Use with the root `twg` skill for on-call handoffs, incident response and investigation, post-incident reviews, reliability reviews, Assets refresh, capacity views, meeting summaries, and operational risk readouts.\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,25],{"name":13,"slug":14,"type":15},"SRE","sre","tag",{"name":17,"slug":18,"type":15},"Operations","operations",{"name":20,"slug":21,"type":15},"Monitoring","monitoring",{"name":23,"slug":24,"type":15},"Incident Response","incident-response",{"name":9,"slug":8,"type":15},6,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Ftwg-cli","2026-07-25T05:31:50.282857",null,0,[32,8,33,34,35,36,37],"agents","claude","cli","codex","teamwork-graph","twg",{"repoUrl":27,"stars":26,"forks":30,"topics":39,"description":40},[32,8,33,34,35,36,37],"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-operational-health","---\nname: twg-operational-health\ndescription: >\n  Use with the root `twg` skill for on-call handoffs, incident response and\n  investigation, post-incident reviews, reliability reviews, Assets refresh,\n  capacity views, meeting summaries, and operational risk readouts.\n---\n\n# twg-operational-health\n\nUse together with the root `twg` skill. Exact command grammar comes from live\n`twg help` 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- \"I'm taking over on-call\"\n- \"Reliability, incident, SEV, or post-incident review readout\"\n- \"Investigate an active incident and find mitigation\"\n- \"Analyze root cause or draft postmortem\u002FPIR learning\u002Faction items\"\n- \"Open risks, blockers, overloaded people, operational health\"\n\n## First Move\n\nResolve scope, window, anchors, owner\u002Fescalation path, status, recency, and\nfollow-ups. Find the operational anchor before joining relevant surfaces.\nRun without `--site`; TWG inherits the user's pinned Jira\u002FJSM site. Only add a\nsite override when the user explicitly requests another tenant. Never assume a\nvendor-internal incident site.\n\n## Evidence Policy\n\n- Rank by impact, urgency, owner clarity, recurrence risk, and actionability;\n  separate live risks from historical mentions.\n- Cluster compact incident, PIR, follow-up, runbook, owner, asset, or meeting\n  evidence by service, theme, owner, and recency. Hydrate highest-risk clusters;\n  stop once theme, owner signal, and confidence are clear.\n- Separate `working theory`, `confirmed problem`, `mitigation`, and `root\n  cause`. Require a causal mechanism for confirmed root cause; a closed record\n  is insufficient. Mark claims `confirmed`, `supported`, `candidate`, or\n  `missing evidence`; use references for RCA details.\n- After one correction of a repeated backend, auth, or schema error, report the\n  gap and use remaining evidence instead of nearby aliases or broad inventories.\n\n## Recipe Cards\n\n### Leadership Reliability Review \u002F On-Call Handoff\n\nLoad `references\u002Freliability-review.md`. Resolve leader, platform, and window;\ncluster supported themes, separate cause from mitigation, connect prevention\nwork, and rank leadership actions. For handoffs, add a first-hour checklist and\nescalation map.\n\n### Incident Investigation \u002F Mitigation\n\nUse when the incident is active, newly mitigated, or pre-PIR. Anchor on the\nincident record, then pull responders, symptoms, impact, recent\ndeploys\u002Fflags\u002Fconfig, topology, alert\u002Flog\u002Fmetric pointers, ownership, runbooks,\nand similar incidents. If ticket fields are sparse, probe the four golden-signal\nfamilies with bounded follow-ups. See `references\u002Fincident-investigation.md`.\nOutput a four-signal matrix, hypotheses, confidence, next checks, and mitigation\noptions; never call a mitigation the root cause without the causal mechanism.\n\n### Post-Incident Root Cause \u002F Learning\n\nUse after mitigation\u002Frecovery when drafting or evaluating a postmortem\u002FPIR. Pair\nthe incident with the PIR, linked docs, final comms, remediation PRs, and action\nitems; cover confirmed mitigation, causal mechanism, 5-why chain, and\ndetection\u002Fresponse gaps. See `references\u002Fpir-root-cause.md`. Output root cause,\ncontributing factors, mitigation-versus-cause, and prioritized actions.\n\n### Assets \u002F Asset Refresh\n\nBuild contributors from project\u002Fgoal\u002FJira\u002FPR\u002Fdoc\u002Factivity evidence. Inspect\nAssets schema\u002Ftype metadata before AQL; join people via discovered user-like\nattributes such as `Calculated user`. Rank by contribution centrality plus asset\nrisk, and report confidence and gaps. See `references\u002Fassets.md`.\n\n### Capacity \u002F Staffing \u002F Meetings\n\nFor staffing, resolve project\u002Ftopic\u002Forg and identify people by related work,\nownership, review influence, docs, and project\u002Fgoal involvement; check load\n  before recommending. For meetings, query scoped recordings, preview transcripts\n  first, fetch full transcripts only for central ones, then summarize decisions,\n  action items, and gaps.\n\n## Output Shape\n\n- Lead with severity, urgency, or recommendation, then owner, status, recency,\n  impact, confidence, and evidence.\n- For active investigations, add a four-signal evidence matrix and an\n  incident-to-learning timeline with confirmed problem, mitigation, root-cause\n  status, and prevention action.\n- Group patterns across artifacts, give ranked next actions with a suggested\n  owner, and call out data gaps (missing transcripts, no asset match, stale\n  update, ACL\u002Fauth gaps, weak ownership).\n\n## Anti-Patterns\n\n- Do not fetch every transcript or page body, or treat every incident mention\n  as a live risk.\n- Do not wait for chat\u002Fcomments to label RCA before surfacing directional\n  hypotheses for pre-PIR investigation.\n- Do not call mitigation root cause without an established mechanism. Do not\n  treat workflow panels, bot comments, or opaque fields as RCA narrative.\n- Do not use keyword matches alone as org ownership — cross-check assignee,\n  service owner, PIR participants, or org-tree membership.\n- Do not join Assets by display-name guesses before inspecting schema\u002Ftype\n  fields, or recommend staffing from activity counts alone.\n\n## References\n\n- `references\u002Fassets.md` - schema-first Assets queries and person\u002Fdevice joins\n- `references\u002Freliability-review.md` - bounded incident\u002FPIR leadership review\n- `references\u002Fincident-investigation.md` - active investigation and mitigation\n- `references\u002Fpir-root-cause.md` - post-mitigation root-cause and PIR workflow\n",{"data":44,"body":45},{"name":4,"description":6},{"type":46,"children":47},"root",[48,55,85,92,129,135,165,171,184,190,274,280,287,300,306,319,325,338,344,364,370,375,381,399,405,433,439],{"type":49,"tag":50,"props":51,"children":52},"element","h1",{"id":4},[53],{"type":54,"value":4},"text",{"type":49,"tag":56,"props":57,"children":58},"p",{},[59,61,67,69,75,77,83],{"type":54,"value":60},"Use together with the root ",{"type":49,"tag":62,"props":63,"children":65},"code",{"className":64},[],[66],{"type":54,"value":37},{"type":54,"value":68}," skill. Exact command grammar comes from live\n",{"type":49,"tag":62,"props":70,"children":72},{"className":71},[],[73],{"type":54,"value":74},"twg help",{"type":54,"value":76}," or ",{"type":49,"tag":62,"props":78,"children":80},{"className":79},[],[81],{"type":54,"value":82},"twg help describe \u003Cpath>",{"type":54,"value":84},".",{"type":49,"tag":86,"props":87,"children":89},"h2",{"id":88},"cli-launcher-fallback",[90],{"type":54,"value":91},"CLI launcher fallback",{"type":49,"tag":56,"props":93,"children":94},{},[95,97,103,105,111,113,119,121,127],{"type":54,"value":96},"Run ",{"type":49,"tag":62,"props":98,"children":100},{"className":99},[],[101],{"type":54,"value":102},"twg \u003Ccommand>",{"type":54,"value":104},". On shell ",{"type":49,"tag":62,"props":106,"children":108},{"className":107},[],[109],{"type":54,"value":110},"command not found",{"type":54,"value":112},", use ",{"type":49,"tag":62,"props":114,"children":116},{"className":115},[],[117],{"type":54,"value":118},"$HOME\u002F.local\u002Fbin\u002Ftwg",{"type":54,"value":120},"\n(macOS\u002FLinux) \u002F ",{"type":49,"tag":62,"props":122,"children":124},{"className":123},[],[125],{"type":54,"value":126},"$env:LOCALAPPDATA\\Programs\\twg\\bin\\twg.exe",{"type":54,"value":128}," (PowerShell), then\ntell user to add that directory to PATH. Do not treat auth or command errors as\nPATH failures.",{"type":49,"tag":86,"props":130,"children":132},{"id":131},"use-when",[133],{"type":54,"value":134},"Use When",{"type":49,"tag":136,"props":137,"children":138},"ul",{},[139,145,150,155,160],{"type":49,"tag":140,"props":141,"children":142},"li",{},[143],{"type":54,"value":144},"\"I'm taking over on-call\"",{"type":49,"tag":140,"props":146,"children":147},{},[148],{"type":54,"value":149},"\"Reliability, incident, SEV, or post-incident review readout\"",{"type":49,"tag":140,"props":151,"children":152},{},[153],{"type":54,"value":154},"\"Investigate an active incident and find mitigation\"",{"type":49,"tag":140,"props":156,"children":157},{},[158],{"type":54,"value":159},"\"Analyze root cause or draft postmortem\u002FPIR learning\u002Faction items\"",{"type":49,"tag":140,"props":161,"children":162},{},[163],{"type":54,"value":164},"\"Open risks, blockers, overloaded people, operational health\"",{"type":49,"tag":86,"props":166,"children":168},{"id":167},"first-move",[169],{"type":54,"value":170},"First Move",{"type":49,"tag":56,"props":172,"children":173},{},[174,176,182],{"type":54,"value":175},"Resolve scope, window, anchors, owner\u002Fescalation path, status, recency, and\nfollow-ups. Find the operational anchor before joining relevant surfaces.\nRun without ",{"type":49,"tag":62,"props":177,"children":179},{"className":178},[],[180],{"type":54,"value":181},"--site",{"type":54,"value":183},"; TWG inherits the user's pinned Jira\u002FJSM site. Only add a\nsite override when the user explicitly requests another tenant. Never assume a\nvendor-internal incident site.",{"type":49,"tag":86,"props":185,"children":187},{"id":186},"evidence-policy",[188],{"type":54,"value":189},"Evidence Policy",{"type":49,"tag":136,"props":191,"children":192},{},[193,198,203,269],{"type":49,"tag":140,"props":194,"children":195},{},[196],{"type":54,"value":197},"Rank by impact, urgency, owner clarity, recurrence risk, and actionability;\nseparate live risks from historical mentions.",{"type":49,"tag":140,"props":199,"children":200},{},[201],{"type":54,"value":202},"Cluster compact incident, PIR, follow-up, runbook, owner, asset, or meeting\nevidence by service, theme, owner, and recency. Hydrate highest-risk clusters;\nstop once theme, owner signal, and confidence are clear.",{"type":49,"tag":140,"props":204,"children":205},{},[206,208,214,216,222,223,229,231,237,239,245,246,252,253,259,261,267],{"type":54,"value":207},"Separate ",{"type":49,"tag":62,"props":209,"children":211},{"className":210},[],[212],{"type":54,"value":213},"working theory",{"type":54,"value":215},", ",{"type":49,"tag":62,"props":217,"children":219},{"className":218},[],[220],{"type":54,"value":221},"confirmed problem",{"type":54,"value":215},{"type":49,"tag":62,"props":224,"children":226},{"className":225},[],[227],{"type":54,"value":228},"mitigation",{"type":54,"value":230},", and ",{"type":49,"tag":62,"props":232,"children":234},{"className":233},[],[235],{"type":54,"value":236},"root cause",{"type":54,"value":238},". Require a causal mechanism for confirmed root cause; a closed record\nis insufficient. Mark claims ",{"type":49,"tag":62,"props":240,"children":242},{"className":241},[],[243],{"type":54,"value":244},"confirmed",{"type":54,"value":215},{"type":49,"tag":62,"props":247,"children":249},{"className":248},[],[250],{"type":54,"value":251},"supported",{"type":54,"value":215},{"type":49,"tag":62,"props":254,"children":256},{"className":255},[],[257],{"type":54,"value":258},"candidate",{"type":54,"value":260},", or\n",{"type":49,"tag":62,"props":262,"children":264},{"className":263},[],[265],{"type":54,"value":266},"missing evidence",{"type":54,"value":268},"; use references for RCA details.",{"type":49,"tag":140,"props":270,"children":271},{},[272],{"type":54,"value":273},"After one correction of a repeated backend, auth, or schema error, report the\ngap and use remaining evidence instead of nearby aliases or broad inventories.",{"type":49,"tag":86,"props":275,"children":277},{"id":276},"recipe-cards",[278],{"type":54,"value":279},"Recipe Cards",{"type":49,"tag":281,"props":282,"children":284},"h3",{"id":283},"leadership-reliability-review-on-call-handoff",[285],{"type":54,"value":286},"Leadership Reliability Review \u002F On-Call Handoff",{"type":49,"tag":56,"props":288,"children":289},{},[290,292,298],{"type":54,"value":291},"Load ",{"type":49,"tag":62,"props":293,"children":295},{"className":294},[],[296],{"type":54,"value":297},"references\u002Freliability-review.md",{"type":54,"value":299},". Resolve leader, platform, and window;\ncluster supported themes, separate cause from mitigation, connect prevention\nwork, and rank leadership actions. For handoffs, add a first-hour checklist and\nescalation map.",{"type":49,"tag":281,"props":301,"children":303},{"id":302},"incident-investigation-mitigation",[304],{"type":54,"value":305},"Incident Investigation \u002F Mitigation",{"type":49,"tag":56,"props":307,"children":308},{},[309,311,317],{"type":54,"value":310},"Use when the incident is active, newly mitigated, or pre-PIR. Anchor on the\nincident record, then pull responders, symptoms, impact, recent\ndeploys\u002Fflags\u002Fconfig, topology, alert\u002Flog\u002Fmetric pointers, ownership, runbooks,\nand similar incidents. If ticket fields are sparse, probe the four golden-signal\nfamilies with bounded follow-ups. See ",{"type":49,"tag":62,"props":312,"children":314},{"className":313},[],[315],{"type":54,"value":316},"references\u002Fincident-investigation.md",{"type":54,"value":318},".\nOutput a four-signal matrix, hypotheses, confidence, next checks, and mitigation\noptions; never call a mitigation the root cause without the causal mechanism.",{"type":49,"tag":281,"props":320,"children":322},{"id":321},"post-incident-root-cause-learning",[323],{"type":54,"value":324},"Post-Incident Root Cause \u002F Learning",{"type":49,"tag":56,"props":326,"children":327},{},[328,330,336],{"type":54,"value":329},"Use after mitigation\u002Frecovery when drafting or evaluating a postmortem\u002FPIR. Pair\nthe incident with the PIR, linked docs, final comms, remediation PRs, and action\nitems; cover confirmed mitigation, causal mechanism, 5-why chain, and\ndetection\u002Fresponse gaps. See ",{"type":49,"tag":62,"props":331,"children":333},{"className":332},[],[334],{"type":54,"value":335},"references\u002Fpir-root-cause.md",{"type":54,"value":337},". Output root cause,\ncontributing factors, mitigation-versus-cause, and prioritized actions.",{"type":49,"tag":281,"props":339,"children":341},{"id":340},"assets-asset-refresh",[342],{"type":54,"value":343},"Assets \u002F Asset Refresh",{"type":49,"tag":56,"props":345,"children":346},{},[347,349,355,357,363],{"type":54,"value":348},"Build contributors from project\u002Fgoal\u002FJira\u002FPR\u002Fdoc\u002Factivity evidence. Inspect\nAssets schema\u002Ftype metadata before AQL; join people via discovered user-like\nattributes such as ",{"type":49,"tag":62,"props":350,"children":352},{"className":351},[],[353],{"type":54,"value":354},"Calculated user",{"type":54,"value":356},". Rank by contribution centrality plus asset\nrisk, and report confidence and gaps. See ",{"type":49,"tag":62,"props":358,"children":360},{"className":359},[],[361],{"type":54,"value":362},"references\u002Fassets.md",{"type":54,"value":84},{"type":49,"tag":281,"props":365,"children":367},{"id":366},"capacity-staffing-meetings",[368],{"type":54,"value":369},"Capacity \u002F Staffing \u002F Meetings",{"type":49,"tag":56,"props":371,"children":372},{},[373],{"type":54,"value":374},"For staffing, resolve project\u002Ftopic\u002Forg and identify people by related work,\nownership, review influence, docs, and project\u002Fgoal involvement; check load\nbefore recommending. For meetings, query scoped recordings, preview transcripts\nfirst, fetch full transcripts only for central ones, then summarize decisions,\naction items, and gaps.",{"type":49,"tag":86,"props":376,"children":378},{"id":377},"output-shape",[379],{"type":54,"value":380},"Output Shape",{"type":49,"tag":136,"props":382,"children":383},{},[384,389,394],{"type":49,"tag":140,"props":385,"children":386},{},[387],{"type":54,"value":388},"Lead with severity, urgency, or recommendation, then owner, status, recency,\nimpact, confidence, and evidence.",{"type":49,"tag":140,"props":390,"children":391},{},[392],{"type":54,"value":393},"For active investigations, add a four-signal evidence matrix and an\nincident-to-learning timeline with confirmed problem, mitigation, root-cause\nstatus, and prevention action.",{"type":49,"tag":140,"props":395,"children":396},{},[397],{"type":54,"value":398},"Group patterns across artifacts, give ranked next actions with a suggested\nowner, and call out data gaps (missing transcripts, no asset match, stale\nupdate, ACL\u002Fauth gaps, weak ownership).",{"type":49,"tag":86,"props":400,"children":402},{"id":401},"anti-patterns",[403],{"type":54,"value":404},"Anti-Patterns",{"type":49,"tag":136,"props":406,"children":407},{},[408,413,418,423,428],{"type":49,"tag":140,"props":409,"children":410},{},[411],{"type":54,"value":412},"Do not fetch every transcript or page body, or treat every incident mention\nas a live risk.",{"type":49,"tag":140,"props":414,"children":415},{},[416],{"type":54,"value":417},"Do not wait for chat\u002Fcomments to label RCA before surfacing directional\nhypotheses for pre-PIR investigation.",{"type":49,"tag":140,"props":419,"children":420},{},[421],{"type":54,"value":422},"Do not call mitigation root cause without an established mechanism. Do not\ntreat workflow panels, bot comments, or opaque fields as RCA narrative.",{"type":49,"tag":140,"props":424,"children":425},{},[426],{"type":54,"value":427},"Do not use keyword matches alone as org ownership — cross-check assignee,\nservice owner, PIR participants, or org-tree membership.",{"type":49,"tag":140,"props":429,"children":430},{},[431],{"type":54,"value":432},"Do not join Assets by display-name guesses before inspecting schema\u002Ftype\nfields, or recommend staffing from activity counts alone.",{"type":49,"tag":86,"props":434,"children":436},{"id":435},"references",[437],{"type":54,"value":438},"References",{"type":49,"tag":136,"props":440,"children":441},{},[442,452,462,472],{"type":49,"tag":140,"props":443,"children":444},{},[445,450],{"type":49,"tag":62,"props":446,"children":448},{"className":447},[],[449],{"type":54,"value":362},{"type":54,"value":451}," - schema-first Assets queries and person\u002Fdevice joins",{"type":49,"tag":140,"props":453,"children":454},{},[455,460],{"type":49,"tag":62,"props":456,"children":458},{"className":457},[],[459],{"type":54,"value":297},{"type":54,"value":461}," - bounded incident\u002FPIR leadership review",{"type":49,"tag":140,"props":463,"children":464},{},[465,470],{"type":49,"tag":62,"props":466,"children":468},{"className":467},[],[469],{"type":54,"value":316},{"type":54,"value":471}," - active investigation and mitigation",{"type":49,"tag":140,"props":473,"children":474},{},[475,480],{"type":49,"tag":62,"props":476,"children":478},{"className":477},[],[479],{"type":54,"value":335},{"type":54,"value":481}," - post-mitigation root-cause and PIR workflow",{"items":483,"total":590},[484,496,513,528,543,556,576],{"slug":37,"name":37,"fn":485,"description":486,"org":487,"tags":488,"stars":26,"repoUrl":27,"updatedAt":495},"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},[489,490,493],{"name":9,"slug":8,"type":15},{"name":491,"slug":492,"type":15},"Automation","automation",{"name":494,"slug":34,"type":15},"CLI","2026-07-25T05:31:49.287124",{"slug":497,"name":497,"fn":498,"description":499,"org":500,"tags":501,"stars":26,"repoUrl":27,"updatedAt":512},"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},[502,503,506,509],{"name":9,"slug":8,"type":15},{"name":504,"slug":505,"type":15},"Enterprise Search","enterprise-search",{"name":507,"slug":508,"type":15},"Knowledge Management","knowledge-management",{"name":510,"slug":511,"type":15},"Research","research","2026-07-25T05:56:27.582838",{"slug":514,"name":514,"fn":515,"description":516,"org":517,"tags":518,"stars":26,"repoUrl":27,"updatedAt":527},"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},[519,522,523,526],{"name":520,"slug":521,"type":15},"A\u002FB Testing","a-b-testing",{"name":9,"slug":8,"type":15},{"name":524,"slug":525,"type":15},"MCP","mcp",{"name":510,"slug":511,"type":15},"2026-07-22T05:36:16.491486",{"slug":529,"name":529,"fn":530,"description":531,"org":532,"tags":533,"stars":26,"repoUrl":27,"updatedAt":542},"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},[534,535,538,541],{"name":9,"slug":8,"type":15},{"name":536,"slug":537,"type":15},"Confluence","confluence",{"name":539,"slug":540,"type":15},"Documents","documents",{"name":507,"slug":508,"type":15},"2026-07-25T05:31:47.271484",{"slug":544,"name":544,"fn":545,"description":546,"org":547,"tags":548,"stars":26,"repoUrl":27,"updatedAt":555},"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},[549,550,551,552],{"name":9,"slug":8,"type":15},{"name":507,"slug":508,"type":15},{"name":510,"slug":511,"type":15},{"name":553,"slug":554,"type":15},"Search","search","2026-07-25T05:31:51.299922",{"slug":557,"name":557,"fn":558,"description":559,"org":560,"tags":561,"stars":26,"repoUrl":27,"updatedAt":575},"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},[562,563,566,569,572],{"name":9,"slug":8,"type":15},{"name":564,"slug":565,"type":15},"Code Review","code-review",{"name":567,"slug":568,"type":15},"Engineering","engineering",{"name":570,"slug":571,"type":15},"GitHub","github",{"name":573,"slug":574,"type":15},"Pull Requests","pull-requests","2026-07-25T05:31:52.317362",{"slug":577,"name":577,"fn":578,"description":579,"org":580,"tags":581,"stars":26,"repoUrl":27,"updatedAt":589},"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},[582,583,586],{"name":9,"slug":8,"type":15},{"name":584,"slug":585,"type":15},"Jira","jira",{"name":587,"slug":588,"type":15},"Task Management","task-management","2026-07-25T05:31:46.279241",11,{"items":592,"total":758},[593,608,624,641,652,663,678,695,710,722,734,744],{"slug":594,"name":594,"fn":595,"description":596,"org":597,"tags":598,"stars":605,"repoUrl":606,"updatedAt":607},"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},[599,600,601,604],{"name":491,"slug":492,"type":15},{"name":584,"slug":585,"type":15},{"name":602,"slug":603,"type":15},"Meetings","meetings",{"name":587,"slug":588,"type":15},848,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fatlassian-mcp-server","2026-07-12T07:58:45.323861",{"slug":609,"name":609,"fn":610,"description":611,"org":612,"tags":613,"stars":605,"repoUrl":606,"updatedAt":623},"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},[614,615,616,617,620],{"name":9,"slug":8,"type":15},{"name":536,"slug":537,"type":15},{"name":584,"slug":585,"type":15},{"name":618,"slug":619,"type":15},"Project Management","project-management",{"name":621,"slug":622,"type":15},"Reporting","reporting","2026-07-12T07:58:38.457696",{"slug":625,"name":625,"fn":626,"description":627,"org":628,"tags":629,"stars":605,"repoUrl":606,"updatedAt":640},"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},[630,633,636,637],{"name":631,"slug":632,"type":15},"Agile","agile",{"name":634,"slug":635,"type":15},"Dashboards","dashboards",{"name":584,"slug":585,"type":15},{"name":638,"slug":639,"type":15},"Sprint Planning","sprint-planning","2026-07-12T07:58:41.031798",{"slug":642,"name":642,"fn":643,"description":644,"org":645,"tags":646,"stars":605,"repoUrl":606,"updatedAt":651},"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},[647,648,649,650],{"name":536,"slug":537,"type":15},{"name":504,"slug":505,"type":15},{"name":584,"slug":585,"type":15},{"name":507,"slug":508,"type":15},"2026-07-12T07:58:39.684132",{"slug":653,"name":653,"fn":654,"description":655,"org":656,"tags":657,"stars":605,"repoUrl":606,"updatedAt":662},"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},[658,659,660,661],{"name":631,"slug":632,"type":15},{"name":536,"slug":537,"type":15},{"name":584,"slug":585,"type":15},{"name":618,"slug":619,"type":15},"2026-07-12T07:58:37.200385",{"slug":664,"name":664,"fn":665,"description":666,"org":667,"tags":668,"stars":605,"repoUrl":606,"updatedAt":677},"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},[669,672,673,674],{"name":670,"slug":671,"type":15},"Debugging","debugging",{"name":584,"slug":585,"type":15},{"name":618,"slug":619,"type":15},{"name":675,"slug":676,"type":15},"Triage","triage","2026-07-12T07:58:33.007343",{"slug":679,"name":679,"fn":680,"description":681,"org":682,"tags":683,"stars":692,"repoUrl":693,"updatedAt":694},"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},[684,685,686,689],{"name":9,"slug":8,"type":15},{"name":494,"slug":34,"type":15},{"name":687,"slug":688,"type":15},"Deployment","deployment",{"name":690,"slug":691,"type":15},"Plugin Development","plugin-development",14,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fforge-skills","2026-07-12T07:58:52.007851",{"slug":696,"name":696,"fn":697,"description":698,"org":699,"tags":700,"stars":692,"repoUrl":693,"updatedAt":709},"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},[701,702,705,706],{"name":9,"slug":8,"type":15},{"name":703,"slug":704,"type":15},"Code Analysis","code-analysis",{"name":687,"slug":688,"type":15},{"name":707,"slug":708,"type":15},"QA","qa","2026-07-12T07:58:50.744672",{"slug":711,"name":711,"fn":712,"description":713,"org":714,"tags":715,"stars":692,"repoUrl":693,"updatedAt":721},"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},[716,719,720],{"name":717,"slug":718,"type":15},"API Development","api-development",{"name":567,"slug":568,"type":15},{"name":504,"slug":505,"type":15},"2026-07-12T07:58:48.520248",{"slug":723,"name":723,"fn":724,"description":725,"org":726,"tags":727,"stars":692,"repoUrl":693,"updatedAt":733},"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},[728,729,732],{"name":9,"slug":8,"type":15},{"name":730,"slug":731,"type":15},"Cost Optimization","cost-optimization",{"name":17,"slug":18,"type":15},"2026-07-12T07:58:53.557299",{"slug":735,"name":735,"fn":736,"description":737,"org":738,"tags":739,"stars":692,"repoUrl":693,"updatedAt":743},"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},[740,741,742],{"name":9,"slug":8,"type":15},{"name":670,"slug":671,"type":15},{"name":687,"slug":688,"type":15},"2026-07-12T07:58:47.226713",{"slug":745,"name":745,"fn":746,"description":747,"org":748,"tags":749,"stars":692,"repoUrl":693,"updatedAt":757},"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},[750,753,754],{"name":751,"slug":752,"type":15},"Audit","audit",{"name":703,"slug":704,"type":15},{"name":755,"slug":756,"type":15},"Security","security","2026-07-12T07:58:54.806538",24]