CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-worktree

Git-native worktree management via a bundled single-file CLI - create, list (with per-worktree git stats), and safely tear down isolated checkouts under .worktrees/ for parallel workstreams. Use when the user or an orchestrating skill wants to "create a worktree", "work on this in a separate worktree", "spin up an isolated checkout", "list my worktrees", "clean up / remove a worktree", or invokes /prp-worktree.

79

Quality

100%

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

100%Weight 40%Scale 1-3

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

An efficient, action-first body that wraps a bundled CLI with executable commands, explicit safety rails on the destructive operation, and clean delegation of detail to the script's own --help. It is well within token budget and leaves nothing essential implicit.

DimensionReasoningScore

Conciseness

The ~37-line body is lean and assumes Claude knows git/worktree basics (it never explains what a worktree is), with each section — Run it, Conventions, Gotchas, Resources — earning its place; the only rhetorical flourish ("instead of improvised git worktree incantations") is purposeful, not padding.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands — "uv run ${CLAUDE_PLUGIN_ROOT}/skills/prp-worktree/scripts/worktree.py create <name> [--base <branch>]" — with concrete flags and per-subcommand behavior, matching the executable-and-specific anchor rather than pseudocode.

3 / 3

Workflow Clarity

Per the simple-skills note the single action (run the CLI) is unambiguous, and the destructive remove path has an explicit validation gate — the script "refuses if the worktree has uncommitted changes" plus "Never force without first investigating what would be lost" — so validation is present, not missing, avoiding the cap at 2.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized sections and a single one-level-deep reference to scripts/worktree.py (verified present), delegating flag detail to "--help on any subcommand" rather than duplicating it inline, matching the clear-overview / well-signaled-reference anchor.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A tight, well-constructed description that states concrete capabilities and pairs them with explicit, natural-language trigger phrases and the slash-command invocation. It cleanly satisfies all four dimensions with no verbosity or first/second-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "create, list (with per-worktree git stats), and safely tear down isolated checkouts under .worktrees" — which matches the score-3 anchor for several specific actions rather than a vague domain mention.

3 / 3

Completeness

Explicitly answers both what (create/list/teardown of isolated checkouts) and when ("Use when the user or an orchestrating skill wants to..." with concrete triggers plus the /prp-worktree invocation), matching the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Natural phrasings a user or orchestrator would actually say are quoted verbatim — "create a worktree", "work on this in a separate worktree", "spin up an isolated checkout", "list my worktrees", "clean up / remove a worktree" — giving good coverage; voice is third-person ("Use when the user..."), so no I/you penalty applies.

3 / 3

Distinctiveness Conflict Risk

"Git-native worktree management" is a clear niche with worktree-specific triggers unlikely to fire for unrelated skills, matching the clear-niche/distinct-triggers anchor rather than a generic overlap-prone description.

3 / 3

Total

12

/

12

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.