Skills lllllllama rigorpilot-skills RigorPilot

repo-intake-and-plan

Use it when:
You're starting to reproduce a deep-learning repo and want it mapped before anything runs.
It does:
Reads the README and setup files, lists the documented commands and sorts them into inference, evaluation, training or other.
You get:
A short repo summary, a command list, the smallest documented run worth trying first, and the ambiguities and risks.
Doesn't:
Install anything, download data or model weights, run the commands or patch code.
Usually called by:
RigorPilot's main skill, which reproduces a research repo from its README, as its first step.

Skill 2 of 11 in the RigorPilot bundle, after ai-research-reproduction and before paper-context-resolver.

TL;DR

The first step in RigorPilot, a set of skills that reproduces deep-learning research code by following its README. It reads the README and the usual project files (requirements.txt, environment.yml, pyproject.toml, setup.py, Dockerfile) and looks for clues in folders such as configs, scripts and examples. Commands are sorted by what they do: running the model on inputs (inference), scoring it on a benchmark (evaluation), training or fine-tuning it, or other steps like installing, downloading and preprocessing. It's conservative: explicit README commands win over guesses from file names, guessed categories are marked as inferred, and ambiguity is written down rather than settled by assumption. The run it recommends is the smallest one the README documents that can still be trusted, and you can steer it with a priority, such as inference first. Setup and the run itself are left to other RigorPilot skills.

Summarizes the skill at fb3ccdf.

npx skills add https://github.com/lllllllama/rigorpilot-skills --skill repo-intake-and-plan
Total Downloads
491,961 on skills.sh, Nov 9, 2026
Repo stars
486 lllllllama/rigorpilot-skills
First seen
Mar 30, 2026 on skills.sh
Weekly Downloads
7.3K
+22616% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 2132
Sep 2842
Oct 560
Oct 123,505
Oct 1910,921
Oct 2611,048
Nov 28,742
Nov 97,269
Category

Research reproduction, financial data, charts and diagrams.

Type

A multi-step process the agent follows: interview, debug, run a TDD loop, review.

Effect

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.

Needs

Instructions only. Works in any agent that supports skills.

Publisher

Everyone else. Unverified vendor claims default to community.

Topics
Stack

SKILL.md

From lllllllama/rigorpilot-skills at fb3ccdf. Checked daily, last changed Oct 20, 2026.

Frontmatter
name: repo-intake-and-plan
description: 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.

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/.