Skip to content

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

results-report

Verified

This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.

references/EVIDENCE-PROPAGATION.md

View on GitHub
# Evidence Propagation

Use this file to keep `results-analysis` outputs aligned with the final report.

## Mapping rule

- `analysis-report.md` -> main findings and narrative summary
- `stats-appendix.md` -> test choice, uncertainty, effect size, correction rule
- `figure-catalog.md` -> figure purpose and per-figure interpretation scaffolding
- figure files -> visual evidence cited in `Figure-by-Figure Interpretation`

## Minimum statistical carry-over

Every strong claim in a results report should preserve:
- sample size or run/seed count,
- metric definition,
- uncertainty summary,
- test name,
- effect size when relevant,
- multiple-comparison handling when relevant.

## Unsupported claim rule

If the analysis bundle does not support a claim strongly enough, keep the claim tentative and say why.
Do not upgrade a suggestive result into a decisive conclusion during report writing.
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