[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CJ7353SB24HXVNJYA912PC":3,"skill-same:01M6CJ7353SB24HXVNJYA912PC":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":63},"01M6CJ7353SB24HXVNJYA912PC","enter-issue",null,"Create a GitHub issue from screenshots, images, text descriptions, or any combination. Use this when the user wants to file a new issue or report a bug.","thefrederiksen\u002Fdevthrottle","thefrederiksen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F220024918?v=4","01M6CJ5XSV9624762E0FDS49BZ","01M6CJ5XY3WWF9943901Y87DEX",110,"MIT","https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fenter-issue\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"enter issue","issue","github issue","new","when","title","true","images","bug","screenshots","use","user","text","file","report","create","github","2026-11-10 10:12:30",false,"---\nname: enter-issue\ndescription: Create a GitHub issue from screenshots, images, text descriptions, or any combination. Use this when the user wants to file a new issue or report a bug.\ndisable-model-invocation: true\nargument-hint: [title or description]\n---\n\n# Create GitHub Issue\n\nCreate a new GitHub issue based on the user's input. The input may include screenshots, images, text descriptions, error logs, or any combination.\n\n## Input: $ARGUMENTS\n\n## Instructions\n\n1. **Gather context from the user's input:**\n   - Read any text description or title provided in `$ARGUMENTS`\n   - If the user has provided screenshot paths or image paths, read them using the Read tool to understand their content\n   - Common screenshot locations to check if referenced:\n     - `%USERPROFILE%\\Pictures\\Screenshots`\n     - `%OneDrive%\\Pictures\\Screenshots`\n   - If no title is provided, derive one from the description\u002Fimages\n\n2. **Collect additional information if needed:**\n   - If the description is vague, use AskUserQuestion to clarify:\n     - What is the expected behavior?\n     - What is the actual behavior?\n     - Steps to reproduce?\n     - Priority\u002Fseverity?\n   - If the user provided enough information, proceed without asking\n\n3. **Upload images to the issue:**\n   - If images\u002Fscreenshots were provided, they need to be included in the issue\n   - Use `gh issue create` which supports image references in markdown\n   - For local images, upload them by referencing in the issue body — GitHub CLI handles image uploads when you use the web editor, so instead embed image paths as attachments\n   - Strategy: Create the issue first, then use `gh issue edit` to add images if needed, OR reference images inline\n\n4. **Determine labels:**\n   - Check available labels: `gh label list`\n   - Apply appropriate labels (bug, enhancement, documentation, etc.)\n   - If no matching labels exist, create them if appropriate\n\n5. **Create the issue using GitHub CLI:**\n   ```\n   gh issue create --title \"TITLE\" --body \"BODY\" --label \"LABELS\"\n   ```\n   - Title: Clear, concise, imperative form (e.g., \"Fix crash when opening settings\")\n   - Body format:\n     ```markdown\n     ## Description\n     [Clear description of the issue]\n\n     ## Screenshots\n     [Any attached images]\n\n     ## Steps to Reproduce (if bug)\n     1. Step one\n     2. Step two\n\n     ## Expected Behavior\n     [What should happen]\n\n     ## Actual Behavior\n     [What actually happens]\n\n     ## Additional Context\n     [Any extra info, logs, environment details]\n     ```\n\n6. **Report back:**\n   - Show the created issue URL\n   - Show the issue number\n   - Summarize what was created\n\n## Important Notes\n- Always use `gh` CLI for GitHub operations\n- Use a HEREDOC for the body to preserve formatting:\n  ```bash\n  gh issue create --title \"Title\" --body \"$(cat \u003C\u003C'EOF'\n  ## Description\n  ...\n  EOF\n  )\"\n  ```\n- If images were provided, mention that they should be manually attached via the GitHub web UI if CLI upload is not possible, and provide the issue URL for easy access\n","# Create GitHub Issue\n\nCreate a new GitHub issue based on the user's input. The input may include screenshots, images, text descriptions, error logs, or any combination.\n\n## Input: $ARGUMENTS\n\n## Instructions\n\n1. **Gather context from the user's input:**\n   - Read any text description or title provided in `$ARGUMENTS`\n   - If the user has provided screenshot paths or image paths, read them using the Read tool to understand their content\n   - Common screenshot locations to check if referenced:\n     - `%USERPROFILE%\\Pictures\\Screenshots`\n     - `%OneDrive%\\Pictures\\Screenshots`\n   - If no title is provided, derive one from the description\u002Fimages\n\n2. **Collect additional information if needed:**\n   - If the description is vague, use AskUserQuestion to clarify:\n     - What is the expected behavior?\n     - What is the actual behavior?\n     - Steps to reproduce?\n     - Priority\u002Fseverity?\n   - If the user provided enough information, proceed without asking\n\n3. **Upload images to the issue:**\n   - If images\u002Fscreenshots were provided, they need to be included in the issue\n   - Use `gh issue create` which supports image references in markdown\n   - For local images, upload them by referencing in the issue body — GitHub CLI handles image uploads when you use the web editor, so instead embed image paths as attachments\n   - Strategy: Create the issue first, then use `gh issue edit` to add images if needed, OR reference images inline\n\n4. **Determine labels:**\n   - Check available labels: `gh label list`\n   - Apply appropriate labels (bug, enhancement, documentation, etc.)\n   - If no matching labels exist, create them if appropriate\n\n5. **Create the issue using GitHub CLI:**\n   ```\n   gh issue create --title \"TITLE\" --body \"BODY\" --label \"LABELS\"\n   ```\n   - Title: Clear, concise, imperative form (e.g., \"Fix crash when opening settings\")\n   - Body format:\n     ```markdown\n     ## Description\n     [Clear description of the issue]\n\n     ## Screenshots\n     [Any attached images]\n\n     ## Steps to Reproduce (if bug)\n     1. Step one\n     2. Step two\n\n     ## Expected Behavior\n     [What should happen]\n\n     ## Actual Behavior\n     [What actually happens]\n\n     ## Additional Context\n     [Any extra info, logs, environment details]\n     ```\n\n6. **Report back:**\n   - Show the created issue URL\n   - Show the issue number\n   - Summarize what was created\n\n## Important Notes\n- Always use `gh` CLI for GitHub operations\n- Use a HEREDOC for the body to preserve formatting:\n  ```bash\n  gh issue create --title \"Title\" --body \"$(cat \u003C\u003C'EOF'\n  ## Description\n  ...\n  EOF\n  )\"\n  ```\n- If images were provided, mention that they should be manually attached via the GitHub web UI if CLI upload is not possible, and provide the issue URL for easy access\n",{"name":5,"description":7,"argument-hint":40,"disable-model-invocation":42},[41],"title or description",true,"main","12032d2a3437cdccc46ff85a50252c60258f2e2e",".claude\u002Fskills\u002Fenter-issue",12,"https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle","https:\u002F\u002Fdevthrottle.com\u002F?ref=gh-about","https:\u002F\u002Fgithub.com\u002Fthefrederiksen","2026-11-11 12:28:38",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":42},[53,56,59],{"tool":54,"command":55},"npx","npx skills add thefrederiksen\u002Fdevthrottle --skill enter-issue",{"tool":57,"command":58},"bunx","bunx skills add thefrederiksen\u002Fdevthrottle --skill enter-issue",{"tool":60,"command":61},"pnpm","pnpm dlx skills add thefrederiksen\u002Fdevthrottle --skill enter-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fenter-issue\u002FSKILL.md",[],[65,92,110,138,165,187],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":35},"01M6CJ9FZRKCB1Y8AY6WAK3JJM","devthrottle-sessions","Talk to the other DevThrottle sessions running across your machines - list them, rename this one, send one of the rare queued messages, read the inbox, reply, open a new session, and close one down. Use when the task involves: message another session, ask another session, list sessions, what sessions are running, spawn a session, rename this session, close this session.","https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002Fplugins\u002Fdevthrottle\u002Fskills\u002Fdevthrottle-sessions\u002FSKILL.md",[],[72,73,74,75,76,77,78,79,80,81,82,28,83,84,85,86,87,88,89,90,22,91,21],"sessions","devthrottle sessions","inbox","messages","new session","open","ask","read","list","spawn","session","reply","task","rename","message","across","close","down","send","running",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":35},"01M6CJ9CYRKE8TSBX67XPTT65R","devthrottle-install","Hand the user the documented steps to install or update DevThrottle, and to connect a gateway afterwards. Use when the task involves: install DevThrottle, set up DevThrottle, update DevThrottle, connect a gateway, cc-devthrottle not found, where do the cc tools come from.","https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002Fplugins\u002Fdevthrottle\u002Fskills\u002Fdevthrottle-install\u002FSKILL.md",[],[99,100,101,102,103,104,105,29,28,106,107,108,84,109,22],"install","devthrottle install","connect","update","gateway","SET","Tools","up","cc","do","hand",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":35},"01M6CJ99Q2QJSXDYAKRBWPGKN2","proof-covers-the-wrong-thing","A proof can be valid and still say nothing about what you changed - wrong surface, wrong reader, wrong caller, or an untested premise. Name what your evidence does NOT cover. Use when the task involves: prove it, by construction, root cause, reproduced it, repro, guard-local, skipped test, suite is green, premise, assumption, self review, it is settled.","https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-discipline\u002Fskills\u002Fproof-covers-the-wrong-thing\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,125,28,126,127,128,84,129,130,131,132,133,134,135,136,137,22],"proof covers the wrong thing","proof","Wrong","review","valid","test","self review","guard","reader","evidence","repro","say","green","self","local","you","can","cover","suite","prove","root cause",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":35},"01M6CJ96VERHA4PKRHMF9ZXTBF","destructive-sweeps-lean-to-keep","A destructive operation acts only on what it can positively prove is disposable. Enumerate what to DELETE, never what to skip - and refresh the safety signal on every real use. Use when the task involves: sweep, purge, cleanup, delete old, prune, reclaim space, stale files, retention, aged out, rm -rf, git clean, drop the table.","https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-discipline\u002Fskills\u002Fdestructive-sweeps-lean-to-keep\u002FSKILL.md",[],[145,146,147,148,149,150,151,152,153,154,155,28,156,157,158,159,160,84,161,162,163,164,136,22],"lean","destructive sweeps lean to keep","keep","cleanup","delete","git","Safety","prune","table","sweep","refresh","never","only","stale","files","clean","drop","retention","reclaim space","signal",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":35},"01M6CJ93GRYMHCZZS657RBHPW6","checks-that-fail-open","A check whose pass condition is an ABSENCE certifies a run that never happened. Restate it as a specific PRESENCE - and an empty result is a broken instrument, never a clean run. Use when the task involves: verify, prove it, sweep, grep returned nothing, zero hits, clean run, it passed, no defects, reviewed, delivered, double check, how do we know.","https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-discipline\u002Fskills\u002Fchecks-that-fail-open\u002FSKILL.md",[],[77,172,173,174,175,176,154,177,178,179,28,156,180,160,108,84,181,182,183,184,185,186,136,22],"checks that fail open","run","ZeRO","verify","how","grep","check","broken","double check","as","condition","restate","presence","defects","result",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":35},"01M6CJ906AQPKFA2CCKKHAZC13","wingman-brief-reviewer","RETIRED 2026-09-16 - do not run it. It reviewed saved wingman turn BRIEFS, whose writer was retired in issue","https:\u002F\u002Fgithub.com\u002Fthefrederiksen\u002Fdevthrottle\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwingman-brief-reviewer\u002Fskill.md",[],[194,195,196,173,19,108,197,198,199,200,201],"brief","reviewer","wingman brief reviewer","writer","it","briefs","saved","2026"]