agentleFS
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/causal-modeling/SKILL.md

causal-modeling

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Campaign for building causal models — identify variables, map mechanisms, collect evidence, analyze interventions, validate models. Produces causal graphs in the wiki vault.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call context-init at campaign start

    line 49
  2. Very specific:

    Call context-checkpoint after each strategy completes

    line 50
  3. Very specific:

    Call knowledge-compilation after each strategy </HARD-GATE>

    line 51
  4. Distinctive:

    Correlation is not causation: Every causal edge must have mechanistic justification, not just statistical association.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Causal Modeling

Build causal models for research domains. Identifies variables, maps causal mechanisms, collects supporting evidence, analyzes potential interventions, and validates the resulting causal graph.

Manifest

LevelCountSkills
Strategy5variable-identification, mechanism-mapping, evidence-collection, intervention-analysis, model-validation
Tactic3counterfactual-reasoning, evidence-weighing, feedback-loop-detection
SOP10variable-page-creation, mechanism-edge-creation, evidence-linking, contradiction-flagging, confidence-scoring, intervention-page-creation, loop-documentation, model-gap-detection, causal-chain-query, validation-report

Budget Table

MetricSmallMediumLarge
Variables identified82040
Causal edges created154080
Evidence pages linked103060
Interventions analyzed2510
Feedback loops documented136

Strategy Sequence (Reference, Not Prescription)

  1. variable-identification — identify key variables in the causal system
  2. mechanism-mapping — map causal mechanisms between variables
  3. evidence-collection — gather evidence supporting/refuting causal claims
  4. intervention-analysis — analyze what happens when variables are manipulated
  5. model-validation — validate the causal model for consistency and completeness

MCP Tools Used

  • vault_search — find existing variables and mechanisms
  • vault_add_edge — create causal edges (derived_from, supported_by, contradicts)
  • vault_query_graph — trace causal chains
  • vault_graph_stats — assess model coverage
  • vault_lint — validate structural integrity

Context-Management

<HARD-GATE> - Call `context-init` at campaign start - Call `context-checkpoint` after each strategy completes - Call `knowledge-compilation` after each strategy </HARD-GATE>

Guiding Principles

  • Correlation is not causation. Every causal edge must have mechanistic justification, not just statistical association.
  • Confounders are everywhere. Actively search for confounding variables that could explain observed relationships.
  • Interventions reveal truth. The strongest evidence for causation comes from intervention studies.
  • Feedback loops are the norm. Most real systems have circular causation. Document loops explicitly.
  • Confidence is calibrated. Strong mechanism + strong evidence = high confidence. Weak either = low confidence.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.