30-SECOND BRIEF
What it does—and when it fits
Repo Intake and Plan is a README-first helper for research-code repositories. It inventories documented commands and common project files, classifies inference, evaluation, and training candidates, recommends the smallest trustworthy reproduction target, and records ambiguity and risk without setting up environments or running experiments.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/repo-intake-and-plan/~/.claude/skills/repo-intake-and-plan/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add lllllllama/rigorpilot-skills --skill repo-intake-and-plan --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Inventory repository entry points
Collect documented commands, configuration, and likely experiment surfaces.
Classify run candidates
Distinguish smoke, inference, evaluation, and training paths before choosing one.
Recommend a minimal target
Propose the smallest run that can produce trustworthy evidence.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to lllllllama/rigorpilot-skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- It does not create environments, download assets, execute commands, perform paper lookup, or write the final report.
- A repository with weak documentation may require a separate context-resolution step before planning is reliable.
BEST FIT
Who it is for
Researchers beginning a repository reproduction
Teams triaging unfamiliar ML codebases
BEFORE YOU USE IT
Risks to review before use
Planning from incomplete repository evidence
README commands can be stale or omit scientific assumptions. Mark ambiguity, avoid high-cost runs, and resolve critical paper or asset gaps before treating the plan as reproducible.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at lllllllama/rigorpilot-skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.