CtrlK
BlogDocsLog inGet started
Tessl Logo

plan-readiness-review

Review planner task packets for readiness without rewriting authoritative task state.

60

Quality

70%

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 ./docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_plan_reviewer/skills/plan-readiness-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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, token-efficient instruction-only skill: it defines explicit inputs, a closed decision vocabulary, and a concrete checklist of required checks with no padding. Its main gaps are the unspecified output format and the implicit mapping from failed checks to the four decisions.

Suggestions

Specify the structure of the returned review (e.g. which decision was chosen, which checks passed/failed, and evidence for each failure).

Add brief decision criteria mapping check failures to each of the four outcomes so the choice between needs_revision, needs_clarification, and blocked is deterministic.

State the operating sequence explicitly (apply each required check to the packet, then select the single decision) to remove the reliance on section order.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and efficient: 'Use this skill when a planner artifact needs an independent quality gate before execution or clarification.' plus tightly-scoped Inputs, Output, and Required Checks sections. Every token earns its place with no explanation of concepts Claude already knows.

5 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: an explicit input list, a closed decision enum ('approve', 'needs_revision', 'needs_clarification', 'blocked'), and six specific check items ('no hidden fallback or degradation is accepted'). It stays below 5 because the output format beyond the decision value and how each check maps to a decision are left implicit.

4 / 5

Workflow Clarity

The flow is coherent and unambiguous for a simple single-task skill — consume the listed inputs, apply the required checks, return exactly one decision — and the checks act as a checklist. It is not 5 because the sequence is implied by section order (Inputs → Output → Checks) rather than stated as an explicit step sequence with decision criteria per check.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into clearly labeled sections (Inputs, Output, Required Checks) — per the simple-skill guidance this matches the top anchor.

5 / 5

Total

18

/

20

Passed

Description

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

A terse, third-person description with a distinct niche and a clear 'what', but it omits any 'when to use' trigger phrasing and offers only a single action, so it reads more like a role definition than an invocable capability. Adding an explicit 'Use when...' clause with natural trigger terms would lift both completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a planner task packet needs an independent readiness check before execution or clarification.'

Include natural trigger synonyms users would actually say, such as 'plan review', 'is the plan ready', or 'task packet check'.

Optionally enumerate the review actions (check scope, acceptance criteria, verification, risks) to strengthen specificity.

DimensionReasoningScore

Specificity

The description names its domain ('planner task packets') and one concrete action ('Review ... for readiness'), but unlike the score-4/5 anchors it does not list several specific actions — the supplementary clause 'without rewriting authoritative task state' is a constraint, not a capability.

3 / 5

Completeness

It has a clear 'what' (review task packets for readiness) but no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3; it is not score 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

Terms like 'planner', 'task packets', and 'readiness' are relevant keywords a user in this workflow might say, but there are no natural variations or synonyms ('review the plan', 'is the plan ready', 'plan quality gate'), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Planner task packets', 'readiness', and 'authoritative task state' carve a clear niche that would rarely fire the wrong skill; only minor overlap risk with generic code/document review skills keeps it below 5.

4 / 5

Total

13

/

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
SeemSeam/claude_codex_bridge
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.