paper-reproduction
Skill108 starsChanged 8 months agoMITView on GitHub
This skill should be used when the user asks to "reproduce a paper",
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Kayn-43/agent-configtheir own version, first seen Sep 15, 2026
- Osgood001/agentic-science-playground-skillstheir own version, first seen Aug 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Osgood001/agentic-science-playground-skills★ 2same name
- Kayn-43/agent-config★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- literature-reviewSkill
- scholar-monitoringSkill
- trend-analysisSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Call paper_search with the paper title, topic, or known identifier.
- Very specific: line 34
Call paper_judge with rubric="reproducibility" to assess implementation feasibility.
- Very specific: line 46
Call paper_summarize to extract key contributions, methods, and findings.
- Distinctive: line 50
Use the summary to inform the implementation plan in Step 4
- Very specific: line 54
Call save_to_memory with an outline of the planned implementation steps.
- Very specific: line 64
Call export_to_obsidian to create a structured Obsidian note for the paper.
- Distinctive: line 73
After completing the above workflow, proceed with code implementation using available tools (Bash, Write, etc.).
- Distinctive: line 80
Use the summary from Step 3 and the plan from Step 4 as starting context
- Very specific: line 89
When LLM-backed tools return degraded=True:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paper Reproduction Workflow
Reproduce or implement a paper: locate it, assess reproducibility, understand its contributions, save an implementation plan, and export a paper note.
Workflow
Step 1: Find the paper
Call paper_search with the paper title, topic, or known identifier.
- Parameters:
query(required; include ArXiv ID or DOI if known for direct lookup),max_results(default 10; use 3–5 for a known paper to minimize noise) - Returns: list of paper dicts with
title,abstract,authors,year,venue,arxiv_id,doi - Select the most specific match if multiple results are returned
Step 2: Judge reproducibility
Call paper_judge with rubric="reproducibility" to assess implementation feasibility.
- Parameters:
title,abstract,full_text(optional; include if available for richer analysis),rubric="reproducibility" - Returns: dimension scores (1–5) including
rigor,clarity,novelty,reproducibility,overall_score, andrecommendation - Favorable signals: high
rigorandclarityscores - Unfavorable signals: low
clarityscore may indicate reproduction difficulty; lowreproducibilityscore indicates missing implementation details (pseudocode, datasets)
Step 3: Summarize paper contributions
Call paper_summarize to extract key contributions, methods, and findings.
- Parameters:
title,abstract - Returns: dict with
summarykey (concise string covering contributions and approach) - Use the summary to inform the implementation plan in Step 4
Step 4: Save reproduction plan to memory
Call save_to_memory with an outline of the planned implementation steps.
- Parameters:
content(implementation plan text),kind("project"for structured plans or"decision"for approach decisions),user_id(default"default"),scope_type("global"or"track"if this paper belongs to a research track),scope_id(track ID ifscope_type="track"),confidence(0.0–1.0) - Include: key algorithms to implement, datasets needed, evaluation metrics, dependencies
Step 5: Export paper note
Call export_to_obsidian to create a structured Obsidian note for the paper.
- Parameters:
title,abstract,authors(list),year,venue,arxiv_id,doi(provide all available identifiers) - Returns: dict with
markdownkey — YAML-frontmattered note ready for Obsidian vault - The note provides a permanent reference alongside the implementation
Implementation Guidance
After completing the above workflow, proceed with code implementation using available
tools (Bash, Write, etc.). The Paper2Code pipeline in PaperBot
(src/paperbot/repro/) provides deeper multi-stage analysis (Planning → Blueprint →
Environment → Generation → Verification) for complex reproductions requiring the full
PaperBot backend.
For simpler reproductions:
- Use the summary from Step 3 and the plan from Step 4 as starting context
- Implement iteratively, checking against paper details in the Obsidian note
- Store implementation decisions in memory with
kind="decision"as the work progresses
Degraded Mode
paper_judge and paper_summarize require a configured LLM API key.
paper_search works without LLM.
When LLM-backed tools return degraded=True:
- The response also contains an
errorkey describing the issue - Set
OPENAI_API_KEYorANTHROPIC_API_KEYand restart the MCP server - In degraded mode, use
paper_searchto locate the paper and proceed to implementation using the raw abstract and metadata; skip Steps 2 and 3
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

