[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFXYHHJ94SCX5CQ902BT39":3,"skill-same:01M7DFXYHHJ94SCX5CQ902BT39":121},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7DFXYHHJ94SCX5CQ902BT39","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. [Superpowers; user-invoked. Code tab: diagnose a build-ticket\u002FSDD run that went wrong.]","phillippasqualato\u002FPAPcSetup","phillippasqualato","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F243869150?v=4","01M7DFRVNH334NRG1TXEJPXBZH","01M7DFRVP62D3G2NB7N6KFCWCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\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. [Superpowers; user-invoked. Code tab: diagnose a build-ticket\u002FSDD run that went wrong.]\"\ndisable-model-invocation: true\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`, repeating both until the audit returns CLEAN.\n   Complete the bundle template's evidence check and reconciliation before\n   showing the final scrub log, file 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 candidates by mtime and size, find marker line numbers,\n   dispatch `prompts\u002Fsimilar-session.md` per candidate in parallel, and\n   append report §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`, repeating both until the audit returns CLEAN.\n   Complete the bundle template's evidence check and reconciliation before\n   showing the final scrub log, file 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 candidates by mtime and size, find marker line numbers,\n   dispatch `prompts\u002Fsimilar-session.md` per candidate in parallel, and\n   append report §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,"disable-model-invocation":23},true,"main","337c4b675cfdf7b5e53e9311f3c757dac9123236","plugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup","https:\u002F\u002Fgithub.com\u002Fphillippasqualato","2026-10-07 04:02:12",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add phillippasqualato\u002FPAPcSetup --skill diagnosing-superpowers",{"tool":36,"command":37},"bunx","bunx skills add phillippasqualato\u002FPAPcSetup --skill diagnosing-superpowers",{"tool":39,"command":40},"pnpm","pnpm dlx skills add phillippasqualato\u002FPAPcSetup --skill diagnosing-superpowers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002FSKILL.md",[43,49,53,57,61,65,69,73,77,81,85,89,93,97,101,105,109,113,117],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"prompts\u002Fanalyst-common.md","REFERENCE","参考文档",1582,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fanalyst-common.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"prompts\u002Fcost-and-time.md",1640,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fcost-and-time.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"prompts\u002Fplan-adherence.md",1637,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fplan-adherence.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"prompts\u002Fquality-evidence.md",1476,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fquality-evidence.md",{"path":62,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":63,"sourceHtmlUrl":64},"prompts\u002Frepeated-work.md",1469,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Frepeated-work.md",{"path":66,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":67,"sourceHtmlUrl":68},"prompts\u002Frequest-conflicts.md",1011,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Frequest-conflicts.md",{"path":70,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":71,"sourceHtmlUrl":72},"prompts\u002Fscrub-audit.md",1363,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub-audit.md",{"path":74,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":75,"sourceHtmlUrl":76},"prompts\u002Fscrub.md",1471,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub.md",{"path":78,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":79,"sourceHtmlUrl":80},"prompts\u002Fsimilar-session.md",1711,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fsimilar-session.md",{"path":82,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":83,"sourceHtmlUrl":84},"prompts\u002Fskill-timeline.md",1646,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fskill-timeline.md",{"path":86,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":87,"sourceHtmlUrl":88},"prompts\u002Fstumbles.md",1330,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fstumbles.md",{"path":90,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fcontext-safety.md",990,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fcontext-safety.md",{"path":94,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fgithub-issues.md",1644,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fgithub-issues.md",{"path":98,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fredaction-policy.md",2243,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fredaction-policy.md",{"path":102,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fsession-discovery.md",1859,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fsession-discovery.md",{"path":106,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":107,"sourceHtmlUrl":108},"templates\u002Fbundle-README.md",3672,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fbundle-README.md",{"path":110,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":111,"sourceHtmlUrl":112},"templates\u002Fcase.md",2983,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fcase.md",{"path":114,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":115,"sourceHtmlUrl":116},"templates\u002Fissue.md",1851,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fissue.md",{"path":118,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":119,"sourceHtmlUrl":120},"templates\u002Freport.md",2359,"https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Freport.md",[122,129,136,143,150,159],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":18},"01M7DG6ZPZW6PW5DMB4EA5X6AG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment [Superpowers; user-invoked. Use to write or pressure-test a skill, e.g. product-studio changes.]","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":18},"01M7DG6WK1GVEQN4F2PM7JRV43","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code [product-studio: canonical Code-tab execution, entered via build-ticket; user-invoked otherwise]","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":18},"01M7DG6RZ6Q3VSTTKFH519WC21","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":18},"01M7DG6N1WY2DRM3XP41SP4M0W","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":154,"licenseFileUrl":155,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":18},"01M7DG6HBW3X6CFPBDZG16BNVR","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. [Python alternative to playwright-skill (canonical for scripted browser checks); user-invoked only.]","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":18},"01M7DG6E1K8KEPBHP6GGDTDG4W","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[]]