Causal Inference Root Cause

Systematically investigates causal relationships to identify true root causes rather than correlations or symptoms. Distinguishes genuine causation from spurious associations, tests competing explanations, and designs interventions addressing underlying drivers. Use when investigating why something happened, debugging systems, analyzing failures, evaluating policy impacts, or when user mentions root cause, causal chain, confounding, spurious correlation, or asks "why did this really happen?

200 stars 25 forksFinance & Crypto Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill causal-inference-root-cause
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/causal-inference-root-cause ~/.claude/skills/causal-inference-root-cause

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Causal Inference & Root Cause Analysis

## Table of Contents

- [Workflow](#workflow)
  - [1. Define the Effect](#1--define-the-effect)
  - [2. Generate Hypotheses](#2--generate-hypotheses)
  - [3. Build Causal Model](#3--build-causal-model)
  - [4. Test Causality](#4--test-causality)
  - [5. Document & Validate](#5--document--validate)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

Key concepts: root cause (fundamental issue), proximate cause (immediate trigger), confounding variable (third factor creating spurious correlation), counterfactual ("what would have happened without X?"), and causal mechanism (pathway through which X affects Y).

**Quick Example:**

```markdown
# Effect: Website conversion rate dropped 30%

## Competing Hypotheses:
1. New checkout UI is confusing (proximate)
2. Payment processor latency increased (proximate)
3. We changed to a cheaper payment processor that's slower (root cause)

## Test:
- Rollback UI (no change) → UI not cause
- Check payment logs (confirm latency) → latency is cause
- Trace to processor change → processor change is root cause

## Counterfactual:
"If we hadn't switched processors, would conversion have dropped?"
→ No, conversion was fine with old processor

## Conclusion:
Root cause = processor switch
Mechanism = slow checkout → user abandonment
```

## Workflow

Copy this checklist and track your progress:
Read the full skill on GitHub

Details

Skill name
causal-inference-root-cause
Path
skills/causal-inference-root-cause/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Causal Inference Root Cause skill do?

Systematically investigates causal relationships to identify true root causes rather than correlations or symptoms. Distinguishes genuine causation from spurious associations, tests competing explanations, and designs interventions addressing underlying drivers. Use when investigating why something happened, debugging systems, analyzing failures, evaluating policy impacts, or when user mentions root cause, causal chain, confounding, spurious correlation, or asks "why did this really happen?

How do I install the Causal Inference Root Cause skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Causal Inference Root Cause popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Concept Rediscovery Walk

200

lyndonkl/claude

Guides a learner to invent a math or ML concept themselves through a Socratic walk — a sequence of small guessable questions that ends with the learner stating the formal definition unprompted. The 3Blue1Brown signature move. Use when the learner is meeting a foundational concept (eigenvectors, gradient, attention, softmax, KL divergence) for the first time, when prior exposure produced memorization without understanding, or when the user says "explain it from scratch", "I want to really get it", "build it up for me", or "where does this come from".

Finance & Crypto25

Bookkeeping Automation

213

TerminalSkills/skills

Automate bookkeeping workflows by parsing bank statements (CSV/OFX/QIF), categorizing transactions using rules or an LLM, reconciling accounts, generating expense reports, and detecting duplicates. Use when: automating transaction categorization, building reconciliation pipelines, processing bank exports, or generating expense summaries without manual data entry.

Finance & Crypto34

Corporate Governance Analysis

200

lyndonkl/claude

Assesses who actually controls a company and whether management is accountable — board independence, dual-class and voting structures, cross-holdings and pyramids, the marginal investor, and the gap between stated and real accountability. Use in a corporate finance analysis, when setting the objective function for a valuation, when assessing the odds that bad management gets replaced, or when valuing control.

Finance & Crypto25

Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.