[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-atlassian-twg-engineering-work":3,"mdc--y3feio-key":43,"related-org-atlassian-twg-engineering-work":495,"related-repo-atlassian-twg-engineering-work":678},{"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-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},"atlassian","Atlassian","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fatlassian.png",[12,16,19,22,23],{"name":13,"slug":14,"type":15},"GitHub","github","tag",{"name":17,"slug":18,"type":15},"Code Review","code-review",{"name":20,"slug":21,"type":15},"Engineering","engineering",{"name":9,"slug":8,"type":15},{"name":24,"slug":25,"type":15},"Pull Requests","pull-requests",6,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Ftwg-cli","2026-07-25T05:31:52.317362",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-engineering-work","---\nname: twg-engineering-work\ndescription: >\n  Use with root `twg` for code search, repositories using an API\u002Fpackage,\n  implementation and reverse-dependency discovery, PR status and reviews, repo\n  contributors, hot areas, and issue-to-PR lookups.\n---\n\n# twg-engineering-work\n\nUse together with the root `twg` skill. Exact command grammar must come from\nlive `twg help`, `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- \"Which PRs are waiting for my review?\"\n- \"Where is this API implemented or used?\"\n- \"Which repositories directly depend on this package?\"\n- \"Latest PRs for this issue\"\n- \"Who contributed most to this repo\u002Ftopic?\"\n- \"Repos I created PRs in\"\n- \"Stale reviews\"\n- \"Review flow or bottlenecks\"\n- \"PR-only status for a user, team, or repo\"\n- \"PR status for Alice\" or \"this person's PRs\"\n- \"My PRs this week\"\n- \"Summarize my pull requests for a time window\"\n- \"Open bugs\u002Ftasks with PRs in flight\"\n\n## First Move\n\nResolve the engineering anchor:\n\n- Repo prompt: identify workspace and repo from URL, local checkout, or repo query.\n- PR prompt: resolve exact PR URL, ID, workspace, and repo.\n- Workitem prompt: fetch\u002Fcontext the Jira workitem to discover linked PRs,\n  commits, branches, and repos.\n- Topic prompt: resolve\u002Fsearch once, then find linked repos, PRs, and workitems.\n- Code prompt: search the concrete package, API, symbol, or behavior, then\n  inspect only the source locations needed to verify the requested relationship.\n\nUse matching typed pull-request, Bitbucket, Jira, context, and search commands.\nProvider-native PR commands apply only to their host; Bitbucket\nactivity\u002Fcomment\u002Ftask commands never apply to GitHub PRs. Use focused help for\nuncertain routes\u002Fcontracts.\n\n## Route Selection\n\n- For queues, query candidate PRs first, then hydrate selected PRs needing action.\n- For stale reviews, group by repo, author, reviewer, and stage before fetching\n  detailed comments or diffs.\n- For issue-to-PR lookup, use workitem context before broad PR text search.\n- For repo contributors and hot areas, combine PR\u002Fcommit\u002Ffile-area signals with\n  ownership and review evidence.\n- For PR leadership\u002Fteam\u002Forg rollups, use `twg-status-rollups`; this skill\n  supplements PR details.\n- For person\u002Frepo status, collect merged\u002Fopen PRs for relevant people, repos,\n  and window.\n- Code: load `references\u002Fcode-search.md`.\n- For person-scoped summaries with Jira, docs, meetings, planning, or\n  notifications, use `twg-status-rollups` plus\n  `..\u002Ftwg-status-rollups\u002Freferences\u002Fpersonal-work-summary.md`; this skill owns\n  PR-only work.\n\n## Evidence Policy\n\n- Hydrate PR details, comments, tasks, pipeline status, and diff only for stale,\n  blocked, central, or high-impact PRs.\n- For PR rollups, stop after the evidence set identifies the main themes,\n  repos\u002Fservices, owners, and recency. Do not keep searching for more PRs when\n  the next batch would only add more examples of the same theme.\n- For review status, include age, requested reviewers, comments\u002Ftasks, approval\n  state, CI\u002Fcheck or pipeline state, and last activity when the provider surface\n  exposes them.\n- For repo\u002Fteam reports, group by repo, service, or workstream rather than only\n  person counts.\n- Inspect PR titles\u002Fdescriptions and linked issues to infer themes; do not rank\n  solely by PR count.\n- Keep Bitbucket, GitHub connector\u002Ftool, and Atlassian auth failures separate.\n- If PR graph or repo-wide query calls repeatedly fail, make one narrower\n  fallback using known repos, people, workitems, or search anchors. If that also\n  fails, answer from the successful evidence and call out the PR coverage gap.\n\n## Recipe Cards\n\n### Review Queue\n\nQuery reviewer-scoped open PRs. Sort by waiting time, requested action,\nunresolved tasks\u002Fcomments, failing CI, and project relevance. Hydrate only PRs\nthat need action.\n\n### Stale Reviews \u002F Review Bottlenecks\n\nFind PRs open or waiting beyond the threshold. Group by repo, author, reviewer,\nand stage. Identify bottleneck patterns such as missing reviewer, unresolved\ntasks, failing CI, repeated request-changes, or owner unavailable.\n\n### Issue PRs\n\nUse workitem context to find linked PRs, commits, branches, and repos. Fetch PRs\nonly if the user asks for details, status, or next action.\n\n### Repo Contributors \u002F Hot Areas\n\nQuery PRs\u002Fcommits for the repo and time window. Group by files\u002Fareas, authors,\nreviewers, and themes. For hot areas, prioritize changed area plus frequency and\nownership signals.\n\n### PR-Based Status Rollup\n\nResolve org\u002Fteam first, then collect PRs for members or repos in the time window.\nGroup into themes and repos\u002Fservices. Call out gaps where PR-only evidence omits\nJira, docs, planning, or customer context.\nFor a single person where the prompt is broader than PRs, switch to\n`twg-status-rollups` and load\n`..\u002Ftwg-status-rollups\u002Freferences\u002Fpersonal-work-summary.md`.\n\n## Output Shape\n\nFor queues, include PR, repo, owner, state, reason, next action, and evidence.\nFor engineering reports, summarize workstreams, contributors, bottlenecks,\nrisks, and gaps. Include stable URLs or IDs for key artifacts.\n\n## Anti-Patterns\n\n- Do not guess Bitbucket workspace or repo.\n- Do not fetch every PR body, diff, or comment in a large queue.\n- Do not treat PR counts as impact.\n- Do not mix Bitbucket, GitHub connector\u002Ftool, and Atlassian auth failures.\n",{"data":44,"body":45},{"name":4,"description":6},{"type":46,"children":47},"root",[48,55,93,100,137,143,213,219,224,252,257,263,336,342,380,386,393,398,404,409,415,420,426,431,437,455,461,466,472],{"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,85,91],{"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 must come from\nlive ",{"type":49,"tag":62,"props":70,"children":72},{"className":71},[],[73],{"type":54,"value":74},"twg help",{"type":54,"value":76},", ",{"type":49,"tag":62,"props":78,"children":80},{"className":79},[],[81],{"type":54,"value":82},"twg help \u003Cterms>",{"type":54,"value":84},", or ",{"type":49,"tag":62,"props":86,"children":88},{"className":87},[],[89],{"type":54,"value":90},"twg help describe \u003Cpath>",{"type":54,"value":92},".",{"type":49,"tag":94,"props":95,"children":97},"h2",{"id":96},"cli-launcher-fallback",[98],{"type":54,"value":99},"CLI launcher fallback",{"type":49,"tag":56,"props":101,"children":102},{},[103,105,111,113,119,121,127,129,135],{"type":54,"value":104},"Run ",{"type":49,"tag":62,"props":106,"children":108},{"className":107},[],[109],{"type":54,"value":110},"twg \u003Ccommand>",{"type":54,"value":112},". On shell ",{"type":49,"tag":62,"props":114,"children":116},{"className":115},[],[117],{"type":54,"value":118},"command not found",{"type":54,"value":120},", use ",{"type":49,"tag":62,"props":122,"children":124},{"className":123},[],[125],{"type":54,"value":126},"$HOME\u002F.local\u002Fbin\u002Ftwg",{"type":54,"value":128},"\n(macOS\u002FLinux) \u002F ",{"type":49,"tag":62,"props":130,"children":132},{"className":131},[],[133],{"type":54,"value":134},"$env:LOCALAPPDATA\\Programs\\twg\\bin\\twg.exe",{"type":54,"value":136}," (PowerShell), then\ntell user to add that directory to PATH. Do not treat auth or command errors as\nPATH failures.",{"type":49,"tag":94,"props":138,"children":140},{"id":139},"use-when",[141],{"type":54,"value":142},"Use When",{"type":49,"tag":144,"props":145,"children":146},"ul",{},[147,153,158,163,168,173,178,183,188,193,198,203,208],{"type":49,"tag":148,"props":149,"children":150},"li",{},[151],{"type":54,"value":152},"\"Which PRs are waiting for my review?\"",{"type":49,"tag":148,"props":154,"children":155},{},[156],{"type":54,"value":157},"\"Where is this API implemented or used?\"",{"type":49,"tag":148,"props":159,"children":160},{},[161],{"type":54,"value":162},"\"Which repositories directly depend on this package?\"",{"type":49,"tag":148,"props":164,"children":165},{},[166],{"type":54,"value":167},"\"Latest PRs for this issue\"",{"type":49,"tag":148,"props":169,"children":170},{},[171],{"type":54,"value":172},"\"Who contributed most to this repo\u002Ftopic?\"",{"type":49,"tag":148,"props":174,"children":175},{},[176],{"type":54,"value":177},"\"Repos I created PRs in\"",{"type":49,"tag":148,"props":179,"children":180},{},[181],{"type":54,"value":182},"\"Stale reviews\"",{"type":49,"tag":148,"props":184,"children":185},{},[186],{"type":54,"value":187},"\"Review flow or bottlenecks\"",{"type":49,"tag":148,"props":189,"children":190},{},[191],{"type":54,"value":192},"\"PR-only status for a user, team, or repo\"",{"type":49,"tag":148,"props":194,"children":195},{},[196],{"type":54,"value":197},"\"PR status for Alice\" or \"this person's PRs\"",{"type":49,"tag":148,"props":199,"children":200},{},[201],{"type":54,"value":202},"\"My PRs this week\"",{"type":49,"tag":148,"props":204,"children":205},{},[206],{"type":54,"value":207},"\"Summarize my pull requests for a time window\"",{"type":49,"tag":148,"props":209,"children":210},{},[211],{"type":54,"value":212},"\"Open bugs\u002Ftasks with PRs in flight\"",{"type":49,"tag":94,"props":214,"children":216},{"id":215},"first-move",[217],{"type":54,"value":218},"First Move",{"type":49,"tag":56,"props":220,"children":221},{},[222],{"type":54,"value":223},"Resolve the engineering anchor:",{"type":49,"tag":144,"props":225,"children":226},{},[227,232,237,242,247],{"type":49,"tag":148,"props":228,"children":229},{},[230],{"type":54,"value":231},"Repo prompt: identify workspace and repo from URL, local checkout, or repo query.",{"type":49,"tag":148,"props":233,"children":234},{},[235],{"type":54,"value":236},"PR prompt: resolve exact PR URL, ID, workspace, and repo.",{"type":49,"tag":148,"props":238,"children":239},{},[240],{"type":54,"value":241},"Workitem prompt: fetch\u002Fcontext the Jira workitem to discover linked PRs,\ncommits, branches, and repos.",{"type":49,"tag":148,"props":243,"children":244},{},[245],{"type":54,"value":246},"Topic prompt: resolve\u002Fsearch once, then find linked repos, PRs, and workitems.",{"type":49,"tag":148,"props":248,"children":249},{},[250],{"type":54,"value":251},"Code prompt: search the concrete package, API, symbol, or behavior, then\ninspect only the source locations needed to verify the requested relationship.",{"type":49,"tag":56,"props":253,"children":254},{},[255],{"type":54,"value":256},"Use matching typed pull-request, Bitbucket, Jira, context, and search commands.\nProvider-native PR commands apply only to their host; Bitbucket\nactivity\u002Fcomment\u002Ftask commands never apply to GitHub PRs. Use focused help for\nuncertain routes\u002Fcontracts.",{"type":49,"tag":94,"props":258,"children":260},{"id":259},"route-selection",[261],{"type":54,"value":262},"Route Selection",{"type":49,"tag":144,"props":264,"children":265},{},[266,271,276,281,286,299,304,316],{"type":49,"tag":148,"props":267,"children":268},{},[269],{"type":54,"value":270},"For queues, query candidate PRs first, then hydrate selected PRs needing action.",{"type":49,"tag":148,"props":272,"children":273},{},[274],{"type":54,"value":275},"For stale reviews, group by repo, author, reviewer, and stage before fetching\ndetailed comments or diffs.",{"type":49,"tag":148,"props":277,"children":278},{},[279],{"type":54,"value":280},"For issue-to-PR lookup, use workitem context before broad PR text search.",{"type":49,"tag":148,"props":282,"children":283},{},[284],{"type":54,"value":285},"For repo contributors and hot areas, combine PR\u002Fcommit\u002Ffile-area signals with\nownership and review evidence.",{"type":49,"tag":148,"props":287,"children":288},{},[289,291,297],{"type":54,"value":290},"For PR leadership\u002Fteam\u002Forg rollups, use ",{"type":49,"tag":62,"props":292,"children":294},{"className":293},[],[295],{"type":54,"value":296},"twg-status-rollups",{"type":54,"value":298},"; this skill\nsupplements PR details.",{"type":49,"tag":148,"props":300,"children":301},{},[302],{"type":54,"value":303},"For person\u002Frepo status, collect merged\u002Fopen PRs for relevant people, repos,\nand window.",{"type":49,"tag":148,"props":305,"children":306},{},[307,309,315],{"type":54,"value":308},"Code: load ",{"type":49,"tag":62,"props":310,"children":312},{"className":311},[],[313],{"type":54,"value":314},"references\u002Fcode-search.md",{"type":54,"value":92},{"type":49,"tag":148,"props":317,"children":318},{},[319,321,326,328,334],{"type":54,"value":320},"For person-scoped summaries with Jira, docs, meetings, planning, or\nnotifications, use ",{"type":49,"tag":62,"props":322,"children":324},{"className":323},[],[325],{"type":54,"value":296},{"type":54,"value":327}," plus\n",{"type":49,"tag":62,"props":329,"children":331},{"className":330},[],[332],{"type":54,"value":333},"..\u002Ftwg-status-rollups\u002Freferences\u002Fpersonal-work-summary.md",{"type":54,"value":335},"; this skill owns\nPR-only work.",{"type":49,"tag":94,"props":337,"children":339},{"id":338},"evidence-policy",[340],{"type":54,"value":341},"Evidence Policy",{"type":49,"tag":144,"props":343,"children":344},{},[345,350,355,360,365,370,375],{"type":49,"tag":148,"props":346,"children":347},{},[348],{"type":54,"value":349},"Hydrate PR details, comments, tasks, pipeline status, and diff only for stale,\nblocked, central, or high-impact PRs.",{"type":49,"tag":148,"props":351,"children":352},{},[353],{"type":54,"value":354},"For PR rollups, stop after the evidence set identifies the main themes,\nrepos\u002Fservices, owners, and recency. Do not keep searching for more PRs when\nthe next batch would only add more examples of the same theme.",{"type":49,"tag":148,"props":356,"children":357},{},[358],{"type":54,"value":359},"For review status, include age, requested reviewers, comments\u002Ftasks, approval\nstate, CI\u002Fcheck or pipeline state, and last activity when the provider surface\nexposes them.",{"type":49,"tag":148,"props":361,"children":362},{},[363],{"type":54,"value":364},"For repo\u002Fteam reports, group by repo, service, or workstream rather than only\nperson counts.",{"type":49,"tag":148,"props":366,"children":367},{},[368],{"type":54,"value":369},"Inspect PR titles\u002Fdescriptions and linked issues to infer themes; do not rank\nsolely by PR count.",{"type":49,"tag":148,"props":371,"children":372},{},[373],{"type":54,"value":374},"Keep Bitbucket, GitHub connector\u002Ftool, and Atlassian auth failures separate.",{"type":49,"tag":148,"props":376,"children":377},{},[378],{"type":54,"value":379},"If PR graph or repo-wide query calls repeatedly fail, make one narrower\nfallback using known repos, people, workitems, or search anchors. If that also\nfails, answer from the successful evidence and call out the PR coverage gap.",{"type":49,"tag":94,"props":381,"children":383},{"id":382},"recipe-cards",[384],{"type":54,"value":385},"Recipe Cards",{"type":49,"tag":387,"props":388,"children":390},"h3",{"id":389},"review-queue",[391],{"type":54,"value":392},"Review Queue",{"type":49,"tag":56,"props":394,"children":395},{},[396],{"type":54,"value":397},"Query reviewer-scoped open PRs. Sort by waiting time, requested action,\nunresolved tasks\u002Fcomments, failing CI, and project relevance. Hydrate only PRs\nthat need action.",{"type":49,"tag":387,"props":399,"children":401},{"id":400},"stale-reviews-review-bottlenecks",[402],{"type":54,"value":403},"Stale Reviews \u002F Review Bottlenecks",{"type":49,"tag":56,"props":405,"children":406},{},[407],{"type":54,"value":408},"Find PRs open or waiting beyond the threshold. Group by repo, author, reviewer,\nand stage. Identify bottleneck patterns such as missing reviewer, unresolved\ntasks, failing CI, repeated request-changes, or owner unavailable.",{"type":49,"tag":387,"props":410,"children":412},{"id":411},"issue-prs",[413],{"type":54,"value":414},"Issue PRs",{"type":49,"tag":56,"props":416,"children":417},{},[418],{"type":54,"value":419},"Use workitem context to find linked PRs, commits, branches, and repos. Fetch PRs\nonly if the user asks for details, status, or next action.",{"type":49,"tag":387,"props":421,"children":423},{"id":422},"repo-contributors-hot-areas",[424],{"type":54,"value":425},"Repo Contributors \u002F Hot Areas",{"type":49,"tag":56,"props":427,"children":428},{},[429],{"type":54,"value":430},"Query PRs\u002Fcommits for the repo and time window. Group by files\u002Fareas, authors,\nreviewers, and themes. For hot areas, prioritize changed area plus frequency and\nownership signals.",{"type":49,"tag":387,"props":432,"children":434},{"id":433},"pr-based-status-rollup",[435],{"type":54,"value":436},"PR-Based Status Rollup",{"type":49,"tag":56,"props":438,"children":439},{},[440,442,447,449,454],{"type":54,"value":441},"Resolve org\u002Fteam first, then collect PRs for members or repos in the time window.\nGroup into themes and repos\u002Fservices. Call out gaps where PR-only evidence omits\nJira, docs, planning, or customer context.\nFor a single person where the prompt is broader than PRs, switch to\n",{"type":49,"tag":62,"props":443,"children":445},{"className":444},[],[446],{"type":54,"value":296},{"type":54,"value":448}," and load\n",{"type":49,"tag":62,"props":450,"children":452},{"className":451},[],[453],{"type":54,"value":333},{"type":54,"value":92},{"type":49,"tag":94,"props":456,"children":458},{"id":457},"output-shape",[459],{"type":54,"value":460},"Output Shape",{"type":49,"tag":56,"props":462,"children":463},{},[464],{"type":54,"value":465},"For queues, include PR, repo, owner, state, reason, next action, and evidence.\nFor engineering reports, summarize workstreams, contributors, bottlenecks,\nrisks, and gaps. Include stable URLs or IDs for key artifacts.",{"type":49,"tag":94,"props":467,"children":469},{"id":468},"anti-patterns",[470],{"type":54,"value":471},"Anti-Patterns",{"type":49,"tag":144,"props":473,"children":474},{},[475,480,485,490],{"type":49,"tag":148,"props":476,"children":477},{},[478],{"type":54,"value":479},"Do not guess Bitbucket workspace or repo.",{"type":49,"tag":148,"props":481,"children":482},{},[483],{"type":54,"value":484},"Do not fetch every PR body, diff, or comment in a large queue.",{"type":49,"tag":148,"props":486,"children":487},{},[488],{"type":54,"value":489},"Do not treat PR counts as impact.",{"type":49,"tag":148,"props":491,"children":492},{},[493],{"type":54,"value":494},"Do not mix Bitbucket, GitHub connector\u002Ftool, and Atlassian auth failures.",{"items":496,"total":677},[497,518,536,553,568,579,594,612,627,639,653,663],{"slug":498,"name":498,"fn":499,"description":500,"org":501,"tags":502,"stars":515,"repoUrl":516,"updatedAt":517},"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},[503,506,509,512],{"name":504,"slug":505,"type":15},"Automation","automation",{"name":507,"slug":508,"type":15},"Jira","jira",{"name":510,"slug":511,"type":15},"Meetings","meetings",{"name":513,"slug":514,"type":15},"Task Management","task-management",848,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fatlassian-mcp-server","2026-07-12T07:58:45.323861",{"slug":519,"name":519,"fn":520,"description":521,"org":522,"tags":523,"stars":515,"repoUrl":516,"updatedAt":535},"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},[524,525,528,529,532],{"name":9,"slug":8,"type":15},{"name":526,"slug":527,"type":15},"Confluence","confluence",{"name":507,"slug":508,"type":15},{"name":530,"slug":531,"type":15},"Project Management","project-management",{"name":533,"slug":534,"type":15},"Reporting","reporting","2026-07-12T07:58:38.457696",{"slug":537,"name":537,"fn":538,"description":539,"org":540,"tags":541,"stars":515,"repoUrl":516,"updatedAt":552},"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},[542,545,548,549],{"name":543,"slug":544,"type":15},"Agile","agile",{"name":546,"slug":547,"type":15},"Dashboards","dashboards",{"name":507,"slug":508,"type":15},{"name":550,"slug":551,"type":15},"Sprint Planning","sprint-planning","2026-07-12T07:58:41.031798",{"slug":554,"name":554,"fn":555,"description":556,"org":557,"tags":558,"stars":515,"repoUrl":516,"updatedAt":567},"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},[559,560,563,564],{"name":526,"slug":527,"type":15},{"name":561,"slug":562,"type":15},"Enterprise Search","enterprise-search",{"name":507,"slug":508,"type":15},{"name":565,"slug":566,"type":15},"Knowledge Management","knowledge-management","2026-07-12T07:58:39.684132",{"slug":569,"name":569,"fn":570,"description":571,"org":572,"tags":573,"stars":515,"repoUrl":516,"updatedAt":578},"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},[574,575,576,577],{"name":543,"slug":544,"type":15},{"name":526,"slug":527,"type":15},{"name":507,"slug":508,"type":15},{"name":530,"slug":531,"type":15},"2026-07-12T07:58:37.200385",{"slug":580,"name":580,"fn":581,"description":582,"org":583,"tags":584,"stars":515,"repoUrl":516,"updatedAt":593},"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},[585,588,589,590],{"name":586,"slug":587,"type":15},"Debugging","debugging",{"name":507,"slug":508,"type":15},{"name":530,"slug":531,"type":15},{"name":591,"slug":592,"type":15},"Triage","triage","2026-07-12T07:58:33.007343",{"slug":595,"name":595,"fn":596,"description":597,"org":598,"tags":599,"stars":609,"repoUrl":610,"updatedAt":611},"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},[600,601,603,606],{"name":9,"slug":8,"type":15},{"name":602,"slug":34,"type":15},"CLI",{"name":604,"slug":605,"type":15},"Deployment","deployment",{"name":607,"slug":608,"type":15},"Plugin Development","plugin-development",14,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fforge-skills","2026-07-12T07:58:52.007851",{"slug":613,"name":613,"fn":614,"description":615,"org":616,"tags":617,"stars":609,"repoUrl":610,"updatedAt":626},"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},[618,619,622,623],{"name":9,"slug":8,"type":15},{"name":620,"slug":621,"type":15},"Code Analysis","code-analysis",{"name":604,"slug":605,"type":15},{"name":624,"slug":625,"type":15},"QA","qa","2026-07-12T07:58:50.744672",{"slug":628,"name":628,"fn":629,"description":630,"org":631,"tags":632,"stars":609,"repoUrl":610,"updatedAt":638},"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},[633,636,637],{"name":634,"slug":635,"type":15},"API Development","api-development",{"name":20,"slug":21,"type":15},{"name":561,"slug":562,"type":15},"2026-07-12T07:58:48.520248",{"slug":640,"name":640,"fn":641,"description":642,"org":643,"tags":644,"stars":609,"repoUrl":610,"updatedAt":652},"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},[645,646,649],{"name":9,"slug":8,"type":15},{"name":647,"slug":648,"type":15},"Cost Optimization","cost-optimization",{"name":650,"slug":651,"type":15},"Operations","operations","2026-07-12T07:58:53.557299",{"slug":654,"name":654,"fn":655,"description":656,"org":657,"tags":658,"stars":609,"repoUrl":610,"updatedAt":662},"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},[659,660,661],{"name":9,"slug":8,"type":15},{"name":586,"slug":587,"type":15},{"name":604,"slug":605,"type":15},"2026-07-12T07:58:47.226713",{"slug":664,"name":664,"fn":665,"description":666,"org":667,"tags":668,"stars":609,"repoUrl":610,"updatedAt":676},"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},[669,672,673],{"name":670,"slug":671,"type":15},"Audit","audit",{"name":620,"slug":621,"type":15},{"name":674,"slug":675,"type":15},"Security","security","2026-07-12T07:58:54.806538",24,{"items":679,"total":761},[680,689,702,717,730,743,751],{"slug":37,"name":37,"fn":681,"description":682,"org":683,"tags":684,"stars":26,"repoUrl":27,"updatedAt":688},"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},[685,686,687],{"name":9,"slug":8,"type":15},{"name":504,"slug":505,"type":15},{"name":602,"slug":34,"type":15},"2026-07-25T05:31:49.287124",{"slug":690,"name":690,"fn":691,"description":692,"org":693,"tags":694,"stars":26,"repoUrl":27,"updatedAt":701},"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},[695,696,697,698],{"name":9,"slug":8,"type":15},{"name":561,"slug":562,"type":15},{"name":565,"slug":566,"type":15},{"name":699,"slug":700,"type":15},"Research","research","2026-07-25T05:56:27.582838",{"slug":703,"name":703,"fn":704,"description":705,"org":706,"tags":707,"stars":26,"repoUrl":27,"updatedAt":716},"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},[708,711,712,715],{"name":709,"slug":710,"type":15},"A\u002FB Testing","a-b-testing",{"name":9,"slug":8,"type":15},{"name":713,"slug":714,"type":15},"MCP","mcp",{"name":699,"slug":700,"type":15},"2026-07-22T05:36:16.491486",{"slug":718,"name":718,"fn":719,"description":720,"org":721,"tags":722,"stars":26,"repoUrl":27,"updatedAt":729},"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},[723,724,725,728],{"name":9,"slug":8,"type":15},{"name":526,"slug":527,"type":15},{"name":726,"slug":727,"type":15},"Documents","documents",{"name":565,"slug":566,"type":15},"2026-07-25T05:31:47.271484",{"slug":731,"name":731,"fn":732,"description":733,"org":734,"tags":735,"stars":26,"repoUrl":27,"updatedAt":742},"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},[736,737,738,739],{"name":9,"slug":8,"type":15},{"name":565,"slug":566,"type":15},{"name":699,"slug":700,"type":15},{"name":740,"slug":741,"type":15},"Search","search","2026-07-25T05:31:51.299922",{"slug":4,"name":4,"fn":5,"description":6,"org":744,"tags":745,"stars":26,"repoUrl":27,"updatedAt":28},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[746,747,748,749,750],{"name":9,"slug":8,"type":15},{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},{"name":24,"slug":25,"type":15},{"slug":752,"name":752,"fn":753,"description":754,"org":755,"tags":756,"stars":26,"repoUrl":27,"updatedAt":760},"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},[757,758,759],{"name":9,"slug":8,"type":15},{"name":507,"slug":508,"type":15},{"name":513,"slug":514,"type":15},"2026-07-25T05:31:46.279241",11]