[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EGYA4A4J2H68ARVVGDN0PB":3,"skill-same:01M7EGYA4A4J2H68ARVVGDN0PB":72},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7EGYA4A4J2H68ARVVGDN0PB","decision-challenge",null,"Use when a high-impact plan, migration or architecture claim needs a bounded adversarial challenge before commitment. Isolates claims from persuasion, attacks assumptions, reconciles doubts with evidence and emits proceed\u002Fhold\u002Fstop. NOT a finished-diff review (`review`\u002F`code-review`), NOT SDD artifact consistency (`analyze`).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fdecision-challenge\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: decision-challenge\ndescription: \"Use when a high-impact plan, migration or architecture claim needs a bounded adversarial challenge before commitment. Isolates claims from persuasion, attacks assumptions, reconciles doubts with evidence and emits proceed\u002Fhold\u002Fstop. NOT a finished-diff review (`review`\u002F`code-review`), NOT SDD artifact consistency (`analyze`).\"\ntags: [adversarial-review, decision-quality, assumptions, risk, preflight]\nrecommends: [analyze, review, code-review, decision-records, security-scan]\nprofiles: [core, full]\norigin: risco\n---\n\n# decision-challenge — doubt with a stopping rule\n\nUse this immediately before a consequential commitment: an irreversible migration, a production-auth change, a costly architecture bet, a launch exception, or a plan whose confidence is higher than its evidence. The purpose is to find the decision-changing doubt, not to perform scepticism forever.\n\nThis skill is read-only unless the user also asks to change the artifact. It emits a challenge record and a verdict. Finished code review stays with `..\u002Freview\u002FSKILL.md` or `..\u002Fcode-review\u002FSKILL.md`; consistency across constitution\u002Fspec\u002Fplan\u002Ftasks stays with `..\u002Fanalyze\u002FSKILL.md`.\n\n## One bounded cycle\n\n```text\nMATERIALIZE → ISOLATE → ATTACK → TEST → RECONCILE → VERDICT\n```\n\n### 1. MATERIALIZE the decision\n\nDo not challenge a cloud of conversation. Write the concrete packet:\n\n- decision or claim being made;\n- artifact and exact revision it applies to;\n- constraints and invariants that must hold;\n- evidence the author relies on;\n- known unknowns;\n- cost of a false positive (unnecessary stop) and false negative (unsafe proceed).\n\nIf the decision cannot be stated in one sentence, split it into claims. “The migration is safe” is not atomic; lock duration, dependency completeness, rollback time and consumer compatibility are separate claims.\n\n### 2. ISOLATE claim from persuasion\n\nCreate a compact challenge packet containing the artifact, contract, constraints and evidence — not the author’s confidence, status, prestige or preferred conclusion. This reduces anchoring.\n\nA genuinely fresh pass is useful when the platform and user authorize one: another agent\u002Fmodel\u002Fcontext can receive only the packet. It is optional, never automatic, and never an excuse to leak data or broaden tool authority. When independent execution is unavailable, make the isolation explicit and challenge locally.\n\n### 3. ATTACK each material claim\n\nFor each claim, ask:\n\n- What observation would make it false?\n- Which dependency or consumer is missing from the inventory?\n- Is the evidence direct, current and representative, or an analogy?\n- What timing, ordering, concurrency or partial-failure path is assumed away?\n- What privilege, data-quality or human handoff must work perfectly?\n- If rollback is promised, has restoration time and data reconciliation been proved?\n- Can the decision be made reversible or staged before accepting this risk?\n\nPrefer one sharp counterexample over ten generic cautions. Rate doubts as blocker, material, or minor by consequence and likelihood; severity is not a count of how uncomfortable the question sounds.\n\n### 4. TEST instead of debating\n\nTurn the strongest doubts into evidence requests: dependency query, row count, dry run, restore rehearsal, shadow traffic, contract test, load profile, permission audit, failure injection or consumer confirmation. Run safe read-only checks that are in scope. Do not mutate production or recruit external systems merely to settle the argument.\n\n### 5. RECONCILE claim by claim\n\nEvery doubt ends in one state:\n\n- **verified** — direct evidence supports the claim;\n- **refuted** — evidence contradicts it;\n- **mitigated** — the plan changed so the original doubt no longer applies;\n- **uncertain** — evidence is missing and consequence remains;\n- **accepted risk** — an authorized owner explicitly accepts a bounded residual risk.\n\nRecord evidence, owner and next action. “Discussed” and “probably fine” are not states.\n\n### 6. VERDICT\n\n- **PROCEED** — no blocker survives; material uncertainties have owners and safe bounds.\n- **HOLD** — a decision-critical uncertainty can be resolved without abandoning the approach.\n- **STOP \u002F REDESIGN** — a claim is refuted or the remaining downside is outside the stated tolerance.\n\nName what would change a HOLD or STOP verdict. A verdict without an unlock condition teaches nothing.\n\n## Stopping rule\n\nRun at most two cycles. A second cycle is allowed only after new evidence or a changed artifact. Stop earlier when a full pass produces no new blocker\u002Fmaterial doubt. Rephrased uncertainty is not new evidence. If the decision remains uncertain after two cycles, keep the uncertainty in the verdict; do not manufacture confidence through repetition.\n\n## Challenge record\n\n```markdown\n# Decision challenge — \u003Cdecision> — \u003Crevision\u002Fdate>\n\n## Contract and stakes\nDecision · invariants · false-positive cost · false-negative cost.\n\n## Claims\n| Claim | Evidence before | Doubt | Test\u002Fevidence | State | Owner |\n\n## Surviving risk\nBlockers · material uncertainty · accepted residual risk.\n\n## Verdict\nPROCEED \u002F HOLD \u002F STOP — reason — unlock condition.\n```\n\n## Anti-patterns\n\n| Smell | Correction |\n|---|---|\n| Every reversible choice receives a panel | Reserve the skill for consequence, uncertainty or irreversibility. |\n| The author’s explanation counts as independent evidence | Isolate claims and require an observation outside the persuasion. |\n| Another model\u002Fagent is mandatory | Use fresh context only when authority, tooling and data boundaries allow it. |\n| Executive pressure relabels a blocker as accepted risk | Require an accountable owner with authority over the consequence. |\n| Domain controls are recreated generically | Route security to `security-scan` and AI quality experiments to `agent-eval`. |\n\n## Orientación (siempre)\n\nCierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente, terminando en pregunta), calibrado al dial de `02-DOCS\u002Fwiki\u002Fharness\u002Fuser-profile.md`. **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills\u002Forient\u002Freferences\u002Forientation-contract.md`. (Defiere a `suggest` el “¿instalo la skill que falta?”.)\n","# decision-challenge — doubt with a stopping rule\n\nUse this immediately before a consequential commitment: an irreversible migration, a production-auth change, a costly architecture bet, a launch exception, or a plan whose confidence is higher than its evidence. The purpose is to find the decision-changing doubt, not to perform scepticism forever.\n\nThis skill is read-only unless the user also asks to change the artifact. It emits a challenge record and a verdict. Finished code review stays with `..\u002Freview\u002FSKILL.md` or `..\u002Fcode-review\u002FSKILL.md`; consistency across constitution\u002Fspec\u002Fplan\u002Ftasks stays with `..\u002Fanalyze\u002FSKILL.md`.\n\n## One bounded cycle\n\n```text\nMATERIALIZE → ISOLATE → ATTACK → TEST → RECONCILE → VERDICT\n```\n\n### 1. MATERIALIZE the decision\n\nDo not challenge a cloud of conversation. Write the concrete packet:\n\n- decision or claim being made;\n- artifact and exact revision it applies to;\n- constraints and invariants that must hold;\n- evidence the author relies on;\n- known unknowns;\n- cost of a false positive (unnecessary stop) and false negative (unsafe proceed).\n\nIf the decision cannot be stated in one sentence, split it into claims. “The migration is safe” is not atomic; lock duration, dependency completeness, rollback time and consumer compatibility are separate claims.\n\n### 2. ISOLATE claim from persuasion\n\nCreate a compact challenge packet containing the artifact, contract, constraints and evidence — not the author’s confidence, status, prestige or preferred conclusion. This reduces anchoring.\n\nA genuinely fresh pass is useful when the platform and user authorize one: another agent\u002Fmodel\u002Fcontext can receive only the packet. It is optional, never automatic, and never an excuse to leak data or broaden tool authority. When independent execution is unavailable, make the isolation explicit and challenge locally.\n\n### 3. ATTACK each material claim\n\nFor each claim, ask:\n\n- What observation would make it false?\n- Which dependency or consumer is missing from the inventory?\n- Is the evidence direct, current and representative, or an analogy?\n- What timing, ordering, concurrency or partial-failure path is assumed away?\n- What privilege, data-quality or human handoff must work perfectly?\n- If rollback is promised, has restoration time and data reconciliation been proved?\n- Can the decision be made reversible or staged before accepting this risk?\n\nPrefer one sharp counterexample over ten generic cautions. Rate doubts as blocker, material, or minor by consequence and likelihood; severity is not a count of how uncomfortable the question sounds.\n\n### 4. TEST instead of debating\n\nTurn the strongest doubts into evidence requests: dependency query, row count, dry run, restore rehearsal, shadow traffic, contract test, load profile, permission audit, failure injection or consumer confirmation. Run safe read-only checks that are in scope. Do not mutate production or recruit external systems merely to settle the argument.\n\n### 5. RECONCILE claim by claim\n\nEvery doubt ends in one state:\n\n- **verified** — direct evidence supports the claim;\n- **refuted** — evidence contradicts it;\n- **mitigated** — the plan changed so the original doubt no longer applies;\n- **uncertain** — evidence is missing and consequence remains;\n- **accepted risk** — an authorized owner explicitly accepts a bounded residual risk.\n\nRecord evidence, owner and next action. “Discussed” and “probably fine” are not states.\n\n### 6. VERDICT\n\n- **PROCEED** — no blocker survives; material uncertainties have owners and safe bounds.\n- **HOLD** — a decision-critical uncertainty can be resolved without abandoning the approach.\n- **STOP \u002F REDESIGN** — a claim is refuted or the remaining downside is outside the stated tolerance.\n\nName what would change a HOLD or STOP verdict. A verdict without an unlock condition teaches nothing.\n\n## Stopping rule\n\nRun at most two cycles. A second cycle is allowed only after new evidence or a changed artifact. Stop earlier when a full pass produces no new blocker\u002Fmaterial doubt. Rephrased uncertainty is not new evidence. If the decision remains uncertain after two cycles, keep the uncertainty in the verdict; do not manufacture confidence through repetition.\n\n## Challenge record\n\n```markdown\n# Decision challenge — \u003Cdecision> — \u003Crevision\u002Fdate>\n\n## Contract and stakes\nDecision · invariants · false-positive cost · false-negative cost.\n\n## Claims\n| Claim | Evidence before | Doubt | Test\u002Fevidence | State | Owner |\n\n## Surviving risk\nBlockers · material uncertainty · accepted residual risk.\n\n## Verdict\nPROCEED \u002F HOLD \u002F STOP — reason — unlock condition.\n```\n\n## Anti-patterns\n\n| Smell | Correction |\n|---|---|\n| Every reversible choice receives a panel | Reserve the skill for consequence, uncertainty or irreversibility. |\n| The author’s explanation counts as independent evidence | Isolate claims and require an observation outside the persuasion. |\n| Another model\u002Fagent is mandatory | Use fresh context only when authority, tooling and data boundaries allow it. |\n| Executive pressure relabels a blocker as accepted risk | Require an accountable owner with authority over the consequence. |\n| Domain controls are recreated generically | Route security to `security-scan` and AI quality experiments to `agent-eval`. |\n\n## Orientación (siempre)\n\nCierra cada turno con el **bloque-brújula** (📍 dónde estás · ✅ qué hiciste · 🧭 por qué · ➡️ siguiente, terminando en pregunta), calibrado al dial de `02-DOCS\u002Fwiki\u002Fharness\u002Fuser-profile.md`. **Nunca termines en seco.** Protocolo completo: skill `orient` → `skills\u002Forient\u002Freferences\u002Forientation-contract.md`. (Defiere a `suggest` el “¿instalo la skill que falta?”.)\n",{"name":5,"tags":24,"origin":30,"profiles":31,"recommends":34,"description":7},[25,26,27,28,29],"adversarial-review","decision-quality","assumptions","risk","preflight","risco",[32,33],"core","full",[35,36,37,38,39],"analyze","review","code-review","decision-records","security-scan","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fdecision-challenge",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill decision-challenge",{"tool":54,"command":55},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill decision-challenge",{"tool":57,"command":58},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill decision-challenge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fdecision-challenge\u002FSKILL.md",true,[62,68],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"evals\u002Fcases.yaml","REFERENCE","参考文档",3162,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fdecision-challenge\u002Fevals\u002Fcases.yaml",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"evals\u002FREADME.md",359,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fdecision-challenge\u002Fevals\u002FREADME.md",[73,81,86,93,100,107],{"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":80},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":82,"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":83,"categories":84,"keywords":85,"publishedAt":80},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\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":80},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":80},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":80},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":80},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]