repo-intake-and-plan
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
适合你，如果需要从GitHub仓库快速提取命令并制定复现方案
npx oh-my-skill add lllllllama/ai-paper-reproduction-skill/repo-intake-and-plancurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- lllllllama/ai-paper-reproduction-skill/repo-intake-and-plannpx oh-my-skill verify lllllllama/ai-paper-reproduction-skill/repo-intake-and-plan怎么用
商店整理自技能原文 · 版本 56bc41c · 表述以原文为准装上后，Claude 会先扫描仓库，读取 README 等文件，提取文档中的命令，并分类为推理、评估、训练等，最后给出最小的可信复现计划。
在复现任务开始时，需要先了解仓库结构和文档命令时触发。不要在执行命令或设置环境时使用。
技能原文 SKILL.md
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/.