brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/results-report
results-report
VerifiedThis 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| examples/example-results-report.md | markdown | 3.9 KB |
| references/EVIDENCE-PROPAGATION.md | markdown | 896 B |
| references/decision-oriented-analysis.md | markdown | 542 B |
| references/figure-interpretation.md | markdown | 628 B |
| references/report-naming.md | markdown | 1.0 KB |
| references/report-structure.md | markdown | 1.4 KB |
| references/statistical-completeness.md | markdown | 543 B |
references/report-naming.md
View on GitHub# Report Naming Standard
## Filename
Use:
```text
YYYY-MM-DD--{experiment-line}--r{round}--{purpose}.md
```
Rules:
- date must be the report date,
- `experiment-line` should be short and stable,
- `round` should be zero-padded only if that is already the project convention; otherwise `r3` / `r03` are both acceptable if used consistently,
- `purpose` should describe why the report exists, not a vague label like `summary` unless that is truly the purpose.
Recommended purpose values:
- `transfer-summary`
- `ablation-report`
- `failure-analysis`
- `robustness-check`
- `round-review`
## Title
Use:
```text
{Experiment Line} / Round {N} / {Purpose} / {YYYY-MM-DD}
```
## Frontmatter fields
Required:
- `type: results-report`
- `date`
- `experiment_line`
- `round`
- `purpose`
- `status`
- `source_artifacts`
- `linked_experiments`
- `linked_results`
## Placement in Obsidian
Internal reports go to:
```text
Results/Reports/{filename}
```
Do not put internal experiment reports in `Writing/` unless they are already manuscript/slides/rebuttal material.
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: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |