brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/results-analysis
results-analysis
VerifiedThis skill should be used when the user asks to "analyze experimental results", "run strict statistical analysis", "compare model performance", "generate scientific figures", "check significance", "do ablation analysis", or mentions interpreting experiment data with rigorous statistics and visualization. It focuses on strict analysis bundles, not Results-section prose.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.7 KB |
| USAGE.md | markdown | 2.9 KB |
| examples/example-analysis-report.md | markdown | 2.2 KB |
| examples/example-figure-catalog.md | markdown | 1.3 KB |
| examples/example-stats-appendix.md | markdown | 1.2 KB |
| references/analysis-depth.md | markdown | 844 B |
| references/common-pitfalls.md | markdown | 998 B |
| references/figure-interpretation.md | markdown | 939 B |
| references/statistical-methods.md | markdown | 16.1 KB |
| references/statistical-reporting.md | markdown | 1.1 KB |
| references/visualization-best-practices.md | markdown | 6.4 KB |
references/statistical-reporting.md
View on GitHub# Statistical Reporting Standard
## Minimum reporting package
For every major comparison, report:
- metric definition and direction,
- unit of analysis,
- sample size / run count,
- descriptive statistics,
- uncertainty estimate,
- inferential test,
- effect size,
- correction strategy when multiple contrasts exist,
- limitation if assumptions or sample size are weak.
## Required fields
### Descriptive
- `mean ± std` when repeated runs are comparable
- `95% CI` when inference is discussed
- median / IQR when distribution is strongly non-normal
### Inferential
- exact test name
- test statistic and degrees of freedom when applicable
- p-value format
- effect size
- correction method for multiple comparisons
## Do not do these
- report only best run
- report only p-values
- hide non-significant comparisons
- treat unstable trends as conclusions
- switch tests without stating why
## Default wording rule
Use three layers:
1. **Observation** — what changed numerically
2. **Support** — what the test/effect size says
3. **Boundary** — what remains uncertain
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |