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.
Save adds this to your Playground favorites. Hearts show appreciation.
How you can use it
- Scan a code repository and list the commands its README documents.
- Sort documented commands into inference, evaluation, and training groups before running anything.
- Get a short plan for the smallest trustworthy way to reproduce a research repo.
Who it's for
- Researchers trying to reproduce a deep learning paper's code who want to check it before running anything.
- Engineers reviewing an unfamiliar machine learning repo before spending time setting it up.
Written by AI from this item's description. Check the source before relying on it.
See what it would do for your project in Playground →Set it up
Pick the app you use.
repo-intake-and-plan
- 1
Open Plugins → Skills
Left sidebar → Plugins, then the Skills tab.
- 2
Add → Upload from your computer
Pick the SKILL.md (or Create with editor and paste the text), then Create.
- 3
Use it with /
In a chat, type / and pick the skill, then write your request.
Show the skill file
# 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/`.
Read a skill before you install it: it tells the AI what to do. Promptu never installs or runs anything.
Install from the command line
npx skills add https://github.com/lllllllama/rigorpilot-skills
Review commands before running them. Promptu never runs code on your machine or pushes changes to your repo.

