[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750B7TBCV7YZPDEGH4GV34B":3,"skill-same:01M750B7TBCV7YZPDEGH4GV34B":47},{"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},"01M750B7TBCV7YZPDEGH4GV34B","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.","michael-denyer\u002Fpstack-claude","michael-denyer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F97485362?v=4","01M7509NWA6PC2Z183SZ6D78FT","Michael Denyer","01M7509NX1YE4AYWW6Y30TCCRV",4309,"MIT","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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.\"\n---\n\n# Interrogate\n\nOn Codex, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcodex-tools.md), including its per-skill notes, before following this skill.\n\nOn GitHub Copilot, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcopilot-tools.md), including its per-skill notes, before following this skill.\n\nOn Muse, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fmuse-tools.md), including its per-skill notes, before following this skill.\n\nOn Antigravity, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fagy-tools.md), including its per-skill notes, before following this skill.\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 `general-purpose`. 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\n## Models\n\nRole defaults, stamped from `plugins\u002Fpstack\u002Fmodels.json` (edit there, rerun `tools\u002Fgenerate.mjs`). A matching role line in the `pstack-models.md` override sheet overrides each at runtime; `\u002Fsetup-pstack` writes it and lists its path per runtime.\n\n- interrogate reviewers: `opus`, `fable`, `sonnet`, `haiku`\n\n## Reasoning effort\n\nA role value in the override sheet may name a reasoning effort after its model, as in `opus @xhigh`. Levels on Claude Code: `low`, `medium`, `high`, `xhigh`, `max`. Which ones apply depends on the model. A value without `@` takes the sheet's `default effort` line, a level or `session`, and `session` when the sheet has no such line. On Claude Code, `session` sets no effort. On other runtimes, follow the platform mapping for `session`. Strip the suffix before reading the model: `inherit-parent` or `auto` still omits `model` at every level, and a model name is passed as `model`. Pass the level as the dispatch's effort field and keep the `subagent_type` you would otherwise use. That is `effort` on the Claude Code `Agent` call and `reasoning_effort` on Codex's `spawn_agent`. On Muse it is `effort` on a Workflow child; a `subagent_spawn` dispatch keeps the session's effort.\n","# Interrogate\n\nOn Codex, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcodex-tools.md), including its per-skill notes, before following this skill.\n\nOn GitHub Copilot, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fcopilot-tools.md), including its per-skill notes, before following this skill.\n\nOn Muse, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fmuse-tools.md), including its per-skill notes, before following this skill.\n\nOn Antigravity, read the [platform mapping](..\u002Fpoteto-mode\u002Freferences\u002Fagy-tools.md), including its per-skill notes, before following this skill.\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 `general-purpose`. 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\n## Models\n\nRole defaults, stamped from `plugins\u002Fpstack\u002Fmodels.json` (edit there, rerun `tools\u002Fgenerate.mjs`). A matching role line in the `pstack-models.md` override sheet overrides each at runtime; `\u002Fsetup-pstack` writes it and lists its path per runtime.\n\n- interrogate reviewers: `opus`, `fable`, `sonnet`, `haiku`\n\n## Reasoning effort\n\nA role value in the override sheet may name a reasoning effort after its model, as in `opus @xhigh`. Levels on Claude Code: `low`, `medium`, `high`, `xhigh`, `max`. Which ones apply depends on the model. A value without `@` takes the sheet's `default effort` line, a level or `session`, and `session` when the sheet has no such line. On Claude Code, `session` sets no effort. On other runtimes, follow the platform mapping for `session`. Strip the suffix before reading the model: `inherit-parent` or `auto` still omits `model` at every level, and a model name is passed as `model`. Pass the level as the dispatch's effort field and keep the `subagent_type` you would otherwise use. That is `effort` on the Claude Code `Agent` call and `reasoning_effort` on Codex's `spawn_agent`. On Muse it is `effort` on a Workflow child; a `subagent_spawn` dispatch keeps the session's effort.\n",{"name":5,"description":7},"main","bc09365fe61c725c486ba95157fc4048bf8a0b99","plugins\u002Fpstack\u002Fskills\u002Finterrogate",397,"https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude","https:\u002F\u002Fgithub.com\u002Fmichael-denyer","https:\u002F\u002Fwww.wisdompanel.com\u002F","Software Engineer and Bioinformatician","2026-11-13 23:53:05",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add michael-denyer\u002Fpstack-claude --skill interrogate",{"tool":39,"command":40},"bunx","bunx skills add michael-denyer\u002Fpstack-claude --skill interrogate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add michael-denyer\u002Fpstack-claude --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Finterrogate\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M750F31RNVHGK1JVWBJHDGTX","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\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M750F17NKT7YCP8ND5675XHN","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M750EYD7DP60DDPQY6GK3TTR","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M750EWQG73FRRSA065D2NMRZ","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M750ETTMA3MB36DJQJ1H4QGB","thermos","Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug\u002Fsecurity and code-quality branch audits.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermos\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M750EQVQMQSW08KYGM7TG8K0","thermo-nuclear-review","Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-review\u002FSKILL.md",[],[]]