[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A00T4FZ1Y1PR5N8PSRT2X9":3,"skill-same:01M7A00T4FZ1Y1PR5N8PSRT2X9":129},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7A00T4FZ1Y1PR5N8PSRT2X9","diagnosing-superpowers",null,"Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, \"it took too long\", \"why is it so expensive\", \"what is it doing\" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.","sazlin\u002Floadout","sazlin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7120031?v=4","01M79ZSNX5RMXATQTSH5NGHN51","Sean Azlin","01M79ZSNXQ5HCTYC1RE7J5CAPF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: diagnosing-superpowers\ndescription: Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, \"it took too long\", \"why is it so expensive\", \"what is it doing\" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.\n---\n\n# Diagnosing Superpowers\n\n## Overview\n\nPin down with your human partner what went wrong in a session, read the\ntranscripts on disk, and report what happened with evidence. You report;\nyou do not diagnose superpowers. Whoever triages the bundle or the issue\ndecides whether superpowers changes.\n\n**Core principle:** Every finding cites `path:line`. No citation, no\nfinding. Every number comes from the transcript or from a command you ran,\nnever from memory.\n\n## Workflow\n\nCreate a todo per step. Steps 5–7 run only on their stated condition.\n\n1. **Problem intake.** Ask one question at a time until you can write a\n   statement naming the session(s), the turn range if known, what your\n   partner expected, what happened, and the observable they care about\n   (wall-clock, tokens, repeated actions, one specific action). \"It took\n   too long\" is a complaint, not a problem statement. Note whether the\n   goal is a superpowers bug report.\n2. **Locate.** Resolve each session to verified absolute filesystem paths using\n   `references\u002Fsession-discovery.md`. Confirm a past session by quoting its\n   first prompt and timestamp, and list every candidate you rejected with the\n   reason, or \"none\". Enumerate subagent transcripts. Create\n   `~\u002F.superpowers\u002Fdiagnosing-superpowers\u002F\u003Csession-id>\u002F`, tell your\n   partner the path, and fill `templates\u002Fcase.md` there, following its\n   provenance rules for environment and skill observations.\n3. **Triage.** Read the region around the reported problem yourself. Then\n   dispatch one analyst subagent per dimension in parallel, each given the\n   case file path, `prompts\u002Fanalyst-common.md`, and one dimension file from\n   `prompts\u002F`: `skill-timeline.md`,\n   `plan-adherence.md`, `repeated-work.md`, `stumbles.md`,\n   `quality-evidence.md`, `request-conflicts.md`, `cost-and-time.md`.\n   Split a dimension by turn range when the transcript is long. Discard\n   any returned finding without `path:line`.\n4. **Report.** Fill every section of `templates\u002Freport.md` in order, write\n   it to the workspace, show it, and give the path. Check what cited content\n   actually proves and preserve the supporting case; a symlink alias is not a\n   redundant copy.\n5. **GitHub issues** — when report §7 says possible or likely, or your\n   partner asks. Search open and closed issues for the symptoms per\n   `references\u002Fgithub-issues.md`. Show matches and suggest adding the\n   report to the closest. If none match, fill `templates\u002Fissue.md`, write\n   it to the workspace, show the exact text, and create the issue only\n   after approval. `gh` cannot attach files; if a bundle exists, give\n   your partner its path to attach in the browser.\n6. **Export** — only when your partner asks for a bundle; never build one\n   unprompted. If the intake goal was a bug report, say once that a\n   scrubbed bundle is available on request, then wait. Ask the redaction\n   level, stating what each includes: skeleton (no tool-result bodies),\n   evidence (bodies only for cited events), full. Build the bundle per\n   `templates\u002Fbundle-README.md`. Dispatch `prompts\u002Fscrub.md`, then\n   `prompts\u002Fscrub-audit.md`. Repeat that pair at most 3 rounds, stopping\n   early when the audit returns CLEAN. If the last audit is still MISSED,\n   stop, show the last MISSED list, and ask whether to export as limited\n   or abort. Do not re-dispatch scrub on 429-class or tool failures;\n   surface the error and stop. Complete the bundle template's evidence\n   check and reconciliation before showing the final scrub log, file\n   list, and privacy and evidence outcomes.\n   Archive (`zip -r` or `tar -czf`) only after approval. With the archive\n   path, state what it contains, point at the scrub log for replacements, and\n   say scrubbing can miss things: they must review every file before sharing.\n7. **Similar sessions** — when asked. Turn confirmed findings into a\n   signature. List candidate transcripts by mtime and size, then keep at\n   most the 8 newest files over 4 KiB. Find marker line numbers. Dispatch\n   `prompts\u002Fsimilar-session.md` sequentially or in batches of at most 4;\n   never one subagent per leftover file at once. Matching stays\n   file-based (CASE, CANDIDATE, SIGNATURE). Stop after the first yes or\n   partial hits that fill report §9 rather than waiting on every\n   candidate, then append §9.\n\n## Quick reference\n\nAll seven analysts always run. This table says which region to read\nyourself in step 3 and which findings to lead with in the verdict.\n\n| Complaint | Read first, lead with |\n|---|---|\n| \"It took too long\" | cost-and-time, stumbles |\n| \"Why did it do this extra work?\" | repeated-work, plan-adherence |\n| \"Why is it so expensive?\" | cost-and-time |\n| \"What the hell is it doing?\" (still running) | skill-timeline; note in-progress in coverage |\n| \"It ignored the plan\" | plan-adherence, compaction lines first |\n| \"Skill X never fired\" | skill-timeline |\n\n## Hard rules\n\n- **Context safety.** One transcript line can be a megabyte. Follow\n  `references\u002Fcontext-safety.md` on every session file, every time.\n- **Read-only.** Never modify, move, or delete a session file.\n- **Exact paths to subagents.** A subagent's \"current session\" is its\n  own. Pass absolute paths and ids.\n- **Human prompts only.** Hook output, system reminders, and tool results\n  are not your partner's words. In a subagent transcript, \"user\" is the\n  parent agent.\n- **No superpowers diagnosis.** Report §7 states involvement and stops.\n  Never name a defect in a skill or propose a change. Your partner\n  pressing for a fix does not waive this; point at the issue step and\n  mention that a bundle is available on request. No advice to your\n  partner either.\n- **Approval gates.** No archive before your partner has seen the scrub\n  log and file list. No issue or comment before they approve the exact\n  text.\n- **Intake before analysis.** Nothing in steps 2–7 starts until your\n  partner has answered. If they are away, write the questions and stop.\n  A statement you reconstructed for them is not an answer. An\n  already-scoped request — one specific event, what is running now, or\n  the analysis to run — is itself the statement: answer it, then ask.\n  A whole-session \"why\" is a complaint.\n\n## Red Flags\n\n| Thought | Reality |\n|---------|---------|\n| \"The problem is obvious, skip intake\" | The problem statement scopes everything. Ask. |\n| \"They're away, so I'll reconstruct the statement\" | You cannot reconstruct what they wanted. Write the questions and stop. |\n| \"I'll sweep everything now and ask at the end\" | An unscoped sweep spends their budget on the wrong question. Ask first. |\n| \"They want a bug report, so I'll build the bundle now\" | The bundle is their session data, packaged. Build it only when they ask for it. |\n| \"Small, targeted edit, no restructuring needed\" | Not your call, however small. Report the evidence; the triager decides. |\n| \"The price per token is well known\" | Numbers you did not compute from the transcript are invented. Cite or drop. |\n","# Diagnosing Superpowers\n\n## Overview\n\nPin down with your human partner what went wrong in a session, read the\ntranscripts on disk, and report what happened with evidence. You report;\nyou do not diagnose superpowers. Whoever triages the bundle or the issue\ndecides whether superpowers changes.\n\n**Core principle:** Every finding cites `path:line`. No citation, no\nfinding. Every number comes from the transcript or from a command you ran,\nnever from memory.\n\n## Workflow\n\nCreate a todo per step. Steps 5–7 run only on their stated condition.\n\n1. **Problem intake.** Ask one question at a time until you can write a\n   statement naming the session(s), the turn range if known, what your\n   partner expected, what happened, and the observable they care about\n   (wall-clock, tokens, repeated actions, one specific action). \"It took\n   too long\" is a complaint, not a problem statement. Note whether the\n   goal is a superpowers bug report.\n2. **Locate.** Resolve each session to verified absolute filesystem paths using\n   `references\u002Fsession-discovery.md`. Confirm a past session by quoting its\n   first prompt and timestamp, and list every candidate you rejected with the\n   reason, or \"none\". Enumerate subagent transcripts. Create\n   `~\u002F.superpowers\u002Fdiagnosing-superpowers\u002F\u003Csession-id>\u002F`, tell your\n   partner the path, and fill `templates\u002Fcase.md` there, following its\n   provenance rules for environment and skill observations.\n3. **Triage.** Read the region around the reported problem yourself. Then\n   dispatch one analyst subagent per dimension in parallel, each given the\n   case file path, `prompts\u002Fanalyst-common.md`, and one dimension file from\n   `prompts\u002F`: `skill-timeline.md`,\n   `plan-adherence.md`, `repeated-work.md`, `stumbles.md`,\n   `quality-evidence.md`, `request-conflicts.md`, `cost-and-time.md`.\n   Split a dimension by turn range when the transcript is long. Discard\n   any returned finding without `path:line`.\n4. **Report.** Fill every section of `templates\u002Freport.md` in order, write\n   it to the workspace, show it, and give the path. Check what cited content\n   actually proves and preserve the supporting case; a symlink alias is not a\n   redundant copy.\n5. **GitHub issues** — when report §7 says possible or likely, or your\n   partner asks. Search open and closed issues for the symptoms per\n   `references\u002Fgithub-issues.md`. Show matches and suggest adding the\n   report to the closest. If none match, fill `templates\u002Fissue.md`, write\n   it to the workspace, show the exact text, and create the issue only\n   after approval. `gh` cannot attach files; if a bundle exists, give\n   your partner its path to attach in the browser.\n6. **Export** — only when your partner asks for a bundle; never build one\n   unprompted. If the intake goal was a bug report, say once that a\n   scrubbed bundle is available on request, then wait. Ask the redaction\n   level, stating what each includes: skeleton (no tool-result bodies),\n   evidence (bodies only for cited events), full. Build the bundle per\n   `templates\u002Fbundle-README.md`. Dispatch `prompts\u002Fscrub.md`, then\n   `prompts\u002Fscrub-audit.md`. Repeat that pair at most 3 rounds, stopping\n   early when the audit returns CLEAN. If the last audit is still MISSED,\n   stop, show the last MISSED list, and ask whether to export as limited\n   or abort. Do not re-dispatch scrub on 429-class or tool failures;\n   surface the error and stop. Complete the bundle template's evidence\n   check and reconciliation before showing the final scrub log, file\n   list, and privacy and evidence outcomes.\n   Archive (`zip -r` or `tar -czf`) only after approval. With the archive\n   path, state what it contains, point at the scrub log for replacements, and\n   say scrubbing can miss things: they must review every file before sharing.\n7. **Similar sessions** — when asked. Turn confirmed findings into a\n   signature. List candidate transcripts by mtime and size, then keep at\n   most the 8 newest files over 4 KiB. Find marker line numbers. Dispatch\n   `prompts\u002Fsimilar-session.md` sequentially or in batches of at most 4;\n   never one subagent per leftover file at once. Matching stays\n   file-based (CASE, CANDIDATE, SIGNATURE). Stop after the first yes or\n   partial hits that fill report §9 rather than waiting on every\n   candidate, then append §9.\n\n## Quick reference\n\nAll seven analysts always run. This table says which region to read\nyourself in step 3 and which findings to lead with in the verdict.\n\n| Complaint | Read first, lead with |\n|---|---|\n| \"It took too long\" | cost-and-time, stumbles |\n| \"Why did it do this extra work?\" | repeated-work, plan-adherence |\n| \"Why is it so expensive?\" | cost-and-time |\n| \"What the hell is it doing?\" (still running) | skill-timeline; note in-progress in coverage |\n| \"It ignored the plan\" | plan-adherence, compaction lines first |\n| \"Skill X never fired\" | skill-timeline |\n\n## Hard rules\n\n- **Context safety.** One transcript line can be a megabyte. Follow\n  `references\u002Fcontext-safety.md` on every session file, every time.\n- **Read-only.** Never modify, move, or delete a session file.\n- **Exact paths to subagents.** A subagent's \"current session\" is its\n  own. Pass absolute paths and ids.\n- **Human prompts only.** Hook output, system reminders, and tool results\n  are not your partner's words. In a subagent transcript, \"user\" is the\n  parent agent.\n- **No superpowers diagnosis.** Report §7 states involvement and stops.\n  Never name a defect in a skill or propose a change. Your partner\n  pressing for a fix does not waive this; point at the issue step and\n  mention that a bundle is available on request. No advice to your\n  partner either.\n- **Approval gates.** No archive before your partner has seen the scrub\n  log and file list. No issue or comment before they approve the exact\n  text.\n- **Intake before analysis.** Nothing in steps 2–7 starts until your\n  partner has answered. If they are away, write the questions and stop.\n  A statement you reconstructed for them is not an answer. An\n  already-scoped request — one specific event, what is running now, or\n  the analysis to run — is itself the statement: answer it, then ask.\n  A whole-session \"why\" is a complaint.\n\n## Red Flags\n\n| Thought | Reality |\n|---------|---------|\n| \"The problem is obvious, skip intake\" | The problem statement scopes everything. Ask. |\n| \"They're away, so I'll reconstruct the statement\" | You cannot reconstruct what they wanted. Write the questions and stop. |\n| \"I'll sweep everything now and ask at the end\" | An unscoped sweep spends their budget on the wrong question. Ask first. |\n| \"They want a bug report, so I'll build the bundle now\" | The bundle is their session data, packaged. Build it only when they ask for it. |\n| \"Small, targeted edit, no restructuring needed\" | Not your call, however small. Report the evidence; the triager decides. |\n| \"The price per token is well known\" | Numbers you did not compute from the transcript are invented. Cite or drop. |\n",{"name":5,"description":7},"main","f6497b6aafdead5bb7cf244894b930f699a53e46","skills\u002Fdiagnosing-superpowers",1,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout","https:\u002F\u002Fgithub.com\u002Fsazlin","https:\u002F\u002Fseanazlin.com","Principal Engineer & Engineering Leader | AI Infrastructure & Marketplace Systems | Fractional CTO for 0-to-1 Startups","2026-11-14 20:13:46",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add sazlin\u002Floadout --skill diagnosing-superpowers",{"tool":39,"command":40},"bunx","bunx skills add sazlin\u002Floadout --skill diagnosing-superpowers",{"tool":42,"command":43},"pnpm","pnpm dlx skills add sazlin\u002Floadout --skill diagnosing-superpowers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002FSKILL.md",true,[47,53,57,61,65,69,73,77,81,85,89,93,97,101,105,109,113,117,121,125],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"evals\u002Fevals.json","REFERENCE","参考文档",2338,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fevals\u002Fevals.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"prompts\u002Fanalyst-common.md",1582,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fanalyst-common.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"prompts\u002Fcost-and-time.md",1640,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fcost-and-time.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"prompts\u002Fplan-adherence.md",1637,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fplan-adherence.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"prompts\u002Fquality-evidence.md",1476,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fquality-evidence.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"prompts\u002Frepeated-work.md",1469,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Frepeated-work.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"prompts\u002Frequest-conflicts.md",1011,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Frequest-conflicts.md",{"path":78,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":79,"sourceHtmlUrl":80},"prompts\u002Fscrub-audit.md",1363,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub-audit.md",{"path":82,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":83,"sourceHtmlUrl":84},"prompts\u002Fscrub.md",1471,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub.md",{"path":86,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":87,"sourceHtmlUrl":88},"prompts\u002Fsimilar-session.md",1711,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fsimilar-session.md",{"path":90,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":91,"sourceHtmlUrl":92},"prompts\u002Fskill-timeline.md",1646,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fskill-timeline.md",{"path":94,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":95,"sourceHtmlUrl":96},"prompts\u002Fstumbles.md",1330,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fstumbles.md",{"path":98,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fcontext-safety.md",990,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fcontext-safety.md",{"path":102,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fgithub-issues.md",1644,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fgithub-issues.md",{"path":106,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fredaction-policy.md",2243,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fredaction-policy.md",{"path":110,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fsession-discovery.md",1859,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fsession-discovery.md",{"path":114,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":115,"sourceHtmlUrl":116},"templates\u002Fbundle-README.md",3672,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fbundle-README.md",{"path":118,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":119,"sourceHtmlUrl":120},"templates\u002Fcase.md",2983,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fcase.md",{"path":122,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":123,"sourceHtmlUrl":124},"templates\u002Fissue.md",1851,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fissue.md",{"path":126,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":127,"sourceHtmlUrl":128},"templates\u002Freport.md",2359,"https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Freport.md",[130,137,144,151,158,165],{"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":19},"01M7A06GGYSGA1EA79WNMD8JHJ","demo","Demo skill","https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmini_loadout\u002Fskills\u002Fdemo\u002FSKILL.md",[],[],{"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":19},"01M7A06BTSB17JVWZ52Z3DQDYY","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":19},"01M7A069Y4ZJZBPP82QJ9KBHTV","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":19},"01M7A0676YNTT61WYZ7241T3RB","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\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":19},"01M7A065AY047VH6JBN19WFAZ9","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\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":19},"01M7A062FBQ3VPWZT3BP8DWYKA","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\u002Fsazlin\u002Floadout\u002Fblob\u002Fmain\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[]]