[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXRW5KWDN7C1DC5TFDX9R6":3,"skill-same:01M6DXRW5KWDN7C1DC5TFDX9R6":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6DXRW5KWDN7C1DC5TFDX9R6","show-jira-issue",null,"Use this skill when the user asks about a specific Jira issue by key (e.g. PROJ-123, ENG-456) — for viewing the description, status, comments, transitions, or any other field. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' a key, or asks any direct question about an issue they reference. Do NOT trigger when an issue key appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.","atomicinnovation\u002Faccelerator","atomicinnovation","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F65866524?v=4","01M6DXP513JV585FN2QPNR6079","Atomic","01M6DXP55MPK99YVZ2HGMEN991",34,"MIT","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fintegrations\u002Fjira\u002Fshow-jira-issue\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"show jira issue","jira","show","issue","use","when","render","trigger","false","expand","me","do","up","code review","fetch","question","check","Bash","messages","code","release notes","notes","commit","review","2026-11-10 10:12:30",false,"---\nname: show-jira-issue\ndescription: >\n  Use this skill when the user asks about a specific Jira issue by key\n  (e.g. PROJ-123, ENG-456) — for viewing the description, status,\n  comments, transitions, or any other field. Trigger when the user says\n  'look up', 'check on', 'tell me about', 'what's on', or 'what is the\n  status of' a key, or asks any direct question about an issue they\n  reference. Do NOT trigger when an issue key appears incidentally inside\n  other prose (commit messages, code review comments, release notes),\n  where the user is talking about the issue rather than asking to fetch it.\nargument-hint: \"\u003CISSUE-KEY> [--fields a,b,c] [--expand a,b,c] [--comments N] [--render-adf|--no-render-adf]\"\ndisable-model-invocation: false\nallowed-tools:\n  - Bash(accelerator config *)\n  - Bash(accelerator jira *)\n---\n\n# Show Jira Issue\n\n!`accelerator config context --skill show-jira-issue --fail-safe`\n\nFetch and render a single Jira issue by key. Work through the steps below\nin order.\n\n## Step 1: Parse the issue key and flags\n\nThe first positional argument is the issue key (e.g. `ENG-42`, `PROJ-1234`).\nRemaining arguments are passed through to the subcommand as-is.\n\n`--render-adf` defaults to ON — single-issue reads are for humans, so rendered\nMarkdown is the natural output. Pass `--no-render-adf` verbatim if the user\nexplicitly asked for raw ADF or JSON.\n\n## Step 2: Fetch the issue\n\nRun the show subcommand with the key and any flags supplied:\n\n```\naccelerator jira show \u003CISSUE-KEY> [flags]\n```\n\nRun the bare launcher **directly** as an executable; never prefix it with\n`bash`\u002F`sh`\u002F`env` and never pipe its output (a wrapper prefix or a pipe escapes\nthe skill's `allowed-tools` permission and forces an unnecessary prompt).\n\nThe subcommand emits a JSON document with a top-level `outcome` keyword:\n`found` or `not-found`. On `not-found`, tell the user the issue was not found\nand check the key. On a non-zero exit, show the error — a credential or site\nfailure names an `E_*` cause on stderr; suggest `\u002Finit-jira`.\n\n## Step 3: Render the result\n\nParse the JSON response and present a human-readable summary from `.fields`:\n\n- **Heading**: `## KEY — Summary text`\n- **Fields block**: Status, Type, Priority, Assignee, Reporter (omit if absent).\n- **Description**: render inline as Markdown (already rendered when\n  `--render-adf` is on).\n- **Comments** (when `--comments N` was passed): render each comment as a\n  mini conversation block — author, timestamp, body.\n\nIf the `fields` object is sparse (e.g. `--fields summary,status` was used),\nonly render the fields that are present; do not invent missing ones.\n\n## Examples\n\n**Example 1 — look up an issue**\nUser: \"look up PROJ-1234\"\nSkill invokes:\n```\naccelerator jira show PROJ-1234\n```\nThen renders the issue with description as Markdown.\n\n**Example 2 — show recent comments**\nUser: \"what's the discussion on ENG-42 — show me the last few comments\"\nSkill invokes:\n```\naccelerator jira show ENG-42 --comments 5\n```\nThen renders the summary + last 5 comments as an inline conversation.\n\n**Example 3 — raw JSON escape hatch**\nUser: \"give me the raw JSON for ENG-42 — I'm piping it to jq\"\nSkill invokes:\n```\naccelerator jira show ENG-42 --no-render-adf\n```\nThen prints the response with ADF intact.\n\n!`accelerator config instructions show-jira-issue --fail-safe`\n","# Show Jira Issue\n\n!`accelerator config context --skill show-jira-issue --fail-safe`\n\nFetch and render a single Jira issue by key. Work through the steps below\nin order.\n\n## Step 1: Parse the issue key and flags\n\nThe first positional argument is the issue key (e.g. `ENG-42`, `PROJ-1234`).\nRemaining arguments are passed through to the subcommand as-is.\n\n`--render-adf` defaults to ON — single-issue reads are for humans, so rendered\nMarkdown is the natural output. Pass `--no-render-adf` verbatim if the user\nexplicitly asked for raw ADF or JSON.\n\n## Step 2: Fetch the issue\n\nRun the show subcommand with the key and any flags supplied:\n\n```\naccelerator jira show \u003CISSUE-KEY> [flags]\n```\n\nRun the bare launcher **directly** as an executable; never prefix it with\n`bash`\u002F`sh`\u002F`env` and never pipe its output (a wrapper prefix or a pipe escapes\nthe skill's `allowed-tools` permission and forces an unnecessary prompt).\n\nThe subcommand emits a JSON document with a top-level `outcome` keyword:\n`found` or `not-found`. On `not-found`, tell the user the issue was not found\nand check the key. On a non-zero exit, show the error — a credential or site\nfailure names an `E_*` cause on stderr; suggest `\u002Finit-jira`.\n\n## Step 3: Render the result\n\nParse the JSON response and present a human-readable summary from `.fields`:\n\n- **Heading**: `## KEY — Summary text`\n- **Fields block**: Status, Type, Priority, Assignee, Reporter (omit if absent).\n- **Description**: render inline as Markdown (already rendered when\n  `--render-adf` is on).\n- **Comments** (when `--comments N` was passed): render each comment as a\n  mini conversation block — author, timestamp, body.\n\nIf the `fields` object is sparse (e.g. `--fields summary,status` was used),\nonly render the fields that are present; do not invent missing ones.\n\n## Examples\n\n**Example 1 — look up an issue**\nUser: \"look up PROJ-1234\"\nSkill invokes:\n```\naccelerator jira show PROJ-1234\n```\nThen renders the issue with description as Markdown.\n\n**Example 2 — show recent comments**\nUser: \"what's the discussion on ENG-42 — show me the last few comments\"\nSkill invokes:\n```\naccelerator jira show ENG-42 --comments 5\n```\nThen renders the summary + last 5 comments as an inline conversation.\n\n**Example 3 — raw JSON escape hatch**\nUser: \"give me the raw JSON for ENG-42 — I'm piping it to jq\"\nSkill invokes:\n```\naccelerator jira show ENG-42 --no-render-adf\n```\nThen prints the response with ADF intact.\n\n!`accelerator config instructions show-jira-issue --fail-safe`\n",{"name":5,"description":53,"allowed-tools":54,"argument-hint":57,"disable-model-invocation":49},"Use this skill when the user asks about a specific Jira issue by key (e.g. PROJ-123, ENG-456) — for viewing the description, status, comments, transitions, or any other field. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' a key, or asks any direct question about an issue they reference. Do NOT trigger when an issue key appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.\n",[55,56],"Bash(accelerator config *)","Bash(accelerator jira *)","\u003CISSUE-KEY> [--fields a,b,c] [--expand a,b,c] [--comments N] [--render-adf|--no-render-adf]","main","007b2dd695b63c2f097cdc40e54229b6e8b4596a","skills\u002Fintegrations\u002Fjira\u002Fshow-jira-issue",2,"https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator","https:\u002F\u002Fgo-atomic.io","https:\u002F\u002Fgithub.com\u002Fatomicinnovation","2026-11-12 04:07:28",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add atomicinnovation\u002Faccelerator --skill show-jira-issue",{"tool":72,"command":73},"bunx","bunx skills add atomicinnovation\u002Faccelerator --skill show-jira-issue",{"tool":75,"command":76},"pnpm","pnpm dlx skills add atomicinnovation\u002Faccelerator --skill show-jira-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fintegrations\u002Fjira\u002Fshow-jira-issue\u002FSKILL.md",true,[80,86,92,96,101],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},".gitignore","OTHER","其他",30,"https:\u002F\u002Fgithub.com\u002Ffranklee16\u002Facademic-research-skills\u002Fblob\u002Fmaster\u002Fpresentations\u002FPaper-to-Presentation\u002F.gitignore",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"evals\u002Fbenchmark.json","REFERENCE","参考文档",2526,"https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fintegrations\u002Fjira\u002Fshow-jira-issue\u002Fevals\u002Fbenchmark.json",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"evals\u002Fevals.json",4099,"https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fintegrations\u002Fjira\u002Fshow-jira-issue\u002Fevals\u002Fevals.json",{"path":97,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"LICENSE","许可证",1072,"https:\u002F\u002Fgithub.com\u002Ffranklee16\u002Facademic-research-skills\u002Fblob\u002Fmaster\u002Fpresentations\u002FPaper-to-Presentation\u002FLICENSE",{"path":102,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":103,"sourceHtmlUrl":104},"README.md",5501,"https:\u002F\u002Fgithub.com\u002Ffranklee16\u002Facademic-research-skills\u002Fblob\u002Fmaster\u002Fpresentations\u002FPaper-to-Presentation\u002FREADME.md",[106,136,160,181,198,223],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":120,"publishedAt":48},"01M70S7PFGVATJREBFEGPJB718","explore-pr","Build an interactive, design-first and picture-first exploration page for a pull request — its architecture, abstractions and design decisions drawn as diagrams, a guided tour in reading order with code as the evidence, an attention map of where the risk sits, a ledger of its riskiest operations, prior review findings re-checked against the code, and simulations specific to the PR — with the reviewer's verdicts and notes saved. Use when the user wants to explore, understand or review a large pull request or its design, asks for a review page, walkthrough or visual explanation of a PR, or is struggling to review a big change.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fexplore-pr\u002FSKILL.md",[112,115],{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[121,122,123,124,125,126,127,128,129,130,29,131,132,41,43,133,134,47,45,135],"explore pr","explore","pr","diagrams","exploration","re","review findings","walkthrough","design","map","number","URL","architecture","reviewer","change",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":48},"01M6DY04WBTMFV96JMBP5ZXVFX","update-work-item","Update fields (status, priority, tags, parent, etc.) of an existing work item. Use to transition status, change priority, manage tags, or edit any frontmatter field. No transition enforcement — arbitrary changes are allowed.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fupdate-work-item\u002FSKILL.md",[],[143,144,145,146,147,148,28,41,135,149,150,151,152,153,154,155,156,157,158,159],"work","update","update work item","work item","enforcement","manage","config","edit","validate","status","transition","frontmatter","Existing","tags","changes","fields","op",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":48},"01M6DY0106CF15CYEJHZM14GBZ","sync-work-items","Reconcile local work items in meta\u002Fwork\u002F with the active remote tracker named by work.integration. Use when the user wants to sync, push, or pull work items to or from Jira or Linear, preview what a sync would change, or reconcile divergent local and remote state.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fsync-work-items\u002FSKILL.md",[],[143,167,168,169,170,171,172,41,173,135,174,175,176,25,177,178,179,149,180,154,29],"sync","sync work items","promote","Meta","local","only","preview","active","tracker","max","remote","create","adopt","reconcile",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":48},"01M6HNF86984S4XK21Q26VZA21","sync-work-items-recovery","Recovery procedures for work sync failures that need a person — terminal rows, refused pending pushes and refused orders. Read by sync-work-items — not invoked directly.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fsync-work-items-recovery\u002FSKILL.md",[],[188,143,189,167,168,190,191,192,193,194,195,32,196,197],"sync work items recovery","recovery","work-items","for","terminal","read","person","true","orders","pending",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":207,"publishedAt":48},"01M6DXZWH7PR72VCEXSSD4XNK4","stress-test-work-item","Interactively stress-test a work item by grilling the user on scope, assumptions, acceptance criteria, edge cases, and dependencies to surface issues, gaps, and flawed assumptions before implementation is planned.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fstress-test-work-item\u002FSKILL.md",[204],{"categoryNo":205,"categoryName":206,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[208,209,143,210,146,211,212,213,214,215,216,41,217,218,149,151,219,220,221,131,222,154],"stress test","test","stress test work item","stress","scope","issues","edge","stress-test","acceptance","acceptance criteria","dependencies","implementation","grilling","user","gaps",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":48},"01M6DXZRQWHTWV1G9PTTHCGGYA","review-work-item","Review a work item through multiple quality lenses and collaboratively iterate based on findings. Use when the user wants to evaluate a work item before implementation or escalation.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Freview-work-item\u002FSKILL.md",[],[47,143,230,146,231,232,28,41,233,234,149,151,219,221,235,29,236,237,154,238],"review work item","review work","escalation","file","quality","metadata","iterate","evaluate","path"]