mechanism-mapping
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Map causal mechanisms between variables
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
- merge-candidatesSkill
- model-gap-detectionSkill
- model-validationSkill
- 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
Mechanism Mapping
Construct the directed causal graph by creating mechanism edges between the variables identified in the variable-identification phase. Each edge must carry a plain-language description of the underlying mechanism and at least one evidence citation.
Guiding Focus
CC must treat each proposed edge as a hypothesis, not a fact. For every mechanism edge created, the description should answer three questions: what is the pathway, under what conditions does it hold, and what would falsify it. Edges without a plausible mechanism description are placeholders and must be revisited. The goal is a graph where every arrow is defensible, not merely plausible.
Available Tactics
- counterfactual-reasoning — for each edge A→B, ask "if A were held constant, would B still change?" to stress-test the mechanism
- evidence-weighing — rank competing mechanism descriptions by the strength and independence of their supporting citations
- feedback-loop-detection — scan the emerging graph for cycles that would indicate feedback rather than one-way causation
Budget Slice
| Metric | S | M | L |
| Mechanism edges created | 10 | 25 | 50 |
| Mechanism descriptions | 5 | 15 | 30 |
| Evidence citations | 8 | 20 | 40 |
State Ledger Template
| Metric | Target | Current | Status |
|-------------------------|--------|---------|--------|
| Mechanism edges created | S:10 / M:25 / L:50 | 0 | ⬜ |
| Mechanism descriptions | S:5 / M:15 / L:30 | 0 | ⬜ |
| Evidence citations | S:8 / M:20 / L:40 | 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.