[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD0F5S1J7F7T4ATD3BXJZR":3,"skill-same:01M7FD0F5S1J7F7T4ATD3BXJZR":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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7FD0F5S1J7F7T4ATD3BXJZR","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.","mr-jones123\u002Fpstack-harness","mr-jones123","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104372691?v=4","01M7FCRJB8YVBWJJ1BQXH89H0R","Xynil Jhed Lacap","01M7FCRJBVNEVCP78T6XKNR907",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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\nIn OMP, read the `pstack-omp` skill (`skill:\u002F\u002Fpstack-omp`) once per session before you follow this skill. It maps the Cursor names in pstack skills to OMP.\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\nIn OMP, read the `pstack-omp` skill (`skill:\u002F\u002Fpstack-omp`) once per session before you follow this skill. It maps the Cursor names in pstack skills to OMP.\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","0826529c4391fc70aa5202aaf46321b52dd5fb0b","skills\u002Finterrogate","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness","https:\u002F\u002Fgithub.com\u002Fmr-jones123","I make cool stuff.","2026-10-28 19:24:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add mr-jones123\u002Fpstack-harness --skill interrogate",{"tool":38,"command":39},"bunx","bunx skills add mr-jones123\u002Fpstack-harness --skill interrogate",{"tool":41,"command":42},"pnpm","pnpm dlx skills add mr-jones123\u002Fpstack-harness --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002FSKILL.md",[],[46,53,60,67,73,80],{"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},"01M7FD55978EY23TE91WMB5N60","pstack-pi","Maps the Cursor names in pstack skills to Pi tools, child Pi processes, models, and paths. pstack skills read it once per session; poteto-mode embeds it.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fpi\u002Fskills\u002Fpstack-pi\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},"01M7FD534A9NNSPEF63NHQXKN9","create-skill","Author or revise an Agent Skills SKILL.md for Pi. Stands in for Cursor's built-in create-skill, which pstack skills name. Use when writing or editing a skill.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fpi\u002Fskills\u002Fcreate-skill\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},"01M7FD511C7R39T8T427JQ45FQ","pstack-omp","Maps the Cursor names in pstack skills to OMP tools, agents, models, and paths. pstack skills read it once per session; poteto-mode embeds it.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fomp\u002Fskills\u002Fpstack-omp\u002FSKILL.md",[],[],{"skillNo":68,"name":55,"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},"01M7FD4YWGMPSRSNREJJ19QBCK","Author or revise an Agent Skills SKILL.md for OMP. Stands in for Cursor's built-in create-skill, which pstack skills name. Use when writing or editing a skill.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fsrc\u002Fomp\u002Fskills\u002Fcreate-skill\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},"01M7FD4T3R0XMZ7XYE96K36T9C","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\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\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},"01M7FD4P0A76YMSPZPKJY6VJKE","verify-this","Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.","https:\u002F\u002Fgithub.com\u002Fmr-jones123\u002Fpstack-harness\u002Fblob\u002Fmain\u002Fskills\u002Fverify-this\u002FSKILL.md",[],[]]