One repeatable pass that keeps every number and status fak reports PROVENANCE-HONEST - each value labeled by what fak CONTROLS (witnessed/authored) vs what it only OBSERVES (relayed from an external party), and no...
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add anthony-chaudhary/fak --skill conflation-score --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Conflation Score?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/anthony-chaudhary-conflation-score)More formats (shields.io, HTML) on the badges page.
---
name: conflation-score
description: One repeatable pass that keeps every number and status fak reports PROVENANCE-HONEST - each value labeled by what fak CONTROLS (witnessed/authored) vs what it only OBSERVES (relayed from an external party), and no...
metadata:
generated-by: fak project-assets sync
canonical: ../../../.claude/skills/conflation-score/SKILL.md
---
# Canonical project skill adapter
Load and follow [`../../../.claude/skills/conflation-score/SKILL.md`](../../../.claude/skills/conflation-score/SKILL.md). This generated discovery adapter contains no maintained workflow body.
## Portability contract
- The linked canonical `SKILL.md` is the single semantic workflow body for Claude, Codex, and fak-native loaders.
- This adapter changes discovery only; it must not fork, summarize, or translate the workflow.
- Harness-native invocation, permissions, hooks, model routing, and worker launch remain typed adapters outside the semantic body.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
