Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lllllllama avatar

Ai Research Reproduction

  • 587 installs
  • 513 repo stars
  • Updated July 26, 2026
  • lllllllama/ai-paper-reproduction-skill

This is a copy of ai-research-reproduction by lllllllama - installs and ranking accrue to the original listing.

ai-research-reproduction is an agent skill that faithfully reproduces deep learning research repositories with auditable evidence and minimal untrustworthy changes for developers who need README-first, evidence-backed ML

About

ai-research-reproduction is a Rigor Reproduce compatible agent skill from lllllllama/ai-paper-reproduction-skill for README-first deep learning repository reproduction with auditable evidence and conservative patching. Listed on skills.sh with 507 installs, it guides agents to read the repository first, pick the smallest documented inference or evaluation target, coordinate intake and setup, run trusted execution, optionally attempt trusted training, and record assumptions, deviations, and human decision points. The standardized repro_outputs/ bundle captures evidence so reproduction means following documented commands and environments—not arbitrary changes to force a green run. The skill loads shared references including agent-operating-principles.md, research-rigor-principles.md, and deep-learning-experiment-principles.md when scientific comparability matters. Developers reach for ai-research-reproduction when validating paper claims, benchmarking model repos, or producing audit trails for ML experiments. It explicitly excludes paper summaries, generic environment setup alone, or isolated repo scanning without a reproduction target.

  • README-first reproduction workflow that reads repository before acting
  • Selects smallest documented inference or evaluation target
  • Enforces conservative patch rules with recorded evidence, assumptions, deviations and human decision points
  • Produces standardized repro_outputs/ bundle containing results and provenance
  • Coordinates intake, trusted setup, execution, optional training and optional paper-gap analysis

Ai Research Reproduction by the numbers

  • 587 all-time installs (skills.sh)
  • +14 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lllllllama/ai-paper-reproduction-skill --skill ai-research-reproduction

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs587
repo stars513
Last updatedJuly 26, 2026
Repositorylllllllama/ai-paper-reproduction-skill

How do you reproduce a deep learning paper repo faithfully?

Faithfully reproduce deep learning research repositories with auditable evidence and minimal untrustworthy changes.

Who is it for?

ML engineers reproducing published deep learning repositories who need minimal-trust patching and auditable experiment evidence.

Skip if: Developers who only want paper summaries, generic pip installs, or repo scans without a targeted inference or evaluation reproduction run.

When should I use this skill?

The user asks to reproduce a deep learning paper repository, validate README commands, or produce auditable ML experiment evidence.

What you get

repro_outputs/ evidence bundle with run logs, deviations, assumptions, and optional training or gap-analysis notes.

  • repro_outputs/ evidence bundle
  • Deviation and assumption log
  • Trusted inference or evaluation run results

By the numbers

  • Listed with 507 installs on skills.sh
  • Writes standardized evidence to a repro_outputs/ output bundle
  • Loads 3 shared reference principle documents during rigorous reproduction

Files

SKILL.mdMarkdownGitHub ↗

ai-research-reproduction

Purpose

Use this as the Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. The installed slug remains ai-research-reproduction for compatibility. The skill guides the agent toward a minimal trustworthy run with auditable evidence; it should not micromanage implementation details that the model can infer from the repository. Reproduction is not "make it run by changing anything"; it means faithfully reading the README, environment, weights, datasets, and documented commands, then recording results and deviations.

Start from the shared operating principles in ../../references/agent-operating-principles.md, then load ../../references/research-rigor-principles.md and ../../references/deep-learning-experiment-principles.md when scientific meaning, comparability, or experiment details are at stake.

Fit

Use this skill when all are true:

  • The target is an AI code repository with a README, scripts, configs, or

documented commands.

  • The request spans multiple trusted phases such as intake, setup, execution,

training verification, analysis, paper-gap resolution, and reporting.

  • The desired result is a small reproducible target, not broad experimentation.

Do not use this skill for paper summaries, generic environment setup, isolated repo scanning, standalone command execution, open-ended research design, or explicit candidate-only exploration.

