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.

75

Quality

93%

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

96%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.

The body is a tight, executable overview: it gives the run/resume commands, a clear five-stage workflow with explicit halt conditions and a bounded review->fix feedback loop, and delegates the orchestration logic to the bundled script. No padded explanations of concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence: no explanation of what a PR or plan is, just the command, stage sequence, defaults, and safety bounds — every token earns its place.

5 / 5

Actionability

Fully executable copy-paste commands for both start and resume flows, plus concrete flags (--until, --max-cycles, --validate) with their exact behavior and a real script path.

5 / 5

Workflow Clarity

The 'What it does' section sequences all five stages explicitly and the 'Safety' section lists validation checkpoints (green sentinel, --validate exit 0, halt conditions on failure/no-progress/limits), with the review->fix feedback loop clearly bounded by --max-cycles.

5 / 5

Progressive Disclosure

Well-organized into focused sections that delegate the heavy logic to the bundled scripts/prp_loop.py (a real referenced file) at one level deep; the state-file path is surfaced as the inspection/resume entry point, with only minor organization gaps.

4 / 5

Total

19

/

20

Passed

Description

91%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.

The description is third-person, dense with concrete capability language, and pairs a thorough 'Use only when...' trigger clause with a distinctiveness hint against prp-issue. It is slightly long but earns its tokens through explicit trigger guidance.

DimensionReasoningScore

Specificity

Names concrete pipeline actions ('cycling plan, implementation, PR, review, and corrections') with persisted state and safety bounds, but stops short of enumerating each stage's concrete actions comprehensively.

4 / 5

Completeness

Explicitly answers both what (runs the detached, resumable PRP pipeline cycling plan/implement/PR/review/corrections) and when (a clear 'Use only when the user explicitly asks...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural triggers including exact user phrases ('run the full PRP loop', 'run this detached', 'continue across context windows') plus the /prp-loop invocation and contrast with prp-issue.

5 / 5

Distinctiveness Conflict Risk

Distinct niche with explicit trigger phrases and a direct contrast ('Use prp-issue for ordinary end-to-end delivery'), with only minor overlap risk against the related prp-issue skill.

4 / 5

Total

18

/

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.

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