[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARTJGFV5MZKKARSDNSVKP3":3,"skill-same:01M7ARTJGFV5MZKKARSDNSVKP3":50},{"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},"01M7ARTJGFV5MZKKARSDNSVKP3","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.","gutierrezje\u002Fjstack","gutierrezje","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F32502846?v=4","01M7ARSJH934J0XXNJC02Y6PB0","Jesus E. Gutierrez","01M7ARSJJ8PN0AGVX140JK202H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\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\nRead [the global routing table](..\u002Fjesus-mode\u002Freferences\u002Froutes.md) before dispatching. Inspect the current subagent tool's supported model and effort overrides; never silently inherit the parent after a pinned-model rejection.\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 [in-your-own-words](..\u002Fin-your-own-words\u002FSKILL.md), from the user's message, the commits, and the PR description. Ask the user when the intent is unclear. Freeze the scope, intent, diff, tests, and hard constraints before dispatching.\n\n## Fan out\n\nUse the Interrogate routes: two adversaries by default, one with a correctness lens and one with an architecture and edge-case lens. Add the configured third for high-risk or contested changes. Give each adversary the scope, the intent, its lens, and this brief. Keep findings independent until collection.\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. Do not edit the repository under review: run repros from a disposable worktree or temp directory that includes the scope's uncommitted changes. 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\nEach adversary runs in a shared checkout, so give each its own scratch location. Run overlapping writers sequentially.\n\n## Verify\n\nRerun each finding's command in the parent. Keep a finding when the output shows the failure and the failure breaks the intent. Drop the rest, including hypothetical paths the callers cannot reach and preferences with no failing run. Merge findings that share a root cause. Adversaries find different failures, so keep every verified finding rather than 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, ordered by severity. Say \"no verified findings\" when none survive.\n- **Dropped**: for each adversary, the count of dropped findings and why.\n\nCompletion means every reported finding carries a command and output the parent reproduced.\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\nRead [the global routing table](..\u002Fjesus-mode\u002Freferences\u002Froutes.md) before dispatching. Inspect the current subagent tool's supported model and effort overrides; never silently inherit the parent after a pinned-model rejection.\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 [in-your-own-words](..\u002Fin-your-own-words\u002FSKILL.md), from the user's message, the commits, and the PR description. Ask the user when the intent is unclear. Freeze the scope, intent, diff, tests, and hard constraints before dispatching.\n\n## Fan out\n\nUse the Interrogate routes: two adversaries by default, one with a correctness lens and one with an architecture and edge-case lens. Add the configured third for high-risk or contested changes. Give each adversary the scope, the intent, its lens, and this brief. Keep findings independent until collection.\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. Do not edit the repository under review: run repros from a disposable worktree or temp directory that includes the scope's uncommitted changes. 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\nEach adversary runs in a shared checkout, so give each its own scratch location. Run overlapping writers sequentially.\n\n## Verify\n\nRerun each finding's command in the parent. Keep a finding when the output shows the failure and the failure breaks the intent. Drop the rest, including hypothetical paths the callers cannot reach and preferences with no failing run. Merge findings that share a root cause. Adversaries find different failures, so keep every verified finding rather than 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, ordered by severity. Say \"no verified findings\" when none survive.\n- **Dropped**: for each adversary, the count of dropped findings and why.\n\nCompletion means every reported finding carries a command and output the parent reproduced.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","bbac2ca2c2f494880dc8aa5d58dc4f768501f290","skills\u002Finterrogate","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack","https:\u002F\u002Fgithub.com\u002Fgutierrezje","2026-11-11 14:57:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":24},[33,36,39],{"tool":34,"command":35},"npx","npx skills add gutierrezje\u002Fjstack --skill interrogate",{"tool":37,"command":38},"bunx","bunx skills add gutierrezje\u002Fjstack --skill interrogate",{"tool":40,"command":41},"pnpm","pnpm dlx skills add gutierrezje\u002Fjstack --skill interrogate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002FSKILL.md",[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",201,"https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Finterrogate\u002Fagents\u002Fopenai.yaml",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7ARWNBDTFSVCHWFQ4BYWQSX","why","Why code is this way: design rationale, regressions, and history from evidence. For runtime: how.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7ARWKP5P795ZTFRJQJNK9ZK","unslop","Edit prose to remove AI writing patterns when polishing text or asked to make it sound natural.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7ARWG34VZRC0FZTP4Z1VXFH","typescript-best-practices","Use when writing or reviewing .ts\u002F.tsx code: types, validation boundaries, and API signatures.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7ARWBBKAMRHVJH929D2TSW1","sync-pstack","Analyze upstream cursor\u002Fplugins pstack changes and guide semantic ports into Codex-native Jstack without overwriting local skills. Use when the user says \"sync pstack\", \"check pstack updates\", or asks to update Jstack from upstream.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fsync-pstack\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ARW853DBZYE9ETT0ZZHP9J","swarm","Fan out N parallel workers, drain them, and return one report. Use for \u002Fswarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fswarm\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ARW5Y0CMDJCAJ1P3KKBDV8","statechart","Check a finite TLA+ model and explain its paths and rule failures as a statechart.","https:\u002F\u002Fgithub.com\u002Fgutierrezje\u002Fjstack\u002Fblob\u002Fmain\u002Fskills\u002Fstatechart\u002FSKILL.md",[],[]]