agentleFS
Sign inStart free
JunMA98JunMA98/Computer-science-claude-skills/skills/paper-to-code/SKILL.md

paper-to-code

Skill3 starsChanged 8 months agoMITView on GitHub

Use when implementing a paper, method, or system from a publication and you need to translate claims, methods, and diagrams into an executable implementation plan.

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use latex-formatting, novelty-assessment and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lingzhi227Skill

    latex-formatting

    Handle LaTeX formatting, templates, and styling for academic papers. Set up conference templates (ICML, ICLR, NeurIPS, AAAI, ACL), fix formatting issues, manage packages, and ensure venue-specific compliance. Use when the user needs to set up a paper template, fix LaTeX formatting, or prepare for submission.

    Also in 4 projects that use this

  • lingzhi227Skill

    novelty-assessment

    Assess research idea novelty through systematic literature search. Multi-round search-evaluate loops with harsh critic persona. Binary novel/not-novel decision with justification. Use before committing to a research direction.

    Also in 4 projects that use this

  • michaelboedingSkill

    slide-generation

    Use this skill to create presentation slides from structured content. Triggers: "create slides", "generate presentation", "make powerpoint", "create pptx", "build slides", "presentation from content", "slide deck", "slides for" Outputs: PPTX files, Markdown slides, or HTML presentations. Used by: pitch-deck-agent, market-researcher-agent, and other agents needing slides.

    Also in 4 projects that use this

  • OpenAISkill

    idea-generation

    Use when triaging public-equity idea candidates. Do not use for final trade recommendations, pitches, memos, or models.

    Also in 3 projects that use this

  • Hugging FaceSkill

    self-review

    Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the `@claude` CI (checks the diff against references/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what to leave for the actual review. Report-only — does not edit files.

    Also in 4 projects that use this

  • +6 more from lingzhi227

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    do not present inferred details as if the paper explicitly stated them

    line 41
  2. Distinctive:

    keep reproduction goals separate from extension goals

    line 42
  3. Distinctive:

    prefer the simplest faithful baseline before optimization

    line 43

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Purpose

Convert a paper into a concrete implementation roadmap without hiding ambiguities.

When To Use

  • implementing a method from a paper or preprint
  • turning a paper idea into a prototype or baseline
  • extracting architecture, training, and evaluation details from text
  • estimating what is missing before starting reproduction or extension work

Inputs

  • paper, notes, figures, appendices, or pseudo-code
  • any released repo, checkpoint, or supplemental material if available
  • target implementation scope and resource constraints

Outputs

  • implementation map from paper components to code modules
  • list of explicit versus inferred details
  • dependency order for coding tasks
  • acceptance tests tied to paper claims
  • list of missing assumptions or ambiguous steps

Workflow

  1. Extract the paper's main claims and component boundaries.
  2. Convert each contribution into modules, data flow, and interfaces.
  3. Separate paper-stated details from inferred implementation choices.
  4. Define a build order that reaches a testable baseline early.
  5. Tie implementation milestones back to paper claims and evaluation targets.

Constraints

  • do not present inferred details as if the paper explicitly stated them
  • keep reproduction goals separate from extension goals
  • prefer the simplest faithful baseline before optimization
  • record ambiguities early so they do not disappear into code guesses

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free