reproduce-papers

Plan and execute reproducible computer science paper reproductions with artifact inventory and gap tracking.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Alanxtl/skills --skill reproduce-papers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reproduce-papers
Source: https://github.com/Alanxtl/skills/tree/main/reproduce-papers
Command: npx skills add https://github.com/Alanxtl/skills --skill reproduce-papers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps researchers and practitioners turn scholarly papers into traceable, reproducible experiments by guiding them from initial reading to artifact inventory, runnable drafts, gap tracking, and result validation.

Core Features & Use Cases

  • Paper reading to capture problem definition, inputs and outputs, core pipeline, interfaces, and evaluation setup.
  • Artifact and environment inventory to pin down data, code, dependencies, hardware, and runtimes.
  • Runnable draft construction to produce the smallest end-to-end path that verifies the main claim without requiring full fidelity.
  • Gap tracking to log missing details, deviations, and supporting evidence for auditability.
  • Result comparison to align reproduced results with the paper's claims and metrics.

Quick Start

Start from the paper, inventory artifacts and environments, build a minimal runnable draft, and record gaps with evidence for auditability.

Frequently Asked Questions about reproduce-papers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reproduce a computer science paper and track missing artifacts?

To reproduce a computer science paper, you inventory artifacts and environments, build a minimal runnable draft, track gaps with evidence, and compare reproduced results against the paper's claims for auditability.

What is a runnable draft for paper reproduction and when do I need it?

A runnable draft is the smallest end-to-end execution path verifying a paper's main claim without full fidelity. You need it to validate reproducibility before investing in complete environment setup and exact dependency matching.

How do I inventory code, data, and dependencies for a reproducible experiment?

Inventoring artifacts for reproducible experiments involves pinning down data, code, dependencies, hardware specifications, and runtimes. This captures the complete environment needed to execute and validate the scholarly paper's pipeline.

Can I reproduce a paper's results if some implementation details are missing?

Yes, you can reproduce results with missing details by using gap tracking. This logs missing information, deviations from the paper, and supporting evidence, maintaining traceability and auditability throughout the reproduction workflow.

How do I validate reproduced results against a paper's original claims?

Validating reproduced results requires aligning your experimental outputs with the paper's claims and metrics. This involves comparing results, documenting deviations, and capturing evidence to ensure the reproduction satisfies traceability requirements.

What's the best way to ensure traceability when reproducing scholarly papers?

The best way to ensure traceability is maintaining an artifact inventory, building runnable drafts, and continuously tracking gaps with supporting evidence. This workflow captures deviations and provides full auditability for the reproduction process.