repo-intake-and-plan
Skill495 starsChanged 6 months agoMITView on GitHub
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.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-research-exploreSkill
- ai-research-reproductionSkill
- analyze-projectSkill
- env-and-assets-bootstrapSkill
- explore-codeSkill
- explore-runSkill
- minimal-run-and-auditSkill
- paper-context-resolverSkill
- run-trainSkill
- safe-debugSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this as the Rigor Intake helper.
- Distinctive: line 14
When the main skill needs a fast map of repo structure and documented commands.
- Distinctive: line 15
When inference, evaluation, and training candidates must be classified conservatively.
- Distinctive: line 16
When the user explicitly wants to inspect the repo first and not run anything yet.
- Distinctive: line 20
When execution has already started and the task is now about running commands or writing outputs.
- Distinctive: line 21
When the target is not a repository-backed reproduction task.
- Distinctive: line 22
When the user only wants paper interpretation without repo inspection.
- Distinctive: line 23
When the user already has a selected documented command and only needs setup or execution.
- Very specific: line 50
Use references/repo-scan-rules.md and helper scripts under scripts/.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

