[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXR5SQZSXTPXT9ADSP3DXC":3,"skill-same:01M6DXR5SQZSXTPXT9ADSP3DXC":77},{"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":18,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":76},"01M6DXR5SQZSXTPXT9ADSP3DXC","attach-jira-issue",null,"Use this skill only when the user explicitly invokes \u002Fattach-jira-issue to upload one or more local files as attachments to a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Previews what will be uploaded and requires explicit confirmation before POSTing.","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\u002Fattach-jira-issue\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"attach jira issue","issue","jira","attach","files","when","local files","effects","jira-issue","true","more","as","posting","local","upload","only","never","auto","use","write","read","confirmation","Bash","attachments","write skill","file","2026-11-10 10:12:30",false,"---\nname: attach-jira-issue\ndescription: >\n  Use this skill only when the user explicitly invokes \u002Fattach-jira-issue to\n  upload one or more local files as attachments to a Jira issue. This is a\n  write skill with irreversible side effects — it must never be auto-invoked\n  from conversational context. Previews what will be uploaded and requires\n  explicit confirmation before POSTing.\nargument-hint: \"ISSUE-KEY FILE [FILE...]\"\ndisable-model-invocation: true\nallowed-tools:\n  - Bash\n  - Read\n  - Write\n---\n\n# Attach files to a Jira Issue\n\n!`accelerator config context --skill attach-jira-issue --fail-safe`\n\nUpload one or more local files as attachments to a Jira issue. Work through\nthe steps below in order. This skill never auto-invokes — it only runs when\nthe user explicitly types `\u002Fattach-jira-issue`.\n\n## Step 1: Parse flags\n\nRequired:\n- `KEY` — issue key (first positional), e.g. `ENG-42`\n- `FILE [FILE...]` — one or more local file paths to upload\n\n## Step 2: Preview the resolved intent\n\nShow, under **Proposed Jira write — review before sending**:\n\n- `POST` attachments to `\u003CKEY>`;\n- the file list: for each path, run `wc -c \u003Cpath>` via Bash and show the\n  basename with a humanised size (≥ 1 048 576 bytes → MB, ≥ 1 024 bytes → KB,\n  otherwise bytes). A missing or unreadable path is surfaced here — say which\n  file could not be read and stop, making no API call.\n- ⚠️ \"Attachments cannot be removed by this skill once uploaded.\"\n\n## Step 3: Confirm before writing\n\nAsk the user:\n\n> Send this to Jira? Reply **y** to confirm, **n** to revise, anything else to\n> abort.\n\nA clear `y`\u002F`yes` proceeds; a `n`\u002Frevise stays in review (typically different\npaths or a different key); anything ambiguous aborts with \"Aborted — no Jira\nwrite was made.\"\n\n## Step 4: Send the request\n\n```\naccelerator jira attach \u003CKEY> \u003CFILE> [FILE...]\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.\n\n## Step 5: Render the response\n\nOn success the subcommand emits the attachments as a JSON array (it carries no\noutcome envelope — success is the clean, zero-status run). For each element show\nthe filename, id, and humanised size (same KB\u002FMB logic as Step 2):\n\n```\n✓ Attached to \u003CKEY>:\n- \u003Cfilename> (ID: \u003Cid>, \u003Chumanised-size>)\n```\n\nIf the array is empty or unparseable, tell the user \"Upload succeeded but the\nresponse was empty or unreadable.\" On a non-zero exit, show the error — a\nmissing\u002Funreadable file or a credential failure names its cause on stderr;\nsuggest `\u002Finit-jira` for a credential failure.\n\n## Examples\n\n**Example — single file**\nUser: `\u002Fattach-jira-issue ENG-42 .\u002Fscreenshot.png`\nSkill previews the upload (`screenshot.png`, e.g. 84.3 KB), waits for `y`,\nuploads, and confirms with the returned id and size.\n\n!`accelerator config instructions attach-jira-issue --fail-safe`\n","# Attach files to a Jira Issue\n\n!`accelerator config context --skill attach-jira-issue --fail-safe`\n\nUpload one or more local files as attachments to a Jira issue. Work through\nthe steps below in order. This skill never auto-invokes — it only runs when\nthe user explicitly types `\u002Fattach-jira-issue`.\n\n## Step 1: Parse flags\n\nRequired:\n- `KEY` — issue key (first positional), e.g. `ENG-42`\n- `FILE [FILE...]` — one or more local file paths to upload\n\n## Step 2: Preview the resolved intent\n\nShow, under **Proposed Jira write — review before sending**:\n\n- `POST` attachments to `\u003CKEY>`;\n- the file list: for each path, run `wc -c \u003Cpath>` via Bash and show the\n  basename with a humanised size (≥ 1 048 576 bytes → MB, ≥ 1 024 bytes → KB,\n  otherwise bytes). A missing or unreadable path is surfaced here — say which\n  file could not be read and stop, making no API call.\n- ⚠️ \"Attachments cannot be removed by this skill once uploaded.\"\n\n## Step 3: Confirm before writing\n\nAsk the user:\n\n> Send this to Jira? Reply **y** to confirm, **n** to revise, anything else to\n> abort.\n\nA clear `y`\u002F`yes` proceeds; a `n`\u002Frevise stays in review (typically different\npaths or a different key); anything ambiguous aborts with \"Aborted — no Jira\nwrite was made.\"\n\n## Step 4: Send the request\n\n```\naccelerator jira attach \u003CKEY> \u003CFILE> [FILE...]\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.\n\n## Step 5: Render the response\n\nOn success the subcommand emits the attachments as a JSON array (it carries no\noutcome envelope — success is the clean, zero-status run). For each element show\nthe filename, id, and humanised size (same KB\u002FMB logic as Step 2):\n\n```\n✓ Attached to \u003CKEY>:\n- \u003Cfilename> (ID: \u003Cid>, \u003Chumanised-size>)\n```\n\nIf the array is empty or unparseable, tell the user \"Upload succeeded but the\nresponse was empty or unreadable.\" On a non-zero exit, show the error — a\nmissing\u002Funreadable file or a credential failure names its cause on stderr;\nsuggest `\u002Finit-jira` for a credential failure.\n\n## Examples\n\n**Example — single file**\nUser: `\u002Fattach-jira-issue ENG-42 .\u002Fscreenshot.png`\nSkill previews the upload (`screenshot.png`, e.g. 84.3 KB), waits for `y`,\nuploads, and confirms with the returned id and size.\n\n!`accelerator config instructions attach-jira-issue --fail-safe`\n",{"name":5,"description":50,"allowed-tools":51,"argument-hint":54,"disable-model-invocation":55},"Use this skill only when the user explicitly invokes \u002Fattach-jira-issue to upload one or more local files as attachments to a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Previews what will be uploaded and requires explicit confirmation before POSTing.\n",[41,52,53],"Read","Write","ISSUE-KEY FILE [FILE...]",true,"main","007b2dd695b63c2f097cdc40e54229b6e8b4596a","skills\u002Fintegrations\u002Fjira\u002Fattach-jira-issue",2,"https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator","https:\u002F\u002Fgo-atomic.io","https:\u002F\u002Fgithub.com\u002Fatomicinnovation","2026-11-10 21:05:37",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":55},[66,69,72],{"tool":67,"command":68},"npx","npx skills add atomicinnovation\u002Faccelerator --skill attach-jira-issue",{"tool":70,"command":71},"bunx","bunx skills add atomicinnovation\u002Faccelerator --skill attach-jira-issue",{"tool":73,"command":74},"pnpm","pnpm dlx skills add atomicinnovation\u002Faccelerator --skill attach-jira-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fintegrations\u002Fjira\u002Fattach-jira-issue\u002FSKILL.md",[],[78,113,137,156,172,197],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":94,"publishedAt":45},"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",[84,89],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[95,96,97,98,99,100,101,102,103,104,24,105,106,41,107,108,109,110,111,112],"explore pr","explore","pr","diagrams","exploration","re","review findings","walkthrough","design","map","number","URL","code","architecture","reviewer","review","notes","change",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":45},"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",[],[120,121,122,123,124,125,37,41,112,126,127,128,129,130,131,132,133,134,135,136],"work","update","update work item","work item","enforcement","manage","config","edit","validate","status","transition","frontmatter","Existing","tags","changes","fields","op",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":45},"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",[],[120,144,145,146,147,32,34,41,148,112,149,150,151,21,152,153,154,126,155,131,24],"sync","sync work items","promote","Meta","preview","active","tracker","max","remote","create","adopt","reconcile",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":45},"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",[],[163,120,164,144,145,165,166,167,39,168,28,169,170,171],"sync work items recovery","recovery","work-items","for","terminal","person","false","orders","pending",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":45},"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",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000008","测试与质量",[182,183,120,184,123,185,186,187,188,189,190,41,191,192,126,128,193,194,195,105,196,131],"stress test","test","stress test work item","stress","scope","issues","edge","stress-test","acceptance","acceptance criteria","dependencies","implementation","grilling","user","gaps",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":45},"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",[],[110,120,204,123,205,206,37,41,44,207,126,128,193,195,208,24,209,210,131,211],"review work item","review work","escalation","quality","metadata","iterate","evaluate","path"]