mcpField
R
repo-intake-and-plan

repo-intake-and-plan

github.com/lllllllamaDocuments486139.9k installsUpdated 5w ago
Repository

About repo-intake-and-plan

repo-intake-and-plan is the Rigor Intake helper skill for README-first reproduction work. It scans repository structure and documented commands, and conservatively classifies inference, evaluation and training candidates before any execution. It is a helper-tier skill, usually invoked by an orchestrator, and only scans and plans.

Key features

  1. 01Concise repository structure summary
  2. 02Inventory of documented commands
  3. 03Candidate classification into inference, evaluation, training or other
  4. 04Minimum trustworthy reproduction recommendation
  5. 05List of ambiguities and risks

Use cases

  1. 01Getting a fast map of a repository at the start of reproduction work
  2. 02Confirming inference and evaluation entry points before running anything
  3. 03Inspecting a repository first when the user does not want commands run yet

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lllllllama/ai-paper-reproduction-skill --skill repo-intake-and-plan

After installing, type/repo-intake-and-planin Claude Code to confirm it loaded.

Details

From the project README

repo-intake-and-plan

Use this as the Rigor Intake helper. The installed slug remains repo-intake-and-plan for compatibility.

When to apply

  • At the beginning of README-first reproduction work.
  • When the main skill needs a fast map of repo structure and documented commands.
  • When inference, evaluation, and training candidates must be classified conservatively.
  • When the user explicitly wants to inspect the repo first and not run anything yet.

When not to apply

  • When execution has already started and the task is now about running commands or writing outputs.
  • When the target is not a repository-backed reproduction task.
  • When the user only wants paper interpretation without repo inspection.
  • When the user already has a selected documented command and only needs setup or execution.

Clear boundaries

  • This skill scans and plans.
  • This skill is helper-tier and should usually be orchestrator-invoked.
  • It does not install environments.
  • It does not prepare large assets.
  • It does not execute substantive reproduction commands.
  • It does not decide high-risk patching.

Input expectations

  • Target repository path.
  • Access to README and common project files if present.
  • Optional user hints about desired priority, such as inference-first.

Output expectations

  • concise repo structure summary
  • documented command inventory
  • inferred candidate categories: inference, evaluation, training, other
  • minimum trustworthy reproduction recommendation
  • notable ambiguity or risk list

Notes

Use references/repo-scan-rules.md and helper scripts under scripts/.

Comments

Markdown supported