Code Review & Testing · IN-DEPTH PROFILE

Repo Intake and Plan Skill

Map research-code entry points and choose a minimal, trustworthy reproduction target.

View listed source ↗Installation guide ↓
Best for

Researchers beginning a repository reproduction

What you get

Inventory repository entry points + Classify run candidates

Main limitation

It does not create environments, download assets, execute commands, perform paper lookup, or write the final report.

First risk

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.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-24

Pinned revision · fb3ccdf5

Open pinned commit ↗
SkillSignal profileEditorial metadata

Updated 2026-09-24

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

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.

This is aimed at Researchers beginning a repository reproduction. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Inventory repository entry pointsCollect documented commands, configuration, and likely experiment surfaces.
  • Classify run candidatesDistinguish smoke, inference, evaluation, and training paths before choosing one.
  • Recommend a minimal targetPropose the smallest run that can produce trustworthy evidence.
What makes it different
  • 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.
Community signalNo attributed third-party rating yet

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

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.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add lllllllama/rigorpilot-skills --skill repo-intake-and-plan --agent claude-code
Personal install
npx skills add lllllllama/rigorpilot-skills --skill repo-intake-and-plan --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/repo-intake-and-plan/
Personal path~/.claude/skills/repo-intake-and-plan/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Inventory repository entry points

Collect documented commands, configuration, and likely experiment surfaces.

02

Classify run candidates

Distinguish smoke, inference, evaluation, and training paths before choosing one.

03

Recommend a minimal target

Propose the smallest run that can produce trustworthy evidence.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to lllllllama/rigorpilot-skills.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. It does not create environments, download assets, execute commands, perform paper lookup, or write the final report.
  2. A repository with weak documentation may require a separate context-resolution step before planning is reliable.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Claude Code + Codex

frontend-design

Design constraints that push generated interfaces beyond generic AI UI.
Tradeoff to check
Aesthetic judgments remain subjective and still need stakeholder review.
First risk
Style over function · Medium
Source state
Pinned · 34040c9c
Open frontend-design profile ↗
02

Same job family · native to Codex + Claude Code

web-design-guidelines

Review interfaces against practical web design and accessibility rules.
Tradeoff to check
It depends on network access and a live guideline document whose contents can change over time.
First risk
Rule drift or context-free findings · Medium
Source state
Pinned · 063bee94
Open web-design-guidelines profile ↗
03

Same job family · native to Codex + Claude Code

anti-ui-slop

Instruction-only, product-specific UI design contracts with optional real-interface evidence and a hard finish gate.
Tradeoff to check
Repository evidence is required; UIZZE references or user-provided screenshots are optional, and missing reference evidence should be labeled rather than guessed.
First risk
Copying external interface patterns too literally · Medium
Source state
Pinned · 1f564408
Open anti-ui-slop profile ↗
Compare more in the directory →

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

Medium

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.

Medium

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.

COMMON QUESTIONS

Repo Intake and Plan Skill FAQ

What is the Repo Intake and Plan Skill?

Map research-code entry points and choose a minimal, trustworthy reproduction target. 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.

How do I install the Repo Intake and Plan Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed skills.sh page and upstream repository; verify the current SKILL.md.

Is the Repo Intake and Plan Skill safe to use?

SkillSignal checked the source on 2026-09-24, but that is not a runtime test or security certification. Review the “Planning from incomplete repository evidence” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

repository-intakereproduction-planml-research

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.