agentleFS
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/intervention-analysis/SKILL.md

intervention-analysis

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Analyze interventions and manipulations on the causal system

The file

Files
SKILL.md

Intervention Analysis

Identify and analyze interventions — deliberate manipulations of variables in the causal system — and predict their downstream outcomes given the current causal graph. This strategy operationalizes the model by showing what would happen if a practitioner or researcher actually pulled a lever.

Guiding Focus

CC must distinguish clearly between observational associations and interventional effects. An intervention severs the incoming edges to the manipulated variable (do-calculus style), so the predicted outcome may differ substantially from what correlation alone would suggest. For each intervention analyzed, CC should trace the causal path forward through the graph, note moderating variables that could dampen or amplify the effect, and flag any feedback loops that make the outcome path-dependent. Predicted outcomes should be directional claims (increases, decreases, no expected change) with explicit uncertainty where the graph is incomplete.

Available Tactics

  • counterfactual-reasoning — for each intervention, construct the counterfactual scenario (do(X=x) vs do(X=x')) and trace diverging outcomes
  • feedback-loop-detection — identify whether the intervention triggers a feedback loop that partially reverses or amplifies the initial effect
  • evidence-weighing — prioritize interventions that have existing experimental or quasi-experimental evidence over purely theoretical ones

Budget Slice

MetricSML
Interventions analyzed2510
Intervention pages created2510
Predicted outcomes3815

State Ledger Template

| Metric                    | Target | Current | Status |
|---------------------------|--------|---------|--------|
| Interventions analyzed    | S:2 / M:5 / L:10  | 0 | ⬜ |
| Intervention pages created | S:2 / M:5 / L:10 | 0 | ⬜ |
| Predicted outcomes        | 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>

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.