CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-orchestrate

Turns the current session into the operator's SDLC proxy for parallel PRP workstreams in isolated worktrees. It owns the combined outcome, steers autonomous deliveries, holds human and merge gates, verifies proof, and sequences merges. Use when the user wants to "spawn N agents in separate worktrees", "run prp-issue on these issues in parallel", "orchestrate these features", "act as my orchestrator", "coordinate agents through the PRP pipeline", "ship these issues in parallel", or invokes /prp-orchestrate.

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 content is a dense, well-structured orchestration playbook with concrete commands, explicit per-engine routing, and validation gates throughout the batch/merge lifecycle. Mechanics are cleanly pushed to a verified one-level reference, keeping the overview navigable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what worktrees, PRs, or CI are, and every line carries directive load with no padded concept exposition.

5 / 5

Actionability

Gives concrete executable commands ('gh pr view <number> --json ...', 'gh pr diff <n> --name-only', 'git worktree list'), an executable PRP-store resolver block, and explicit per-engine skill routing covering the common cases.

5 / 5

Workflow Clarity

Seven sequenced phases (intake/gate, initialize, launch, monitor, hold gates, integrate, close out) carry explicit validation checkpoints — 'Do not launch before approval', re-verify current-head review and CI before each merge — with feedback loops for the destructive batch merge operations.

5 / 5

Progressive Disclosure

The SKILL.md is an overview that delegates provider mechanics, the workstream prompt, verification, capacity, and cleanup to a real, well-signaled one-level reference (references/launching.md, verified present), keeping the body focused on orchestration logic.

5 / 5

Total

20

/

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.

The description is third-person, concrete, and complete, naming multiple specific capabilities and a rich set of natural trigger phrases including the slash-command invocation. It clearly distinguishes the orchestrator role from the per-workstream PRP skills it composes.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'owns the combined outcome, steers autonomous deliveries, holds human and merge gates, verifies proof, and sequences merges' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (proxy that owns/steers/gates/verifies/sequences) and 'when' via a concrete 'Use when the user wants to...' clause with multiple trigger phrases and the /prp-orchestrate invocation.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases with synonyms — 'spawn N agents in separate worktrees', 'orchestrate these features', 'act as my orchestrator', 'coordinate agents through the PRP pipeline', 'ship these issues in parallel' — that users would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (parallel PRP workstreams in isolated worktrees) with distinct triggers, so it is unlikely to fire for the wrong 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.

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.