CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plan-review

This skill should be used when having multiple specialized agents review a plan in parallel.

55

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/03-plan/plan-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 maximally lean and its single dispatch action is concrete and unambiguous, naming the exact agents to invoke. Its weakness is incompleteness rather than verbosity: it never says what the reviewers should examine or how their parallel feedback should be synthesized into an answer.

Suggestions

Add a brief step for synthesizing results, e.g. 'After all reviews complete, combine findings into a single list of issues sorted by severity.'

Give each reviewer agent a one-line focus (e.g. what the Rails reviewers vs. the simplicity reviewer should look for) so the dispatch is fully specified.

Clarify what 'this plan' refers to (the plan currently under discussion) and what output format the user should receive.

DimensionReasoningScore

Conciseness

The body is two lines with zero padding and no explanation of concepts Claude already knows; every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

The instruction is concrete (three named agents, in parallel, targeting 'this plan'), but key details are missing — no guidance on what each reviewer should focus on or how to combine their outputs — matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The single dispatch action is unambiguous and the simple-skill exception applies, but the post-review step (aggregating three agents' feedback into a result) is an unspecified gap, placing it just below anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, no bundle files exist, and no external references are needed; the minimal structure (heading plus one instruction) is appropriate for a skill of this size, so the simple-skill guideline permits a 5.

5 / 5

Total

17

/

20

Passed

Description

45%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 identifies a real niche (parallel specialized-agent plan review) with a usable trigger clause, but it is thin: the action is generic, the 'what' is only implied inside the 'when' phrasing, and natural trigger variations are missing. It reads closer to a bare trigger sentence than a complete capability description.

Suggestions

State the 'what' explicitly and separately from the trigger, e.g. 'Dispatches multiple specialized reviewer agents to critique a plan in parallel and synthesizes their feedback.'

Add natural trigger phrases and synonyms users would actually say, such as 'review my plan', 'critique this design', or 'get feedback on this plan'.

Name or characterize the reviewer specializations (e.g. Rails-style review, code simplicity) so the skill is distinguishable from generic review skills.

DimensionReasoningScore

Specificity

The description names the domain ('multiple specialized agents review a plan') but the only action is the generic 'review' — no concrete review actions or scope are listed, matching 'names the domain but actions are minimal or generic'.

2 / 5

Completeness

A 'when' clause is present ('should be used when having... review a plan in parallel'), but the 'what' is only implied inside that clause with no separate statement of what the skill actually does; it is not the explicit both-what-and-when of anchor 4.

3 / 5

Trigger Term Quality

It contains some relevant natural keywords ('review', 'plan') but misses common variations and synonyms users would say ('critique', 'feedback', 'evaluate', 'assess this plan'), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The niche of parallel specialized-agent plan review is somewhat specific, but 'review a plan' could still overlap with generic review or code-review skills since the specialized reviewers are not characterized in the description.

3 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

marchatton/agent-skills

Path

.agents/skills/03-plan/plan-review/SKILL.md

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.