Trusted Target Selection

Choose the smallest target that can honestly demonstrate repository-grounded reproduction:

1. documented inference 2. documented evaluation 3. documented training startup or partial verification 4. full training only after explicit user confirmation

Treat README guidance as the primary reproduction intent. Use repository files to clarify the README, not to silently replace it. When the README and paper conflict, record the conflict and use paper-context-resolver only for the narrow reproduction-critical gap.

Workflow

1. Read the README and nearby repo signals. 2. Use repo-intake-and-plan to extract documented commands and candidate targets. 3. Select and justify the minimum trustworthy target. 4. Use env-and-assets-bootstrap only for target-specific environment, checkpoint, dataset, and cache assumptions. 5. Use analyze-project only when structure, insertion points, or suspicious implementation patterns need read-only clarification. 6. Use minimal-run-and-audit for documented inference, evaluation, smoke, or sanity execution. 7. Use run-train instead when the selected trusted target is training startup, short-run verification, full kickoff, or resume. 8. Pause for human review before fuller training claims or any change that could alter dataset, split, checkpoint, preprocessing, metric, loss, model semantics, or result interpretation. 9. Write the standardized outputs and give a concise final note in the user's language when practical.

Patch Boundary

Prefer no repository edits. If edits are needed, keep them conservative and auditable:

  • Try command-line arguments, environment variables, path fixes, dependency

version fixes, or dependency-file fixes before code changes.

  • Reproduction fixes are allowed when needed, but they must not be hidden. State

what changed, why it was necessary, whether it changes scientific meaning, and whether it affects comparability with the paper, README, or baseline.

  • Avoid changing model architecture, core inference semantics, training logic,

loss functions, or experiment meaning.

  • If repository files must change, create a branch named

repro/YYYY-MM-DD-short-task, keep verified patch commits sparse, and record README-fidelity impact in PATCHES.md.

See references/patch-policy.md.

Outputs

Always target repro_outputs/:

SUMMARY.md
COMMANDS.md
LOG.md
SCIENTIFIC_CHANGELOG.md
COMPARABILITY_REPORT.md
status.json
PATCHES.md   # only if patches were applied

Use the templates under assets/ and the field rules in references/output-spec.md.

  • Put the shortest high-value summary in SUMMARY.md.
  • Put copyable commands in COMMANDS.md.
  • Put process evidence, assumptions, failures, and decisions in LOG.md.
  • Put scientific meaning and change effects in SCIENTIFIC_CHANGELOG.md.
  • Put comparison anchors and protocol deviations in COMPARABILITY_REPORT.md.
  • Put durable machine-readable state in status.json.
  • Put branch, commit, validation, and README-fidelity impact in PATCHES.md when needed.
  • Distinguish verified facts from inferred guesses.

Reference Loading

  • Load references/language-policy.md when writing human-readable outputs.
  • Load ../../references/research-rigor-principles.md before making

comparability, contribution, or research-result claims.

  • Load ../../references/deep-learning-experiment-principles.md when dataset,

split, metric, checkpoint, training, or evaluation details matter.

  • Load references/research-safety-principles.md before protocol-sensitive

decisions.

  • Load references/patch-policy.md before modifying repository files.
  • Keep specialized logic in sub-skills, scripts, templates, or references rather

than expanding this entrypoint.

Related skills

How it compares

Choose ai-research-reproduction when auditable, minimal-trust ML repo runs matter; use lighter setup skills when you only need dependencies installed without evidence tracking.

FAQ

What artifact does ai-research-reproduction standardize?

ai-research-reproduction writes a standardized repro_outputs/ bundle recording evidence, assumptions, deviations, and human decision points. The skill treats reproduction as following documented README commands and environments, not arbitrary code changes to force success.

When should ai-research-reproduction not be used?

ai-research-reproduction is not for paper summaries, generic environment setup alone, isolated repository scanning, or standalone command execution without a documented inference or evaluation reproduction target and evidence trail.

AI & Agent Buildingresearchautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.