CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-loop

Runs the detached, resumable PRP pipeline in fresh headless CLI sessions, cycling plan, implementation, PR, review, and corrections with persisted state and safety bounds. Use only when the user explicitly asks to "run the full PRP loop", "run this detached", "continue across context windows", use headless autonomous execution, resume a saved loop, or invokes /prp-loop. Use prp-issue for ordinary end-to-end delivery.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestrator skill: fully executable commands with concrete defaults and flags, a clearly sequenced multi-stage pipeline with explicit green/halt criteria and a bounded correction loop, and a self-contained body that needs no external reference files. The only weakness is a short legacy-comparison paragraph that adds tokens without operational value.

Suggestions

Trim or relocate the 'UX note' comparing the retired Ralph loop — e.g., a single parenthetical ('(replaces the retired interactive Ralph loop)') or a short 'Deprecated' note — since the two-sentence behavioral comparison adds tokens without helping execute this skill.

Move the flag defaults and --until/--validate semantics into a compact single list right after the run commands so all invocation surface area lives in one place, removing the duplicated explanation of what --until implement does.

DimensionReasoningScore

Conciseness

The ~47-line body is dense and operational (commands, defaults, flags, halt conditions), but the 'UX note' paragraph comparing the retired Ralph loop is legacy-history explanation that does not help execute the skill and could be trimmed. This sits between the 'lean, every token earns its place' (5) and 'mostly efficient' (3) anchors, noticeably above the midpoint.

4 / 5

Actionability

Two copy-paste-ready uv run commands cover the two common invocations (start with "$ARGUMENTS", --resume), plus an --until example, concrete defaults (--max-cycles 3, --max-implement-iterations 10), and the authoritative --validate "<cmd>" contract (exit 0 = pass).

5 / 5

Workflow Clarity

The five stages are clearly sequenced with explicit validation checkpoints (VALIDATION: GREEN sentinel, --validate exit 0), a bounded review→fix→re-review feedback loop, and enumerated halt conditions (iteration limits, dirty review after max-cycles, no-progress fix, failed push, stage error) — validation is present, so the batch/destructive cap does not apply.

5 / 5

Progressive Disclosure

The body is under 50 lines, self-contained, and organized into clean sections (Run it, What it does, Safety, Notes); the single referenced path, scripts/prp_loop.py, exists in the bundle. No external references are needed for a skill this size.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person voice, concrete and comprehensive about what the pipeline does, explicit trigger phrases including the slash-command form, and an explicit disambiguation boundary against the sibling prp-issue skill. It clearly matches the rubric's good-overall examples.

DimensionReasoningScore

Specificity

The description enumerates the full pipeline cycle ('cycling plan, implementation, PR, review, and corrections') along with concrete operational specifics ('detached, resumable', 'fresh headless CLI sessions', 'persisted state and safety bounds'), giving comprehensive coverage of concrete actions.

5 / 5

Completeness

The first sentence explicitly answers 'what' (runs the detached, resumable PRP pipeline with its stage cycle) and the second sentence explicitly answers 'when' with concrete trigger phrases ('Use only when the user explicitly asks to...'), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Six natural trigger phrases users would actually say — 'run the full PRP loop', 'run this detached', 'continue across context windows', 'headless autonomous execution', 'resume a saved loop', and the /prp-loop invocation — cover the synonymous ways this skill gets requested.

5 / 5

Distinctiveness Conflict Risk

The 'Use only when the user explicitly asks' guard plus the explicit redirect 'Use prp-issue for ordinary end-to-end delivery' carves out a clear niche and actively steers overlapping requests to the correct sibling skill.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Wirasm/prp
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.