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

Ai Research Reproduction

  • 176k installs
  • 512 repo stars
  • Updated July 26, 2026
  • lllllllama/rigorpilot-skills

ai-research-reproduction is a Claude Code skill for README-first deep learning repository reproduction with end-to-end intake, setup, execution, and evidence recording.

About

A repository reproduction skill for deep learning projects. Use it when you want a minimal trustworthy run that reads the README first, selects the smallest documented target, and records all evidence and deviations.

  • README-first deep learning repository reproduction with end-to-end flow
  • Selects smallest trustworthy target (inference, evaluation, or training)
  • Records all assumptions, deviations, and evidence in standardized outputs

Ai Research Reproduction by the numbers

  • 176,011 all-time installs (skills.sh)
  • +25,339 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #2 of 2,066 Data Science & ML skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

ai-research-reproduction capabilities & compatibility

Capabilities
repository intake · environment bootstrap · execution orchestration · evidence collection
Use cases
research · debugging · testing
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill ai-research-reproduction

Add your badge

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

Listed on Skillselion
Installs176k
repo stars512
Security audit3 / 3 scanners passed
Last updatedJuly 26, 2026
Repositorylllllllama/rigorpilot-skills

What it does

Reproduce deep learning repository results with minimal trustworthy flow and auditable evidence.

Who is it for?

Minimal trustworthy reproduction,Baseline verification,Training startup or short-run verification

Skip if: Paper summaries,Generic environment setup,Standalone command execution,Broad research assistance

When should I use this skill?

The target is an AI repository with README, scripts, and documented commands, and the request spans multiple trusted phases (intake, setup, execution, analysis).

What you get

Standardized repro_outputs/ bundle with SUMMARY.md, COMMANDS.md, LOG.md, SCIENTIFIC_CHANGELOG.md, COMPARABILITY_REPORT.md, status.json, and optional PATCHES.md.

  • repro_outputs/SUMMARY.md
  • repro_outputs/COMMANDS.md
  • repro_outputs/LOG.md

By the numbers

  • 7 standardized output files documenting reproduction with assumptions and deviations

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

Forks & variants (3)

Ai Research Reproduction has 3 known copies in the catalog totaling 617 installs. They canonicalize to this original listing.

How it compares

Use ai-research-reproduction for full README-first orchestration; use repo-intake-and-plan when you only need target selection before committing to a full reproduction run.

FAQ

What is a minimum trustworthy target?

In order: (1) documented inference, (2) documented evaluation, (3) training startup or partial verification, (4) full training only after explicit confirmation.

Are code changes allowed?

Yes, but must be conservative, auditable, and recorded in PATCHES.md with README-fidelity impact.

Is Ai Research Reproduction safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Data Science & MLpipelinesdatabasesanalytics

This week in AI coding

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

unsubscribe anytime.