[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-atlassian-twg-responsibility-routing":3,"mdc--jxhxg8-key":40,"related-org-atlassian-twg-responsibility-routing":348,"related-repo-atlassian-twg-responsibility-routing":529},{"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-responsibility-routing","route engineering responsibilities and escalations","Use with root `twg` to route owners, subject-matter experts, maintainers, reviewers, approvers, decision authorities, Heads of Engineering, or escalation paths for a topic, area, ask, project, service, or component.\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},"Operations","operations","tag",{"name":17,"slug":18,"type":15},"Management","management",{"name":20,"slug":21,"type":15},"Engineering","engineering",{"name":9,"slug":8,"type":15},6,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Ftwg-cli","2026-07-25T05:56:26.912395",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-responsibility-routing","---\nname: twg-responsibility-routing\ndescription: >\n  Use with root `twg` to route owners, subject-matter experts, maintainers,\n  reviewers, approvers, decision authorities, Heads of Engineering, or\n  escalation paths for a topic, area, ask, project, service, or component.\n---\n\n# twg-responsibility-routing\n\nUse the root `twg` skill. Use this workflow to answer “who should I involve,\nwhy them, and in what role?” Do not assume a broad topic is an exact product.\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## Classify The Role\n\nKeep these roles distinct:\n\n- **Declared owner**: formally accountable for an entity or area.\n- **Operational owner or maintainer**: responsible for current delivery or operation.\n- **Expert**: has source-backed depth in one workstream.\n- **Reviewer or consulted party**: evaluates or advises but may not decide.\n- **Approver or decision authority**: can authorize the specific ask or decision.\n- **Escalation or Head of Engineering contact**: leads the responsible engineering\n  organization or can route an unresolved ask.\n- **Informed stakeholder**: affected by the decision but not responsible for it.\n\n## Resolve Scope Before People\n\nFor a fuzzy topic or area, compare one bounded\n`twg search \"\u003Ctopic>\" --app confluence` pass with one bounded\n`twg work search \"\u003Ctopic>\"` pass. Group same-named results into distinct\ninitiative, platform, domain, feature, and team clusters. Hydrate 2-5 central\ncharters, roadmaps, services, projects, or active workstreams before ranking\npeople. If the sources disagree, show the alternative scopes or ask the user.\n\nFor a stable project, goal, component, service, work item, page, or repository,\nuse that reference directly.\n\n## Find Responsibility And Authority\n\n- Use `twg responsibility get \u003Creference>` for declared owners, teams,\n  maintainers, approvers, reviewers, or escalation roles.\n- Use `twg responsibility infer \u003Creference>` only when declared responsibility\n  is missing or the user asks for evidence-based candidates. Preserve confidence,\n  reason codes, evidence window, and declared-versus-observed status.\n- Infer primarily from scoped search, declared roles, and hydrated work evidence.\n  Org data is optional; do not block or weaken the workflow merely because it is\n  unavailable.\n- When org data is connected and a candidate leader or manager is known, prefer\n  the narrowest useful tree: `org-tree` for hierarchy, `work-tree` for\n  cross-surface breadth, `workitem-tree` for Jira work, or `pr-tree` for PR\n  authorship\u002Freview. Tree counts help validate reach and organizational scope;\n  they do not by themselves prove expertise, ownership, or approval authority.\n- For an approval ask, inspect the artifact that defines the decision: project or\n  goal ownership, Jira workflow\u002Fapprover fields, charter, decision record, or\n  accountable team. State separately who can recommend, who must be consulted,\n  and who can approve. Never promote an active contributor into an approver.\n- For escalation, give the nearest verified owner first. Add the engineering\n  leader only when the owner is missing, blocked, cross-team, or the ask needs\n  organizational authority.\n\nUse `twg-context-discovery` only when relationship or dependency expansion is\nneeded after the scope and people roles are established. It is not the default\nroute for a responsibility question.\n\n## Evidence And Output\n\nStrong evidence includes explicit ownership, accountable roles, workflow\nauthority, charter\u002Froadmap leadership, service ownership, sustained decisions,\nor repeated central contributions. Profile text, org proximity, one document,\nraw activity, or a self-authored update is weak evidence by itself.\n\nFor topic\u002FSME maps, return at most five workstreams and one primary expert per\nworkstream unless the user asks for more. Name an overall owner only with\ncross-workstream evidence. For approval or escalation asks, return the proposed\ncontact, role, scope, evidence, confidence, why they are appropriate, and a\nsuggested question or reach-out. State when authority is unconfirmed.\n\nStop when another search would not change scope, role, authority, escalation,\nconfidence, or the recommended contact.\n",{"data":41,"body":42},{"name":4,"description":6},{"type":43,"children":44},"root",[45,52,66,73,110,116,121,197,203,224,229,235,315,327,333,338,343],{"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],{"type":51,"value":57},"Use the root ",{"type":46,"tag":59,"props":60,"children":62},"code",{"className":61},[],[63],{"type":51,"value":34},{"type":51,"value":65}," skill. Use this workflow to answer “who should I involve,\nwhy them, and in what role?” Do not assume a broad topic is an exact product.",{"type":46,"tag":67,"props":68,"children":70},"h2",{"id":69},"cli-launcher-fallback",[71],{"type":51,"value":72},"CLI launcher fallback",{"type":46,"tag":53,"props":74,"children":75},{},[76,78,84,86,92,94,100,102,108],{"type":51,"value":77},"Run ",{"type":46,"tag":59,"props":79,"children":81},{"className":80},[],[82],{"type":51,"value":83},"twg \u003Ccommand>",{"type":51,"value":85},". On shell ",{"type":46,"tag":59,"props":87,"children":89},{"className":88},[],[90],{"type":51,"value":91},"command not found",{"type":51,"value":93},", use ",{"type":46,"tag":59,"props":95,"children":97},{"className":96},[],[98],{"type":51,"value":99},"$HOME\u002F.local\u002Fbin\u002Ftwg",{"type":51,"value":101},"\n(macOS\u002FLinux) \u002F ",{"type":46,"tag":59,"props":103,"children":105},{"className":104},[],[106],{"type":51,"value":107},"$env:LOCALAPPDATA\\Programs\\twg\\bin\\twg.exe",{"type":51,"value":109}," (PowerShell), then\ntell user to add that directory to PATH. Do not treat auth or command errors as\nPATH failures.",{"type":46,"tag":67,"props":111,"children":113},{"id":112},"classify-the-role",[114],{"type":51,"value":115},"Classify The Role",{"type":46,"tag":53,"props":117,"children":118},{},[119],{"type":51,"value":120},"Keep these roles distinct:",{"type":46,"tag":122,"props":123,"children":124},"ul",{},[125,137,147,157,167,177,187],{"type":46,"tag":126,"props":127,"children":128},"li",{},[129,135],{"type":46,"tag":130,"props":131,"children":132},"strong",{},[133],{"type":51,"value":134},"Declared owner",{"type":51,"value":136},": formally accountable for an entity or area.",{"type":46,"tag":126,"props":138,"children":139},{},[140,145],{"type":46,"tag":130,"props":141,"children":142},{},[143],{"type":51,"value":144},"Operational owner or maintainer",{"type":51,"value":146},": responsible for current delivery or operation.",{"type":46,"tag":126,"props":148,"children":149},{},[150,155],{"type":46,"tag":130,"props":151,"children":152},{},[153],{"type":51,"value":154},"Expert",{"type":51,"value":156},": has source-backed depth in one workstream.",{"type":46,"tag":126,"props":158,"children":159},{},[160,165],{"type":46,"tag":130,"props":161,"children":162},{},[163],{"type":51,"value":164},"Reviewer or consulted party",{"type":51,"value":166},": evaluates or advises but may not decide.",{"type":46,"tag":126,"props":168,"children":169},{},[170,175],{"type":46,"tag":130,"props":171,"children":172},{},[173],{"type":51,"value":174},"Approver or decision authority",{"type":51,"value":176},": can authorize the specific ask or decision.",{"type":46,"tag":126,"props":178,"children":179},{},[180,185],{"type":46,"tag":130,"props":181,"children":182},{},[183],{"type":51,"value":184},"Escalation or Head of Engineering contact",{"type":51,"value":186},": leads the responsible engineering\norganization or can route an unresolved ask.",{"type":46,"tag":126,"props":188,"children":189},{},[190,195],{"type":46,"tag":130,"props":191,"children":192},{},[193],{"type":51,"value":194},"Informed stakeholder",{"type":51,"value":196},": affected by the decision but not responsible for it.",{"type":46,"tag":67,"props":198,"children":200},{"id":199},"resolve-scope-before-people",[201],{"type":51,"value":202},"Resolve Scope Before People",{"type":46,"tag":53,"props":204,"children":205},{},[206,208,214,216,222],{"type":51,"value":207},"For a fuzzy topic or area, compare one bounded\n",{"type":46,"tag":59,"props":209,"children":211},{"className":210},[],[212],{"type":51,"value":213},"twg search \"\u003Ctopic>\" --app confluence",{"type":51,"value":215}," pass with one bounded\n",{"type":46,"tag":59,"props":217,"children":219},{"className":218},[],[220],{"type":51,"value":221},"twg work search \"\u003Ctopic>\"",{"type":51,"value":223}," pass. Group same-named results into distinct\ninitiative, platform, domain, feature, and team clusters. Hydrate 2-5 central\ncharters, roadmaps, services, projects, or active workstreams before ranking\npeople. If the sources disagree, show the alternative scopes or ask the user.",{"type":46,"tag":53,"props":225,"children":226},{},[227],{"type":51,"value":228},"For a stable project, goal, component, service, work item, page, or repository,\nuse that reference directly.",{"type":46,"tag":67,"props":230,"children":232},{"id":231},"find-responsibility-and-authority",[233],{"type":51,"value":234},"Find Responsibility And Authority",{"type":46,"tag":122,"props":236,"children":237},{},[238,251,263,268,305,310],{"type":46,"tag":126,"props":239,"children":240},{},[241,243,249],{"type":51,"value":242},"Use ",{"type":46,"tag":59,"props":244,"children":246},{"className":245},[],[247],{"type":51,"value":248},"twg responsibility get \u003Creference>",{"type":51,"value":250}," for declared owners, teams,\nmaintainers, approvers, reviewers, or escalation roles.",{"type":46,"tag":126,"props":252,"children":253},{},[254,255,261],{"type":51,"value":242},{"type":46,"tag":59,"props":256,"children":258},{"className":257},[],[259],{"type":51,"value":260},"twg responsibility infer \u003Creference>",{"type":51,"value":262}," only when declared responsibility\nis missing or the user asks for evidence-based candidates. Preserve confidence,\nreason codes, evidence window, and declared-versus-observed status.",{"type":46,"tag":126,"props":264,"children":265},{},[266],{"type":51,"value":267},"Infer primarily from scoped search, declared roles, and hydrated work evidence.\nOrg data is optional; do not block or weaken the workflow merely because it is\nunavailable.",{"type":46,"tag":126,"props":269,"children":270},{},[271,273,279,281,287,289,295,297,303],{"type":51,"value":272},"When org data is connected and a candidate leader or manager is known, prefer\nthe narrowest useful tree: ",{"type":46,"tag":59,"props":274,"children":276},{"className":275},[],[277],{"type":51,"value":278},"org-tree",{"type":51,"value":280}," for hierarchy, ",{"type":46,"tag":59,"props":282,"children":284},{"className":283},[],[285],{"type":51,"value":286},"work-tree",{"type":51,"value":288}," for\ncross-surface breadth, ",{"type":46,"tag":59,"props":290,"children":292},{"className":291},[],[293],{"type":51,"value":294},"workitem-tree",{"type":51,"value":296}," for Jira work, or ",{"type":46,"tag":59,"props":298,"children":300},{"className":299},[],[301],{"type":51,"value":302},"pr-tree",{"type":51,"value":304}," for PR\nauthorship\u002Freview. Tree counts help validate reach and organizational scope;\nthey do not by themselves prove expertise, ownership, or approval authority.",{"type":46,"tag":126,"props":306,"children":307},{},[308],{"type":51,"value":309},"For an approval ask, inspect the artifact that defines the decision: project or\ngoal ownership, Jira workflow\u002Fapprover fields, charter, decision record, or\naccountable team. State separately who can recommend, who must be consulted,\nand who can approve. Never promote an active contributor into an approver.",{"type":46,"tag":126,"props":311,"children":312},{},[313],{"type":51,"value":314},"For escalation, give the nearest verified owner first. Add the engineering\nleader only when the owner is missing, blocked, cross-team, or the ask needs\norganizational authority.",{"type":46,"tag":53,"props":316,"children":317},{},[318,319,325],{"type":51,"value":242},{"type":46,"tag":59,"props":320,"children":322},{"className":321},[],[323],{"type":51,"value":324},"twg-context-discovery",{"type":51,"value":326}," only when relationship or dependency expansion is\nneeded after the scope and people roles are established. It is not the default\nroute for a responsibility question.",{"type":46,"tag":67,"props":328,"children":330},{"id":329},"evidence-and-output",[331],{"type":51,"value":332},"Evidence And Output",{"type":46,"tag":53,"props":334,"children":335},{},[336],{"type":51,"value":337},"Strong evidence includes explicit ownership, accountable roles, workflow\nauthority, charter\u002Froadmap leadership, service ownership, sustained decisions,\nor repeated central contributions. Profile text, org proximity, one document,\nraw activity, or a self-authored update is weak evidence by itself.",{"type":46,"tag":53,"props":339,"children":340},{},[341],{"type":51,"value":342},"For topic\u002FSME maps, return at most five workstreams and one primary expert per\nworkstream unless the user asks for more. Name an overall owner only with\ncross-workstream evidence. For approval or escalation asks, return the proposed\ncontact, role, scope, evidence, confidence, why they are appropriate, and a\nsuggested question or reach-out. State when authority is unconfirmed.",{"type":46,"tag":53,"props":344,"children":345},{},[346],{"type":51,"value":347},"Stop when another search would not change scope, role, authority, escalation,\nconfidence, or the recommended contact.",{"items":349,"total":528},[350,371,389,406,421,432,447,465,480,492,504,514],{"slug":351,"name":351,"fn":352,"description":353,"org":354,"tags":355,"stars":368,"repoUrl":369,"updatedAt":370},"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},[356,359,362,365],{"name":357,"slug":358,"type":15},"Automation","automation",{"name":360,"slug":361,"type":15},"Jira","jira",{"name":363,"slug":364,"type":15},"Meetings","meetings",{"name":366,"slug":367,"type":15},"Task Management","task-management",848,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fatlassian-mcp-server","2026-07-12T07:58:45.323861",{"slug":372,"name":372,"fn":373,"description":374,"org":375,"tags":376,"stars":368,"repoUrl":369,"updatedAt":388},"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},[377,378,381,382,385],{"name":9,"slug":8,"type":15},{"name":379,"slug":380,"type":15},"Confluence","confluence",{"name":360,"slug":361,"type":15},{"name":383,"slug":384,"type":15},"Project Management","project-management",{"name":386,"slug":387,"type":15},"Reporting","reporting","2026-07-12T07:58:38.457696",{"slug":390,"name":390,"fn":391,"description":392,"org":393,"tags":394,"stars":368,"repoUrl":369,"updatedAt":405},"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},[395,398,401,402],{"name":396,"slug":397,"type":15},"Agile","agile",{"name":399,"slug":400,"type":15},"Dashboards","dashboards",{"name":360,"slug":361,"type":15},{"name":403,"slug":404,"type":15},"Sprint Planning","sprint-planning","2026-07-12T07:58:41.031798",{"slug":407,"name":407,"fn":408,"description":409,"org":410,"tags":411,"stars":368,"repoUrl":369,"updatedAt":420},"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},[412,413,416,417],{"name":379,"slug":380,"type":15},{"name":414,"slug":415,"type":15},"Enterprise Search","enterprise-search",{"name":360,"slug":361,"type":15},{"name":418,"slug":419,"type":15},"Knowledge Management","knowledge-management","2026-07-12T07:58:39.684132",{"slug":422,"name":422,"fn":423,"description":424,"org":425,"tags":426,"stars":368,"repoUrl":369,"updatedAt":431},"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},[427,428,429,430],{"name":396,"slug":397,"type":15},{"name":379,"slug":380,"type":15},{"name":360,"slug":361,"type":15},{"name":383,"slug":384,"type":15},"2026-07-12T07:58:37.200385",{"slug":433,"name":433,"fn":434,"description":435,"org":436,"tags":437,"stars":368,"repoUrl":369,"updatedAt":446},"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},[438,441,442,443],{"name":439,"slug":440,"type":15},"Debugging","debugging",{"name":360,"slug":361,"type":15},{"name":383,"slug":384,"type":15},{"name":444,"slug":445,"type":15},"Triage","triage","2026-07-12T07:58:33.007343",{"slug":448,"name":448,"fn":449,"description":450,"org":451,"tags":452,"stars":462,"repoUrl":463,"updatedAt":464},"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},[453,454,456,459],{"name":9,"slug":8,"type":15},{"name":455,"slug":31,"type":15},"CLI",{"name":457,"slug":458,"type":15},"Deployment","deployment",{"name":460,"slug":461,"type":15},"Plugin Development","plugin-development",14,"https:\u002F\u002Fgithub.com\u002Fatlassian\u002Fforge-skills","2026-07-12T07:58:52.007851",{"slug":466,"name":466,"fn":467,"description":468,"org":469,"tags":470,"stars":462,"repoUrl":463,"updatedAt":479},"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},[471,472,475,476],{"name":9,"slug":8,"type":15},{"name":473,"slug":474,"type":15},"Code Analysis","code-analysis",{"name":457,"slug":458,"type":15},{"name":477,"slug":478,"type":15},"QA","qa","2026-07-12T07:58:50.744672",{"slug":481,"name":481,"fn":482,"description":483,"org":484,"tags":485,"stars":462,"repoUrl":463,"updatedAt":491},"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},[486,489,490],{"name":487,"slug":488,"type":15},"API Development","api-development",{"name":20,"slug":21,"type":15},{"name":414,"slug":415,"type":15},"2026-07-12T07:58:48.520248",{"slug":493,"name":493,"fn":494,"description":495,"org":496,"tags":497,"stars":462,"repoUrl":463,"updatedAt":503},"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},[498,499,502],{"name":9,"slug":8,"type":15},{"name":500,"slug":501,"type":15},"Cost Optimization","cost-optimization",{"name":13,"slug":14,"type":15},"2026-07-12T07:58:53.557299",{"slug":505,"name":505,"fn":506,"description":507,"org":508,"tags":509,"stars":462,"repoUrl":463,"updatedAt":513},"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},[510,511,512],{"name":9,"slug":8,"type":15},{"name":439,"slug":440,"type":15},{"name":457,"slug":458,"type":15},"2026-07-12T07:58:47.226713",{"slug":515,"name":515,"fn":516,"description":517,"org":518,"tags":519,"stars":462,"repoUrl":463,"updatedAt":527},"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},[520,523,524],{"name":521,"slug":522,"type":15},"Audit","audit",{"name":473,"slug":474,"type":15},{"name":525,"slug":526,"type":15},"Security","security","2026-07-12T07:58:54.806538",24,{"items":530,"total":621},[531,540,553,568,581,593,611],{"slug":34,"name":34,"fn":532,"description":533,"org":534,"tags":535,"stars":23,"repoUrl":24,"updatedAt":539},"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},[536,537,538],{"name":9,"slug":8,"type":15},{"name":357,"slug":358,"type":15},{"name":455,"slug":31,"type":15},"2026-07-25T05:31:49.287124",{"slug":541,"name":541,"fn":542,"description":543,"org":544,"tags":545,"stars":23,"repoUrl":24,"updatedAt":552},"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},[546,547,548,549],{"name":9,"slug":8,"type":15},{"name":414,"slug":415,"type":15},{"name":418,"slug":419,"type":15},{"name":550,"slug":551,"type":15},"Research","research","2026-07-25T05:56:27.582838",{"slug":554,"name":554,"fn":555,"description":556,"org":557,"tags":558,"stars":23,"repoUrl":24,"updatedAt":567},"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},[559,562,563,566],{"name":560,"slug":561,"type":15},"A\u002FB Testing","a-b-testing",{"name":9,"slug":8,"type":15},{"name":564,"slug":565,"type":15},"MCP","mcp",{"name":550,"slug":551,"type":15},"2026-07-22T05:36:16.491486",{"slug":569,"name":569,"fn":570,"description":571,"org":572,"tags":573,"stars":23,"repoUrl":24,"updatedAt":580},"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},[574,575,576,579],{"name":9,"slug":8,"type":15},{"name":379,"slug":380,"type":15},{"name":577,"slug":578,"type":15},"Documents","documents",{"name":418,"slug":419,"type":15},"2026-07-25T05:31:47.271484",{"slug":324,"name":324,"fn":582,"description":583,"org":584,"tags":585,"stars":23,"repoUrl":24,"updatedAt":592},"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},[586,587,588,589],{"name":9,"slug":8,"type":15},{"name":418,"slug":419,"type":15},{"name":550,"slug":551,"type":15},{"name":590,"slug":591,"type":15},"Search","search","2026-07-25T05:31:51.299922",{"slug":594,"name":594,"fn":595,"description":596,"org":597,"tags":598,"stars":23,"repoUrl":24,"updatedAt":610},"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},[599,600,603,604,607],{"name":9,"slug":8,"type":15},{"name":601,"slug":602,"type":15},"Code Review","code-review",{"name":20,"slug":21,"type":15},{"name":605,"slug":606,"type":15},"GitHub","github",{"name":608,"slug":609,"type":15},"Pull Requests","pull-requests","2026-07-25T05:31:52.317362",{"slug":612,"name":612,"fn":613,"description":614,"org":615,"tags":616,"stars":23,"repoUrl":24,"updatedAt":620},"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},[617,618,619],{"name":9,"slug":8,"type":15},{"name":360,"slug":361,"type":15},{"name":366,"slug":367,"type":15},"2026-07-25T05:31:46.279241",11]