GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
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…
Install Results Report
$ npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar results-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/results-report .claude/skills/results-report && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "results-report" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/results-report into .claude/skills/results-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "results-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/results-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar results-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/results-report .agents/skills/results-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "results-report" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/results-report into .agents/skills/results-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "results-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar results-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/results-report .cursor/skills/results-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "results-report" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/results-report into .cursor/skills/results-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "results-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Galaxy-Dawn/claude-scholar.git --path skills/results-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar results-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/results-report .gemini/skills/results-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "results-report" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/results-report into .gemini/skills/results-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "results-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Galaxy-Dawn/claude-scholar results-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/results-report .github/skills/results-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "results-report" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/results-report into .github/skills/results-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "results-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar results-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/results-report .opencode/skills/results-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "results-report" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/results-report into .opencode/skills/results-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "results-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
results-report- GitHub stars
- 5.7k
- Used in
- 1 other repo
- Token cost
- ~1.6k tokens
- SKILL.md length
- 662 words
- Files
- 8 (incl. references)
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 6 steps: Confirm the report object → Read the strict analysis bundle → Write the report as a decision object → …
- Asks to write an experiment report
- SKILL.md covers Role boundary, Default output, Required frontmatter and Default report structure, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Results Report is an agent skill from Galaxy-Dawn/claude-scholar. 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.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `examples/example-results-report.md`, `references/EVIDENCE-PROPAGATION.md` and `references/decision-oriented-analysis.md`).
It sits in Research & Science, covering Deep research. The repository describes itself as: Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding… The licence is MIT.
When your agent uses it
- Asks to write an experiment report
- Summarize experimental results
- Do experiment retrospection
- Write a results report
Example prompts
- “write an experiment report”
- “summarize experimental results”
- “do experiment retrospection”
- “/results-report”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9037873. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Results Report loads about 1.6k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 662 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Galaxy-Dawn/claude-scholar at commit 9037873, republished under its MIT licence (© Galaxy-Dawn). 662 words, ~1,588 tokens.
Download SKILL.mdSave it as
.claude/skills/results-report/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- results-report
- description
- 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.
- version
- 0.1.0
- tags
- Research, Reporting, Experiments, Obsidian
Results Report
Write the complete post-experiment summary report after analysis artifacts are ready.
This skill is for the stage after results-analysis.
Role boundary
results-analysis does
- strict statistics,
- real figures,
- figure interpretation scaffolding,
- stats appendix.
results-report 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
Results/Reports/.
When the task is to create or redesign paper-ready figures/tables themselves, rely on publication-chart-skill instead of expanding results-report into figure/table production.
Do not replace strict analysis with confident prose. If the analysis bundle is missing, first identify the blocker and request or produce the missing bundle.
Hard gate: do not write a complete report when analysis-report.md, stats-appendix.md, figure-catalog.md, provenance, or the primary comparison question is missing. In that case, write only a blocker summary and route back to results-analysis.
Default output
The default report is an internal research report, not manuscript prose.
It should be named as:
YYYY-MM-DD--{experiment-line}--r{round}--{purpose}.mdExample:
2026-03-18--freezing--r03--transfer-summary.md2026-03-18--contrastive-adversarial--r02--ablation-report.md
The note title should be:
{Experiment Line} / Round {N} / {Purpose} / {YYYY-MM-DD}Read references/report-naming.md before finalizing the filename or note title.
Required frontmatter
---
type: results-report
date: 2026-03-18
experiment_line: freezing
round: 3
purpose: transfer-summary
status: active
source_artifacts:
- analysis-output/analysis-report.md
- analysis-output/stats-appendix.md
linked_experiments:
- Experiments/Freezing-Study.md
linked_results:
- Results/Freezing-vs-Adapter.md
---Default report structure
The report must include all sections below.
- Executive Summary
- Experiment Identity and Decision Context
- Setup and Evaluation Protocol
- Main Findings
- Statistical Validation
- Figure-by-Figure Interpretation
- Failure Cases / Negative Results / Limitations
- What Changed Our Belief
- Next Actions
- Artifact and Reproducibility Index
Read references/report-structure.md before writing.
Workflow
1. Confirm the report object
Lock these fields first:
- date,
- experiment line,
- round,
- purpose,
- linked experiment note,
- linked durable result note if one already exists.
If round is unknown, do not silently invent a semantic round. Use r00 only as a temporary placeholder and state that it should be normalized later.
2. Read the strict analysis bundle
Minimum required inputs:
analysis-report.mdstats-appendix.mdfigure-catalog.md- actual figures, if available
If these are missing, either generate them first with results-analysis or explicitly state which claims cannot be supported.
Do not turn loose CSV/Markdown artifacts into a polished report unless the strict analysis bundle has already validated unit of analysis, primary metric, and claim wording.
3. Write the report as a decision object
This report is not a transcript of outputs.
Each section must answer a real question:
- What did we test?
- What changed numerically?
- What is actually supported?
- What failed or remains uncertain?
- What should we do next?
Read references/decision-oriented-analysis.md for the expected reasoning depth.
Show full SKILL.md (269 more words)Show less
4. Interpret figures inside the report
Do not only attach figures.
For each main figure:
- introduce why it is included,
- state the key observation,
- explain the supported interpretation,
- explain the decision implication.
Read references/figure-interpretation.md and references/statistical-completeness.md as needed.
5. Choose the write target explicitly
If the current repo is bound to an Obsidian project knowledge base:
- create or update
Results/Reports/{report-name}.md, - link back to the relevant
Experiments/note, - update the matching canonical
Results/note when a durable conclusion is now supported, - append a short trace to today's
Daily/note, - update
.claude/project-memory/<project_id>.md.
If the repo is not bound:
- write the report as a local markdown artifact in the requested output location or next to the analysis bundle,
- keep the same filename contract,
- explicitly say that no Obsidian write-back was attempted.
Use obsidian-project-kb-core conventions only for bound repos. Internal experiment reports belong in Results/Reports/, not Writing/.
6. End with explicit next actions
The report must end with operational decisions, for example:
- stop a weak branch,
- schedule one missing ablation,
- promote a stable finding into manuscript-facing writing,
- update the active plan.
Required quality bar
- The report must be dateable, searchable, and attributable to one experiment line and one round.
- The report must cite actual evidence from the analysis bundle.
- The report must include negative results when they matter.
- The report must separate stable conclusion from tentative interpretation.
- The report must say what changed in project belief and what should happen next.
- The report must preserve Claim Candidate wording and must not promote
speculativeorobservedclaims into decisive conclusions.
Reference files
Load only what is needed:
references/report-structure.mdreferences/report-naming.mdreferences/figure-interpretation.mdreferences/statistical-completeness.mdreferences/decision-oriented-analysis.mdreferences/EVIDENCE-PROPAGATION.mdexamples/example-results-report.md
© Galaxy-Dawn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in skills/results-report of Galaxy-Dawn/claude-scholar.
- SKILL.md
- examples/example-results-report.md
- references/EVIDENCE-PROPAGATION.md
- references/decision-oriented-analysis.md
- references/figure-interpretation.md
- references/report-naming.md
- references/report-structure.md
- references/statistical-completeness.md
Open the folder on GitHubat commit 9037873
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Galaxy-Dawn/claude-scholar, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Results Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Results Report this skillGalaxy-Dawn/claude-scholar | 5.7k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Deep Research WorkflowTokenRhythm/opensquilla | 7.1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Deep Researchsanjay3290/ai-skills | 432 | 9 repos | ~683 | Automated safety check: Notes | Apache-2.0 | |
| Horizontal-Vertical Deep ResearchKKKKhazix/khazix-skills | 21k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Academic Research PipelineImbad0202/academic-research-skills | 51k | — | ~15k | Automated safety check: Pass | Custom licence |
Similar skills
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
Deep Research
sanjay3290/ai-skills
Execute autonomous multi-step research using Google Gemini Deep Research Agent.
Horizontal-Vertical Deep Research
KKKKhazix/khazix-skills
Runs a two-axis deep research method on a product, company, concept or person: its full history over time, compared with peers today, delivered as a typeset PDF report.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
Academic Research Suite for Codex
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
More from Galaxy-Dawn/claude-scholar
All 34 skills in this repoCitation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
Skill Improvement Plan Executor
Galaxy-Dawn/claude-scholar
Reads an improvement-plan file from a companion quality-review skill and applies its suggested fixes to a Claude Skill, backing up first.
Skill Quality Reviewer
Galaxy-Dawn/claude-scholar
Scores a skill across description, content organization, writing style and structure, then produces letter grades and a prioritized improvement plan.
UI/UX Design System Advisor
Galaxy-Dawn/claude-scholar
Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.
Daily Paper Digest
Galaxy-Dawn/claude-scholar
Finds recent arXiv and bioRxiv papers on a topic, narrows them in stages to one pick per field, and writes bilingual Chinese and English summaries.
Nature Data
Galaxy-Dawn/claude-scholar
Prepare, audit, or revise Nature-ready Data Availability statements, data repository plans, dataset citations, and FAIR metadata checklists for manuscripts.
Related
Categories
Questions about Results Report
What does Results Report do?
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…. Results Report is an agent skill from Galaxy-Dawn/claude-scholar. 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.
When should I use Results Report?
Results Report fits situations like: asks to write an experiment report; summarize experimental results; do experiment retrospection; write a results report.
How do I install Results Report in Claude Code?
Run `npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a claude-code`. Or copy the skill folder (skills/results-report in Galaxy-Dawn/claude-scholar) into .claude/skills/results-report in your project. Claude Code loads it when a task matches its description.
How do I install Results Report in Codex?
Run `npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a codex`. Or copy the skill folder (skills/results-report in Galaxy-Dawn/claude-scholar) into .agents/skills/results-report in your project. Codex loads it when a task matches its description.
Can I use Results Report in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Galaxy-Dawn/claude-scholar --skill results-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/results-report, .gemini/skills/results-report, .github/skills/results-report and .opencode/skills/results-report in your project.
What does Results Report need to run?
SKILL.md names no scripts, command-line tools or credentials: Results Report is instructions for the agent only.
Does Results Report access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Results Report safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Results Report use?
Results Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Results Report use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.
What are the alternatives to Results Report?
Skills that share tags, products or a category with Results Report: GitHub Deep Research (bytedance/deer-flow, 84k stars), Deep Research Workflow (TokenRhythm/opensquilla, 7.1k stars), Deep Research (sanjay3290/ai-skills, 432 stars) and Horizontal-Vertical Deep Research (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Results Report?
Galaxy-Dawn (a GitHub user) maintains it in Galaxy-Dawn/claude-scholar, which has 5,725 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 23, 2026.
Source: Galaxy-Dawn/claude-scholar on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.