Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/results-analysis

results-analysis

Verified

This 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.

references/figure-interpretation.md

View on GitHub
# Figure Interpretation Guide

A scientific figure is incomplete until the text answers:
1. why the figure exists,
2. what the reader should notice,
3. why that observation matters.

## Minimal interpretation block

For each figure, provide:
- **Purpose**: the research question this figure addresses
- **Observation**: the concrete pattern seen in the plot
- **Interpretation**: the mechanism or explanation supported by the evidence
- **Implication**: what decision, next experiment, or claim changes because of it

## Caption checklist

A usable caption should specify:
- what is plotted,
- what each axis means,
- sample size,
- what error bars / ribbons represent,
- any normalization or smoothing,
- any significance marker convention.

## Anti-patterns
- restating the axis labels as “interpretation”
- giving only aesthetic comments
- making causal claims unsupported by the plot
- repeating the caption without adding insight
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall