model-validation
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Validate causal model consistency
4 other projects use a version of this.
Adopted by
Most recently taken up by
- nirholas/three.ws-chattheir own version, first seen Nov 8, 2026
- nirholas/three-uitheir own version, first seen Oct 11, 2026
- gmanch94/claude-code-aidlc-templatetheir own version, first seen Jul 11, 2026
- aizech/clinical-skillstheir own version, first seen Apr 19, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- nirholas/three-ui★ 10same name
- nirholas/three.ws-chat★ 10same name
- aizech/clinical-skills★ 4same name
- gmanch94/claude-code-aidlc-template★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- alias-resolutionSkill
- argument-mappingSkill
- argument-synthesisSkill
- argument-visualizationSkill
- axis-extractionSkill
- axis-validationSkill
- causal-chain-querySkill
- causal-modelingSkill
- claim-decompositionSkill
- claim-extractionSkill
- claim-page-creationSkill
- combination-enumerationSkill
- combination-mappingSkill
- concept-decompositionSkill
- concept-extractionSkill
- concept-page-creationSkill
- confidence-scoringSkill
- confidence-updateSkill
- consistency-checkingSkill
- contradiction-flaggingSkill
- counterfactual-reasoningSkill
- dimensional-analysisSkill
- dimension-discoverySkill
- dimension-page-creationSkill
- domain-scopingSkill
- edge-batch-creationSkill
- evidence-attachmentSkill
- evidence-collectionSkill
- evidence-linking-argSkill
- evidence-linkingSkill
- evidence-weighingSkill
- feedback-loop-detectionSkill
- gap-detectionSkill
- gap-prioritizationSkill
- hierarchy-constructionSkill
- hierarchy-visualizationSkill
- intervention-analysisSkill
- intervention-page-creationSkill
- knowledge-compilationSkill
- loop-documentationSkill
- matrix-exportSkill
- matrix-generationSkill
- mechanism-edge-creationSkill
- mechanism-mappingSkill
- merge-candidatesSkill
- model-gap-detectionSkill
- novelty-scoringSkill
- ontology-buildingSkill
- ontology-exportSkill
- ontology-refinementSkill
- question-generationSkill
- rebuttal-documentationSkill
- relation-typingSkill
- seed-concept-searchSkill
- source-gatheringSkill
- strength-assessmentSkill
- strength-scoringSkill
- synthesis-reportSkill
- taxonomy-validationSkill
- validation-reportSkill
- The first 60 shown.
The file
Files
Model Validation
Audit the completed causal model for internal consistency: detect and resolve cycles that should not exist, surface contradictions between evidence and claimed edges, and recalibrate confidence scores where the evidence base has shifted. This strategy is the final quality gate before the model is used for inference or reporting.
Guiding Focus
CC must approach validation as a skeptic, not a defender. The goal is to find problems, not confirm that the model is fine. Cycles in a directed acyclic graph (DAG) are structural errors unless explicitly modeled as feedback loops with documentation. Contradictions between evidence pages and mechanism edges indicate that either the edge or the evidence assessment is wrong — both must be re-examined. Confidence recalibrations should propagate: if a key mechanism edge loses confidence, all downstream claims that depend on it should be flagged for review as well.
Available Tactics
- feedback-loop-detection — distinguish legitimate documented feedback loops from accidental cycles introduced by inconsistent edge direction
- evidence-weighing — re-score confidence on edges where new contradicting evidence was added during evidence-collection
- counterfactual-reasoning — use "if this edge were removed, which predictions would change?" to identify which edges are load-bearing and deserve the most scrutiny
Budget Slice
| Metric | S | M | L |
| Cycles checked | 3 | 8 | 15 |
| Contradictions resolved | 1 | 3 | 6 |
| Confidence recalibrations | 3 | 8 | 15 |
State Ledger Template
| Metric | Target | Current | Status |
|---------------------------|--------|---------|--------|
| Cycles checked | S:3 / M:8 / L:15 | 0 | ⬜ |
| Contradictions resolved | S:1 / M:3 / L:6 | 0 | ⬜ |
| Confidence recalibrations | S:3 / M:8 / L:15 | 0 | ⬜ |<HARD-GATE>
Cannot exit until 80% of budget met. Print state ledger before each iteration decision.
</HARD-GATE>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

