[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FQCPYFDY2TYBPFSTWVNV7":3,"skill-same:01M70FQCPYFDY2TYBPFSTWVNV7":78},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70FQCPYFDY2TYBPFSTWVNV7","config-gc",null,"Garbage collection for your Claude Code configuration. Periodically scans ~\u002F.claude (skills, memory, hooks, permissions, MCP servers, caches) for redundant, stale, orphaned, or low-value items, then walks the user through a confirm-each-deletion cleanup. Use when the user says \"clean up my config\", \"config GC\", \"too many skills\", \"audit my setup\", \"my .claude is bloated\", or asks for a periodic config review.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fconfig-gc\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"config gc","config","gc","hooks","when","value","for","deletion","my","clean","periodic","MCP","up","collection","audit","permissions","code","cleanup","memory","review","2026-11-10 10:12:30",false,"---\nname: config-gc\ndescription: Garbage collection for your Claude Code configuration. Periodically scans ~\u002F.claude (skills, memory, hooks, permissions, MCP servers, caches) for redundant, stale, orphaned, or low-value items, then walks the user through a confirm-each-deletion cleanup. Use when the user says \"clean up my config\", \"config GC\", \"too many skills\", \"audit my setup\", \"my .claude is bloated\", or asks for a periodic config review.\nmetadata:\n  origin: ECC\n---\n\n# Config GC — Garbage Collection for Claude Code Setups\n\nBorrowed from runtime garbage collection: periodically scan for objects that are no longer referenced, redundant, expired, or low-value, and reclaim the space. The critical difference: **here, collection requires a human in the loop. Never delete autonomously.**\n\n## When to Activate\n\n- The user asks to clean up, audit, or slim down their Claude Code configuration\n- The user complains about too many skills, noisy hooks, or slow session startup\n- A monthly\u002Fperiodic config review is due\n- After installing a large skill pack (e.g. this repo), to reconcile overlaps with existing setup\n\nDo NOT activate for: cleaning project source code (that's refactoring), clearing chat history, or uninstalling Claude Code itself.\n\n## Design Philosophy\n\n1. **Append-only configs leak.** Skills, memory files, hooks, and permission entries only ever get added. Without periodic review they rot silently.\n2. **Regular audits beat one-time purges.** Scan every ~30 days, propose a small batch of candidates each time.\n3. **Per-channel strategies.** Each accumulation type (skills, hooks, permissions, ...) has its own staleness signals — don't apply one rule everywhere.\n4. **Soft-delete first.** Rename to `.disabled` > move to `~\u002F.claude\u002F_gc_trash\u002F` > real deletion. Always keep an undo path.\n5. **Forced human-in-the-loop.** Every candidate gets its own `[y\u002Fn\u002Fskip]` confirmation. No \"yes to all\" shortcut.\n6. **Keep a log.** Every GC run appends to `~\u002F.claude\u002Fgc_log.md`: what was touched, why, and how to undo it.\n\n## Scan Channels\n\n| # | Channel | Path | Staleness \u002F redundancy signals |\n|---|---------|------|--------------------------------|\n| 1 | Skills | `~\u002F.claude\u002Fskills\u002F*\u002F` | Heavily overlapping names; never triggered in recent transcripts; domain mismatch with the user's actual work; broken or empty SKILL.md |\n| 2 | Memory | `~\u002F.claude\u002F**\u002Fmemory\u002F*.md` + its index | Multiple index entries for one topic; contents contradicting newer entries; dates that have passed; orphan files missing from the index; sub-100-word fragments that should merge |\n| 3 | Hooks | `~\u002F.claude\u002Fhooks\u002F` + settings | Scripts present on disk but referenced by no hook config; old versions superseded by rewrites |\n| 4 | Permissions | `permissions.allow` in `settings.json` \u002F `settings.local.json` | Duplicate entries; specific entries already covered by a wildcard (e.g. `Bash(git push)` when `Bash(*)` is allowed); one-off grants from past experiments |\n| 5 | MCP servers | `~\u002F.claude.json` or project `.mcp.json` | Servers that fail to connect; functional duplicates; long-unused |\n| 6 | Scheduled reminders \u002F jobs | wherever the user keeps them | Fired one-shots older than 30 days; jobs whose target scripts no longer exist |\n| 7 | Project history | `~\u002F.claude\u002Fprojects\u002F*\u002F` | Stale handoff snapshots; session records superseded by newer state |\n| 8 | Runtime caches | `cache\u002F`, `file-history\u002F`, `logs\u002F`, `shell-snapshots\u002F` | Sort by size and mtime; propose items >30 days old and large |\n\n## Workflow\n\n1. **Scan** all channels (or the subset the user names). Collect candidates with: path, channel, signal that flagged it, size, last-modified.\n2. **Rank** by confidence (broken\u002Forphaned = high; merely old = low) and present as a numbered table. Cap each run at ~20 candidates — GC is periodic, not exhaustive.\n3. **Confirm one by one.** For each candidate show the evidence, then ask `[y\u002Fn\u002Fskip]`. The user can stop at any point.\n4. **Soft-delete confirmed items**: prefer `.disabled` rename for skills\u002Fhooks and `_gc_trash\u002F\u003Cdate>\u002F` move for files. Permission entries live in JSON (no comments possible): back up the settings file, record each removed entry verbatim in `gc_log.md`, then remove it from the `allow` array with `jq`. Only hard-delete when the user explicitly asks.\n5. **Log** the run to `~\u002F.claude\u002Fgc_log.md`: timestamp, items actioned, undo instructions.\n6. **Report**: reclaimed size, channels still healthy, suggested next review date.\n\n## Example Scan Commands\n\nOrphaned hook scripts (channel 3) — scripts on disk that no hook config references:\n\n```bash\nfor f in ~\u002F.claude\u002Fhooks\u002F*; do\n  name=$(basename \"$f\")\n  grep -rq \"$name\" ~\u002F.claude\u002Fsettings.json ~\u002F.claude\u002Fsettings.local.json 2>\u002Fdev\u002Fnull \\\n    || echo \"ORPHAN: $f\"\ndone\n```\n\nRedundant permission entries (channel 4) — duplicates, and specific grants shadowed by a wildcard:\n\n```bash\njq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json | sort | uniq -d\nif jq -e '.permissions.allow | index(\"Bash(*)\")' ~\u002F.claude\u002Fsettings.local.json >\u002Fdev\u002Fnull; then\n  jq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json \\\n    | grep '^Bash(' | grep -vF 'Bash(*)'\nfi\n```\n\nLargest stale caches (channel 8) — `du -k` instead of GNU-only `find -printf`, so it works on macOS\u002FBSD too:\n\n```bash\nfind ~\u002F.claude\u002Ffile-history ~\u002F.claude\u002Fshell-snapshots -type f -mtime +30 \\\n  -exec du -k {} + 2>\u002Fdev\u002Fnull | sort -rn | head -20\n```\n\nSoft-delete with undo path (capture the date once so the log can't disagree with the directory):\n\n```bash\ngc_date=$(date +%Y-%m-%d)\nmkdir -p ~\u002F.claude\u002F_gc_trash\u002F$gc_date\nmv ~\u002F.claude\u002Fskills\u002Fdead-skill ~\u002F.claude\u002F_gc_trash\u002F$gc_date\u002F\necho \"$(date -Iseconds) moved skills\u002Fdead-skill -> _gc_trash\u002F$gc_date\u002F (undo: mv back)\" >> ~\u002F.claude\u002Fgc_log.md\n```\n\nRemoving a confirmed-redundant permission entry (JSON has no comments — back up, log, then edit):\n\n```bash\ncp ~\u002F.claude\u002Fsettings.local.json ~\u002F.claude\u002Fsettings.local.json.bak\necho \"$(date -Iseconds) removed permission entry: Bash(git push) (undo: restore from .bak or re-add)\" >> ~\u002F.claude\u002Fgc_log.md\njq '.permissions.allow -= [\"Bash(git push)\"]' ~\u002F.claude\u002Fsettings.local.json.bak \\\n  > ~\u002F.claude\u002Fsettings.local.json\n```\n\n## Anti-Patterns\n\n- **Bulk approval.** Asking \"delete all 15? [y\u002Fn]\" defeats the design. One item, one decision.\n- **Hard-deleting on first pass.** If there's no `_gc_trash\u002F` copy or `.disabled` rename, you did it wrong.\n- **Treating \"old\" as \"dead\".** A skill untouched for 60 days may be seasonal (tax season, quarterly reviews). Age is a signal, not a verdict — that's why a human confirms.\n- **Cleaning memory by truncation.** Merging two contradicting memory files requires reading both and keeping the newer truth, not deleting the longer one.\n- **Touching anything outside `~\u002F.claude`** (or the project's `.claude\u002F`). Config GC never wanders into source trees.\n\n## Best Practices\n\n- Run after big additions, not just on a calendar: installing a 50-skill pack is exactly when overlap with existing skills appears.\n- When two skills overlap, prefer disabling the one with the weaker trigger description — it's the one that was probably never firing anyway.\n- Permission cleanup is the highest-value channel per minute spent: redundant allow-entries make security review harder.\n- Keep `gc_log.md` forever. It's tiny, and \"when did I disable that hook and why\" comes up more often than you'd think.\n\n## Related Skills\n\n- `skill-stocktake` — audits skill *quality*; config-gc audits skill *existence*. Run stocktake on what survives GC.\n- `workspace-surface-audit` — the additive counterpart: recommends what to install. config-gc is the subtractive half of the same lifecycle.\n- `configure-ecc` — after installing skills with it, run config-gc to reconcile overlaps with your pre-existing setup.\n- `continuous-learning` — produces the memory files this skill later audits.\n- `security-review` — pairs well with the permissions channel.\n","# Config GC — Garbage Collection for Claude Code Setups\n\nBorrowed from runtime garbage collection: periodically scan for objects that are no longer referenced, redundant, expired, or low-value, and reclaim the space. The critical difference: **here, collection requires a human in the loop. Never delete autonomously.**\n\n## When to Activate\n\n- The user asks to clean up, audit, or slim down their Claude Code configuration\n- The user complains about too many skills, noisy hooks, or slow session startup\n- A monthly\u002Fperiodic config review is due\n- After installing a large skill pack (e.g. this repo), to reconcile overlaps with existing setup\n\nDo NOT activate for: cleaning project source code (that's refactoring), clearing chat history, or uninstalling Claude Code itself.\n\n## Design Philosophy\n\n1. **Append-only configs leak.** Skills, memory files, hooks, and permission entries only ever get added. Without periodic review they rot silently.\n2. **Regular audits beat one-time purges.** Scan every ~30 days, propose a small batch of candidates each time.\n3. **Per-channel strategies.** Each accumulation type (skills, hooks, permissions, ...) has its own staleness signals — don't apply one rule everywhere.\n4. **Soft-delete first.** Rename to `.disabled` > move to `~\u002F.claude\u002F_gc_trash\u002F` > real deletion. Always keep an undo path.\n5. **Forced human-in-the-loop.** Every candidate gets its own `[y\u002Fn\u002Fskip]` confirmation. No \"yes to all\" shortcut.\n6. **Keep a log.** Every GC run appends to `~\u002F.claude\u002Fgc_log.md`: what was touched, why, and how to undo it.\n\n## Scan Channels\n\n| # | Channel | Path | Staleness \u002F redundancy signals |\n|---|---------|------|--------------------------------|\n| 1 | Skills | `~\u002F.claude\u002Fskills\u002F*\u002F` | Heavily overlapping names; never triggered in recent transcripts; domain mismatch with the user's actual work; broken or empty SKILL.md |\n| 2 | Memory | `~\u002F.claude\u002F**\u002Fmemory\u002F*.md` + its index | Multiple index entries for one topic; contents contradicting newer entries; dates that have passed; orphan files missing from the index; sub-100-word fragments that should merge |\n| 3 | Hooks | `~\u002F.claude\u002Fhooks\u002F` + settings | Scripts present on disk but referenced by no hook config; old versions superseded by rewrites |\n| 4 | Permissions | `permissions.allow` in `settings.json` \u002F `settings.local.json` | Duplicate entries; specific entries already covered by a wildcard (e.g. `Bash(git push)` when `Bash(*)` is allowed); one-off grants from past experiments |\n| 5 | MCP servers | `~\u002F.claude.json` or project `.mcp.json` | Servers that fail to connect; functional duplicates; long-unused |\n| 6 | Scheduled reminders \u002F jobs | wherever the user keeps them | Fired one-shots older than 30 days; jobs whose target scripts no longer exist |\n| 7 | Project history | `~\u002F.claude\u002Fprojects\u002F*\u002F` | Stale handoff snapshots; session records superseded by newer state |\n| 8 | Runtime caches | `cache\u002F`, `file-history\u002F`, `logs\u002F`, `shell-snapshots\u002F` | Sort by size and mtime; propose items >30 days old and large |\n\n## Workflow\n\n1. **Scan** all channels (or the subset the user names). Collect candidates with: path, channel, signal that flagged it, size, last-modified.\n2. **Rank** by confidence (broken\u002Forphaned = high; merely old = low) and present as a numbered table. Cap each run at ~20 candidates — GC is periodic, not exhaustive.\n3. **Confirm one by one.** For each candidate show the evidence, then ask `[y\u002Fn\u002Fskip]`. The user can stop at any point.\n4. **Soft-delete confirmed items**: prefer `.disabled` rename for skills\u002Fhooks and `_gc_trash\u002F\u003Cdate>\u002F` move for files. Permission entries live in JSON (no comments possible): back up the settings file, record each removed entry verbatim in `gc_log.md`, then remove it from the `allow` array with `jq`. Only hard-delete when the user explicitly asks.\n5. **Log** the run to `~\u002F.claude\u002Fgc_log.md`: timestamp, items actioned, undo instructions.\n6. **Report**: reclaimed size, channels still healthy, suggested next review date.\n\n## Example Scan Commands\n\nOrphaned hook scripts (channel 3) — scripts on disk that no hook config references:\n\n```bash\nfor f in ~\u002F.claude\u002Fhooks\u002F*; do\n  name=$(basename \"$f\")\n  grep -rq \"$name\" ~\u002F.claude\u002Fsettings.json ~\u002F.claude\u002Fsettings.local.json 2>\u002Fdev\u002Fnull \\\n    || echo \"ORPHAN: $f\"\ndone\n```\n\nRedundant permission entries (channel 4) — duplicates, and specific grants shadowed by a wildcard:\n\n```bash\njq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json | sort | uniq -d\nif jq -e '.permissions.allow | index(\"Bash(*)\")' ~\u002F.claude\u002Fsettings.local.json >\u002Fdev\u002Fnull; then\n  jq -r '.permissions.allow[]' ~\u002F.claude\u002Fsettings.local.json \\\n    | grep '^Bash(' | grep -vF 'Bash(*)'\nfi\n```\n\nLargest stale caches (channel 8) — `du -k` instead of GNU-only `find -printf`, so it works on macOS\u002FBSD too:\n\n```bash\nfind ~\u002F.claude\u002Ffile-history ~\u002F.claude\u002Fshell-snapshots -type f -mtime +30 \\\n  -exec du -k {} + 2>\u002Fdev\u002Fnull | sort -rn | head -20\n```\n\nSoft-delete with undo path (capture the date once so the log can't disagree with the directory):\n\n```bash\ngc_date=$(date +%Y-%m-%d)\nmkdir -p ~\u002F.claude\u002F_gc_trash\u002F$gc_date\nmv ~\u002F.claude\u002Fskills\u002Fdead-skill ~\u002F.claude\u002F_gc_trash\u002F$gc_date\u002F\necho \"$(date -Iseconds) moved skills\u002Fdead-skill -> _gc_trash\u002F$gc_date\u002F (undo: mv back)\" >> ~\u002F.claude\u002Fgc_log.md\n```\n\nRemoving a confirmed-redundant permission entry (JSON has no comments — back up, log, then edit):\n\n```bash\ncp ~\u002F.claude\u002Fsettings.local.json ~\u002F.claude\u002Fsettings.local.json.bak\necho \"$(date -Iseconds) removed permission entry: Bash(git push) (undo: restore from .bak or re-add)\" >> ~\u002F.claude\u002Fgc_log.md\njq '.permissions.allow -= [\"Bash(git push)\"]' ~\u002F.claude\u002Fsettings.local.json.bak \\\n  > ~\u002F.claude\u002Fsettings.local.json\n```\n\n## Anti-Patterns\n\n- **Bulk approval.** Asking \"delete all 15? [y\u002Fn]\" defeats the design. One item, one decision.\n- **Hard-deleting on first pass.** If there's no `_gc_trash\u002F` copy or `.disabled` rename, you did it wrong.\n- **Treating \"old\" as \"dead\".** A skill untouched for 60 days may be seasonal (tax season, quarterly reviews). Age is a signal, not a verdict — that's why a human confirms.\n- **Cleaning memory by truncation.** Merging two contradicting memory files requires reading both and keeping the newer truth, not deleting the longer one.\n- **Touching anything outside `~\u002F.claude`** (or the project's `.claude\u002F`). Config GC never wanders into source trees.\n\n## Best Practices\n\n- Run after big additions, not just on a calendar: installing a 50-skill pack is exactly when overlap with existing skills appears.\n- When two skills overlap, prefer disabling the one with the weaker trigger description — it's the one that was probably never firing anyway.\n- Permission cleanup is the highest-value channel per minute spent: redundant allow-entries make security review harder.\n- Keep `gc_log.md` forever. It's tiny, and \"when did I disable that hook and why\" comes up more often than you'd think.\n\n## Related Skills\n\n- `skill-stocktake` — audits skill *quality*; config-gc audits skill *existence*. Run stocktake on what survives GC.\n- `workspace-surface-audit` — the additive counterpart: recommends what to install. config-gc is the subtractive half of the same lifecycle.\n- `configure-ecc` — after installing skills with it, run config-gc to reconcile overlaps with your pre-existing setup.\n- `continuous-learning` — produces the memory files this skill later audits.\n- `security-review` — pairs well with the permissions channel.\n",{"name":5,"metadata":54,"description":7},{"origin":55},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fconfig-gc",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 06:54:12",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill config-gc",{"tool":70,"command":71},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill config-gc",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill config-gc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fconfig-gc\u002FSKILL.md",true,[],[79,87,112,130,149,164],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M72JT3YP1SQHD0MANGDXQ4RT","higgsfield-websites","Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1\u002FR2\u002FKV\u002FDO\u002FContainers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references\u002Fwebsite-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references\u002Fapp-flow.md), `game` (realtime multiplayer rooms — references\u002Fgame-flow.md). Routes to the right flow; each carries its own rules and deploy\u002Fpublish gates.\nUse when: \"build me a website\", \"make a landing page\", \"create a web app\", \"build a SaaS dashboard \u002F portfolio\", \"make me a game\", \"deploy this site\", \"publish\". Also owns GAME ART: \"make a spritesheet\", \"tileable texture\", \"animate a 3D character\", game music\u002FSFX — see the game-* references.\nNOT for: single image\u002Fvideo\u002Faudio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fhiggsfield-ai_skills\u002Fhiggsfield-websites\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":103,"publishedAt":49},"01M70JPK8HAXXA85P7Q8NKZZYG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-skills\u002FSKILL.md",[93,96,99,100],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":97,"categoryName":98,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[104,105,106,107,108,109,110,33,111],"writing","writing skills","editing","deployment","use","Existing","new","work",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":49},"01M70JP4PHBH1CQVVDWZ94W159","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-plans\u002FSKILL.md",[118,119,120],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[104,122,123,124,33,45,35,108,125,126,127,128,129],"writing plans","plans","you","requirements","task","multi","spec","multi-step task",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":49},"01M70JNTYVGXFZT8PASZ844TH8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fverification-before-completion\u002FSKILL.md",[],[137,138,139,140,141,142,108,143,144,145,33,146,111,147,148],"verification","verification before completion","complete","about","output","assertions","prs","evidence","claim","claims","commands","running",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":49},"01M70JNGVSQDESWN0Q5BPJ875V","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-superpowers\u002FSKILL.md",[155],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,159,160,108,33,161,162,163],"using superpowers","superpowers","conversation","how to","how","find","questions",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":49},"01M70JN57CE588NPYPYTWH1DWG","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[171,172,173,174,175,176,33,111,177,178,179,180,181,182,183,123,108,184,185],"using git worktrees","Using git","git","worktrees","git worktrees","implementation","git worktree","worktree","native","Tools","isolation","fallback","feature","via","workspace"]