[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWWNNFBAP4STZGK2JHCXFJ":3,"skill-same:01M7EWWNNFBAP4STZGK2JHCXFJ":44},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M7EWWNNFBAP4STZGK2JHCXFJ","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.","ystory\u002Fpstack","ystory","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3927664?v=4","01M7EWADVVNQXMMHYTDDP2GA2R","Yongsul Kim","01M7EWADWC1NKQW4J5A8VYKQRC",0,"MIT","https:\u002F\u002Fgithub.com\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\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\nAdversaries try to break a change or a design. A finding survives only when a run proves it. Report the findings. Do not apply fixes.\n\n## Frame\n\nThe scope is what the user names. Otherwise it is the branch diff from its merge base with the base branch, through the working tree. State the intent with the **in-your-own-words** skill, from the user's message, the commits, and the PR description. Ask 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. Read the `interrogate reviewers` line in place of `arena runners`. Copy the scope's uncommitted changes into each worktree. Spawn each adversary as `generalPurpose`. In place of the arena task and rationale, give each adversary the scope, the intent, and this brief:\n\n> Break this change. 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. For a design or plan, run a prototype or probe the current tree. Keep repros in your own worktree. Report each finding with a title, the exact command, the output it printed, and the output the intent requires. Leave out anything you did not run. That covers style, naming, structure, and risks that need a future change to matter. No findings is a valid result.\n\n## Verify\n\nVerify each finding per arena Phase F by rerunning its command. Keep a finding when the output shows the failure and the failure breaks the intent. Drop the rest. Merge findings that share a root cause.\n\nSkip arena Phases C, D, and E. Adversaries 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. Say \"no verified findings\" when none survive.\n- **Dropped**: for each adversary, the count of dropped findings and why.\n","# Interrogate\n\nAdversaries try to break a change or a design. A finding survives only when a run proves it. Report the findings. Do not apply fixes.\n\n## Frame\n\nThe scope is what the user names. Otherwise it is the branch diff from its merge base with the base branch, through the working tree. State the intent with the **in-your-own-words** skill, from the user's message, the commits, and the PR description. Ask 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. Read the `interrogate reviewers` line in place of `arena runners`. Copy the scope's uncommitted changes into each worktree. Spawn each adversary as `generalPurpose`. In place of the arena task and rationale, give each adversary the scope, the intent, and this brief:\n\n> Break this change. 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. For a design or plan, run a prototype or probe the current tree. Keep repros in your own worktree. Report each finding with a title, the exact command, the output it printed, and the output the intent requires. Leave out anything you did not run. That covers style, naming, structure, and risks that need a future change to matter. No findings is a valid result.\n\n## Verify\n\nVerify each finding per arena Phase F by rerunning its command. Keep a finding when the output shows the failure and the failure breaks the intent. Drop the rest. Merge findings that share a root cause.\n\nSkip arena Phases C, D, and E. Adversaries 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. 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,"main","eeab2c096ccee71d53b62f123122948b3276323b","upstream\u002Fpstack\u002Fskills\u002Finterrogate","https:\u002F\u002Fgithub.com\u002Fystory\u002Fpstack","https:\u002F\u002Fgithub.com\u002Fystory","2026-11-15 13:27:47",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":24},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ystory\u002Fpstack --skill interrogate",{"tool":37,"command":38},"bunx","bunx skills add ystory\u002Fpstack --skill interrogate",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ystory\u002Fpstack --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7EX17PPX81S94GBNSYSQPZB","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\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7EX157E4BPRYFDH5P192JNC","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7EX12TNCHHD3A8ZW9QK5KG6","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7EX0YZX2VWB4BSX9G8DAC8Y","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7EX0VFAW21G3AH2EK5DR7XE","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\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EX0RQPDJQ1Y5W9QF41EQ6K","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\u002Fystory\u002Fpstack\u002Fblob\u002Fmain\u002Fupstream\u002Fpstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]