PaperclipOrg
Claude Agent Skill · by Lllllllama

Repo Intake And Plan

Takes a fresh repo and does the boring first pass: reads the README, scans for setup scripts and documented commands, then categorizes what looks like inference

Install
Terminal · npx
$npx skills add https://github.com/obra/superpowers --skill test-driven-development
Works with Paperclip

How Repo Intake And Plan fits into a Paperclip company.

Repo Intake And Plan drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md47 lines
Expand
---name: repo-intake-and-plandescription: Narrow helper skill for README-first AI 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 ## 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/`.