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/report-structure.md

View on GitHub
# Results Report Structure

## 1. Executive Summary
Answer:
- what was tested,
- what the highest-confidence conclusion is,
- what decision this changes.

## 2. Experiment Identity and Decision Context
Answer:
- which experiment line this belongs to,
- why this round was run,
- what prior uncertainty or decision it was meant to resolve.

## 3. Setup and Evaluation Protocol
Answer:
- datasets / subjects / splits,
- methods compared,
- primary metrics,
- repeated-run structure,
- any deviations from prior protocol.

## 4. Main Findings
Answer:
- what changed most,
- which comparison matters most,
- where the largest gains or failures appear.

## 5. Statistical Validation
Answer:
- what evidence supports the major claims,
- what tests were used,
- where the evidence is weak.

## 6. Figure-by-Figure Interpretation
For each main figure:
- why it is shown,
- what to notice,
- what is supported,
- what remains uncertain.

## 7. Failure Cases / Negative Results / Limitations
Answer:
- what did not work,
- what instability appeared,
- what limits the current conclusion.

## 8. What Changed Our Belief
Answer:
- which prior hypothesis is strengthened,
- weakened,
- or still unresolved.

## 9. Next Actions
Answer:
- stop / continue / ablate / scale / write.

## 10. Artifact and Reproducibility Index
List:
- source artifacts,
- figure paths,
- scripts/logs,
- linked Obsidian notes.
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