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.
Results Report Write the complete post experiment summary report after analysis artifacts are ready. This skill is for the stage after . Role boundary does strict statistics, real figures, figure interpretation scaffolding, stats appendix. does complete experiment wrap up report, decision oriented narrative, figure by figure interpretation inside a coherent structure, limitations, failure cases, and next actions, Obsidian write back into . Do not replace strict analysis with confident prose. If…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/results-report · pinned to the source commit
# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/33-Galaxy-Dawn-claude-scholar/skills/results-report" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/33-Galaxy-Dawn-claude-scholar/skills/results-report" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/results-report
Scanner static-checks@0.1.0 · commit 692e9fa3fea4. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.