Install
$ agentstack add skill-trecek-useful-claude-skills-make-experiment-diag ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Experimental Design Diagram Selection
Select the right experimental design lens for your analysis. Each lens asks one primary question about an experiment's design, surfacing assumptions and failure modes specific to that epistemic dimension.
When to Use
- Want to visualize or audit experimental design methodology
- Need to select the right lens for a specific experimental concern
- User says
/make-experiment-diag - User wants to examine a specific aspect of an experiment
Critical Constraints
NEVER:
- Skip the selection step — always confirm which lens to use
- Modify any source code or experimental artifacts
- Combine multiple lenses in a single invocation
ALWAYS:
- Present the selection table to help the user choose
- Match user description to the most relevant lens
- Load the selected lens skill using the Skill tool
Core Lenses (always recommended)
| Your experiment involves... | Use this lens | Question it answers | Philosophical Mode | |-----------------------------|---------------|---------------------|--------------------| | Unclear or shifting claims | Estimand Clarity | What exactly is the claim? | Evidential | | Causal attribution without explicit assumptions | Causal Assumptions | What causal assumptions support this design? | Causal-Structural | | Baseline quality or fairness | Comparator Construction | Is the comparator fair and relevant? | Counterfactual | | Data preprocessing, splits, or feature pipelines | Pipeline Integrity | Could data handling create optimistic bias? | Integrity | | Nondeterminism, seed sensitivity, run-to-run noise | Variance & Stability | Is the signal larger than the noise? | Stability | | Asymmetric tuning, compute, or engineering effort | Fair Comparison | Are alternatives compared symmetrically? | Fairness | | Reproducing results from artifacts alone | Reproducibility & Artifacts | Could an independent party reproduce this? | Transparency | | Metric choice, proxy validity, score interpretation | Measurement Validity | Do measurements justify the interpretation? | Psychometric | | Robustness to preprocessing or modeling choices | Sensitivity & Robustness | Which assumptions are load-bearing? | Robustness | | Generalization claims beyond the test suite | Benchmark Representativeness | Does this generalize beyond the test bed? | Generalizability |
Extended Lenses (enable by experiment class)
| Your experiment involves... | Use this lens | Question it answers | Philosophical Mode | |-----------------------------|---------------|---------------------|--------------------| | Shared resources, network effects, spillovers | Unit & Interference | What is the unit, and can treatments spill over? | Causal-Structural | | Power, multiplicity, sequential monitoring | Error Budget | Are error risks sized and controlled? | Statistical | | Theory claims needing adversarial stress | Severity Testing | Would this design have caught the error? | Falsificationist | | Assignment mechanism, blocking, stratification | Randomization & Blocking | Where does comparability come from? | Design-Structural | | Confounds, history effects, co-interventions | Validity Threats | What alternative explanations survive? | Adversarial | | Multi-step exploration, adaptive allocation | Iterative Learning | How does this maximize learning per cost? | Decision-Theoretic | | Mixing discovery and confirmation in one study | Exploratory vs Confirmatory | Is this discovery or test? | Boundary | | Deployment risk, fairness, stakeholder harm | Governance & Risk | What risks arise from acting on this result? | Governance |
Workflow
Step 1: Prompt User
Ask the user:
> What aspect of your experimental design would you like to examine?
Example prompts:
- "I want to check if my causal claims are well-supported"
- "I need to verify my data pipeline doesn't leak"
- "Are my baselines fair comparisons?"
- "Could someone reproduce my experiment?"
- "Is my benchmark representative enough?"
Step 2: Match to Lens
Based on the user's description, match to the most appropriate lens using the selection tables above. If ambiguous, present the top 2-3 candidates and ask the user to choose.
Step 3: Load the Selected Lens
Use the Skill tool to load the selected /exp-lens-{slug} skill.
Step 4: Execute the Loaded Skill
The loaded lens skill takes over and runs its full analysis workflow.
Alias Table
| Alias | Lens | |-------|------| | estimand | exp-lens-estimand-clarity | | causal | exp-lens-causal-assumptions | | comparator | exp-lens-comparator-construction | | pipeline | exp-lens-pipeline-integrity | | variance | exp-lens-variance-stability | | fairness | exp-lens-fair-comparison | | reproducibility | exp-lens-reproducibility-artifacts | | measurement | exp-lens-measurement-validity | | sensitivity | exp-lens-sensitivity-robustness | | benchmark | exp-lens-benchmark-representativeness | | unit | exp-lens-unit-interference | | error | exp-lens-error-budget | | severity | exp-lens-severity-testing | | randomization | exp-lens-randomization-blocking | | validity | exp-lens-validity-threats | | iterative | exp-lens-iterative-learning | | exploratory | exp-lens-exploratory-confirmatory | | governance | exp-lens-governance-risk |
Related Skills
/mermaid- Shared diagram styling (loaded by individual lenses)/make-arch-diag- Software architecture lens counterpart/verify-diag- Verify diagram accuracy against codebase
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Trecek
- Source: Trecek/useful-claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.