causal-inference-engine
Causal inference skill for estimating treatment effects and understanding causal relationships in business data
What this skill does
# Causal Inference Engine
## Overview
The Causal Inference Engine skill provides sophisticated methods for estimating causal effects from observational data. It enables business analysts to move beyond correlation to understand true cause-and-effect relationships, supporting evidence-based decision-making for interventions, policy changes, and strategic initiatives.
## Capabilities
- Propensity score matching
- Inverse probability weighting
- Difference-in-differences
- Instrumental variables
- Regression discontinuity
- Synthetic control methods
- Causal forest implementation
- Sensitivity analysis to unobserved confounding
## Used By Processes
- A/B Testing and Experimentation Framework
- Predictive Analytics Implementation
- Win/Loss Analysis Program
## Usage
### Problem Definition
```python
# Define causal question
causal_problem = {
"treatment": "marketing_campaign",
"outcome": "purchase_conversion",
"confounders": ["customer_segment", "prior_purchases", "channel", "region"],
"instruments": ["random_assignment_probability"], # if available
"effect_type": "ATE", # Average Treatment Effect
"heterogeneity": ["customer_segment", "tenure"] # for CATE
}
```
### Propensity Score Matching
```python
# Propensity score configuration
psm_config = {
"method": "propensity_score_matching",
"estimator": "logistic_regression",
"matching": {
"method": "nearest_neighbor",
"caliper": 0.1,
"replacement": False,
"ratio": 1
},
"balance_check": True,
"covariates": ["age", "income", "prior_purchases", "engagement_score"]
}
```
### Difference-in-Differences
```python
# DiD configuration
did_config = {
"method": "difference_in_differences",
"treatment_group": "stores_with_intervention",
"control_group": "stores_without_intervention",
"pre_period": ["2023-01", "2023-06"],
"post_period": ["2023-07", "2023-12"],
"parallel_trends_test": True,
"fixed_effects": ["store_id", "month"]
}
```
### Causal Forest (Heterogeneous Effects)
```python
# Causal forest for CATE
causal_forest_config = {
"method": "causal_forest",
"n_trees": 1000,
"honest": True,
"effect_modifiers": ["customer_segment", "tenure", "region"],
"output": {
"individual_effects": True,
"confidence_intervals": True,
"variable_importance": True
}
}
```
## Method Selection Guide
| Method | When to Use | Assumptions |
|--------|-------------|-------------|
| Propensity Score | Selection on observables | No unmeasured confounding |
| Difference-in-Differences | Pre/post with control group | Parallel trends |
| Regression Discontinuity | Threshold-based treatment | Continuity at threshold |
| Instrumental Variables | Unmeasured confounding exists | Valid instrument |
| Synthetic Control | Aggregate-level intervention | Pre-treatment fit |
| Causal Forest | Heterogeneous effects | Unconfoundedness |
## Input Schema
```json
{
"causal_problem": {
"treatment": "string",
"outcome": "string",
"confounders": ["string"],
"effect_type": "ATE|ATT|CATE"
},
"data": "dataframe or path",
"method_config": {
"method": "string",
"parameters": "object"
},
"validation": {
"refutation_tests": ["placebo", "subset", "random_common_cause"],
"sensitivity_analysis": "boolean"
}
}
```
## Output Schema
```json
{
"effect_estimate": {
"point_estimate": "number",
"confidence_interval": ["number", "number"],
"p_value": "number",
"standard_error": "number"
},
"heterogeneous_effects": {
"subgroup": {
"effect": "number",
"ci": ["number", "number"]
}
},
"diagnostics": {
"balance_statistics": "object",
"parallel_trends_test": "object",
"first_stage_f_stat": "number (IV)"
},
"refutation_results": {
"test_name": {
"original_effect": "number",
"refuted_effect": "number",
"passed": "boolean"
}
},
"sensitivity": {
"robustness_value": "number",
"interpretation": "string"
}
}
```
## Best Practices
1. Clearly articulate the causal question before analysis
2. Draw a causal diagram (DAG) to identify confounders
3. Check covariate balance after matching/weighting
4. Perform sensitivity analysis to unmeasured confounding
5. Use multiple refutation tests to validate results
6. Report effect sizes with confidence intervals
7. Be transparent about assumptions and limitations
## Refutation Tests
| Test | What It Checks |
|------|----------------|
| Placebo Treatment | Effect should be zero with random treatment |
| Placebo Outcome | Effect should be zero with unrelated outcome |
| Subset Validation | Effect should hold in subsamples |
| Random Common Cause | Adding random confounder shouldn't change effect |
## Integration Points
- Feeds into Hypothesis Tracker for test results
- Connects with Experimentation Manager agent
- Supports Predictive Analyst for causal features
- Integrates with Bayesian Network Analyzer for causal graphs
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.