[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7972XCABD00FR25SJPPWXT2":3,"skill-same:01M7972XCABD00FR25SJPPWXT2":45},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7972XCABD00FR25SJPPWXT2","interrogate",null,"Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Adversaries try to break a change or design, and only findings proven by a run survive.","zenspc\u002Fpi-extensions","zenspc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F305758515?v=4","01M7971P15J72BHA92768XKTYV","Zen Space","01M7971P1R0A3P6E6BT0HTHS1T",13,"MIT","https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: interrogate\ndescription: \"Use for \\\"interrogate\\\", \\\"adversarial review\\\", \\\"multi-model review\\\", \\\"challenge this\\\", \\\"stress test this code\\\", \\\"find blind spots\\\", or \\\"tear this apart\\\". Adversaries try to break a change or design, and only findings proven by a run survive.\"\ndisable-model-invocation: true\n---\n\n# Interrogate\n\nBefore delegation, read [Pi delegation controls](..\u002Fpoteto-mode\u002Freferences\u002Fpi-delegation.md) for read-only acceptance and per-child launch parameters.\n\nRead [Pi review models](..\u002Fpoteto-mode\u002Freferences\u002Fpi-models.md) before launching; report effective models and label same-model panels accurately.\n\nAdversaries try to break a change or a design.\nA finding survives only when a run proves it.\nReport the findings.\nDo not apply fixes.\n\n## Frame\n\nThe scope is what the user names.\nOtherwise it is the branch diff from its merge base with the base branch, through the working tree.\nState the intent with the **in-your-own-words** skill, from the user's message, the commits, and the PR description.\nAsk the user when the intent is unclear.\n\n## Fan out\n\nRun Phase A steps 3 and 4 and Phase B of the **arena** skill, with four changes.\nRead the `interrogate reviewers` line in place of `arena runners`.\nCopy the scope's uncommitted changes into each worktree.\nSpawn each adversary with `agent: \"worker\"`.\nGive it shell and repro-writing tools in its isolated worktree, plus the scoped review acceptance policy from Pi delegation controls.\nRepro creation is allowed; application fixes and writes to the original checkout are not.\nIn place of the arena task and rationale, give each adversary the scope, the intent, and this brief:\n\n> Break this change.\n> Prove each finding with a run against the real code, such as a failing test, a repro script, or command output that shows the wrong behavior.\n> For a design or plan, run a prototype or probe the current tree.\n> Keep repros in your own worktree.\n> Report each finding with a title, the exact command, the output it printed, and the output the intent requires.\n> Leave out anything you did not run.\n> That covers style, naming, structure, and risks that need a future change to matter.\n> No findings is a valid result.\n\n## Verify\n\nVerify each finding per arena Phase F by rerunning its command.\nKeep a finding when the output shows the failure and the failure breaks the intent.\nDrop the rest.\nMerge findings that share a root cause.\n\nSkip arena Phases C, D, and E.\nAdversaries find different failures, so the verdict keeps every verified finding, not one adversary's list.\n\n## Output\n\n- **Intent**: the restatement.\n- **Findings**: for each verified finding, the command, its output, how it breaks the intent, and the adversaries that found it.\n  Say \"no verified findings\" when none survive.\n- **Dropped**: for each adversary, the count of dropped findings and why.\n","# Interrogate\n\nBefore delegation, read [Pi delegation controls](..\u002Fpoteto-mode\u002Freferences\u002Fpi-delegation.md) for read-only acceptance and per-child launch parameters.\n\nRead [Pi review models](..\u002Fpoteto-mode\u002Freferences\u002Fpi-models.md) before launching; report effective models and label same-model panels accurately.\n\nAdversaries try to break a change or a design.\nA finding survives only when a run proves it.\nReport the findings.\nDo not apply fixes.\n\n## Frame\n\nThe scope is what the user names.\nOtherwise it is the branch diff from its merge base with the base branch, through the working tree.\nState the intent with the **in-your-own-words** skill, from the user's message, the commits, and the PR description.\nAsk the user when the intent is unclear.\n\n## Fan out\n\nRun Phase A steps 3 and 4 and Phase B of the **arena** skill, with four changes.\nRead the `interrogate reviewers` line in place of `arena runners`.\nCopy the scope's uncommitted changes into each worktree.\nSpawn each adversary with `agent: \"worker\"`.\nGive it shell and repro-writing tools in its isolated worktree, plus the scoped review acceptance policy from Pi delegation controls.\nRepro creation is allowed; application fixes and writes to the original checkout are not.\nIn place of the arena task and rationale, give each adversary the scope, the intent, and this brief:\n\n> Break this change.\n> Prove each finding with a run against the real code, such as a failing test, a repro script, or command output that shows the wrong behavior.\n> For a design or plan, run a prototype or probe the current tree.\n> Keep repros in your own worktree.\n> Report each finding with a title, the exact command, the output it printed, and the output the intent requires.\n> Leave out anything you did not run.\n> That covers style, naming, structure, and risks that need a future change to matter.\n> No findings is a valid result.\n\n## Verify\n\nVerify each finding per arena Phase F by rerunning its command.\nKeep a finding when the output shows the failure and the failure breaks the intent.\nDrop the rest.\nMerge findings that share a root cause.\n\nSkip arena Phases C, D, and E.\nAdversaries find different failures, so the verdict keeps every verified finding, not one adversary's list.\n\n## Output\n\n- **Intent**: the restatement.\n- **Findings**: for each verified finding, the command, its output, how it breaks the intent, and the adversaries that found it.\n  Say \"no verified findings\" when none survive.\n- **Dropped**: for each adversary, the count of dropped findings and why.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"master","e16dbfe61a2384049fdcd77d96d4b3d8443ba429","packages\u002Fpi-pstack\u002Fskills\u002Finterrogate",4,"https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions","https:\u002F\u002Fgithub.com\u002Fzenspc","2026-11-07 02:05:20",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add zenspc\u002Fpi-extensions --skill interrogate",{"tool":38,"command":39},"bunx","bunx skills add zenspc\u002Fpi-extensions --skill interrogate",{"tool":41,"command":42},"pnpm","pnpm dlx skills add zenspc\u002Fpi-extensions --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7976YX9582Z9VA13BTQZ39J","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7976W286EEWZ784S4EJ3CWC","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7976T5B6XQNV5TJH7X4T16Q","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7976P6PEAWS36Z8H6V9C8Q3","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Fskill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7976JS1CN7NVJBYA99EZDDM","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7976F6VAKHQZHTP3590M4Y6","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Fzenspc\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]