CtrlK
BlogDocsLog inGet started
Tessl Logo

plan-readiness-review

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

61

Quality

71%

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

85%

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

The content is admirably concise and well-structured for a simple review-gate skill, with a clear input/checklist/output shape. The one meaningful gap is actionability: it lists checks and possible decisions but does not connect them, leaving the reviewer without a concrete decision procedure.

Suggestions

Add a short decision rule mapping check outcomes to each verdict (e.g., 'A named risk or non-observable acceptance criterion yields needs_revision; a missing scope yields needs_clarification; an unfixable blocker yields blocked').

Include one or two brief examples showing a packet, the failing checks, and the resulting decision to make the guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and purposeful across terse Inputs, Output, and Required Checks sections with no re-explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

It provides a concrete check list and a fixed decision set, but never maps which check failures produce which decision (approve/needs_revision/needs_clarification/blocked), and gives no examples, leaving the guidance incomplete.

2 / 3

Workflow Clarity

As a simple single-purpose skill under 50 lines, its well-organized Inputs -> Required Checks -> Output structure makes the single action unambiguous; no destructive or batch operation requires a feedback loop.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized sections satisfy progressive disclosure for a simple skill; no bundle files exist or are required.

3 / 3

Total

11

/

12

Passed

Description

57%

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 specific to a clear niche and states a concrete action with a notable constraint, giving it low conflict risk. Its main weakness is the absence of an explicit 'Use when ...' trigger clause, which caps completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit 'Use when ...' clause naming the natural situations users would describe (e.g., 'Use when a planner task packet needs an independent readiness gate before execution, or when replanning after a failed round').

Expand trigger-term coverage with user-natural variants such as 'planner review', 'task readiness', 'plan quality gate', and 'replanning'.

DimensionReasoningScore

Specificity

Names a concrete domain ('planner task packets') and a specific action ('Review ... for readiness') plus a constraint ('without rewriting authoritative task state'), but lists only one action rather than multiple specific actions.

2 / 3

Completeness

Clearly states what the skill does, but provides no explicit 'when to use it' trigger clause; the judging guideline caps completeness at 2 when trigger guidance is missing.

2 / 3

Trigger Term Quality

Contains relevant domain keywords ('planner', 'task packets', 'readiness', 'review') but offers no natural 'Use when ...' trigger phrasing or common term variations a user would naturally say.

2 / 3

Distinctiveness Conflict Risk

Occupies a narrow, specific niche (plan readiness review) with a distinguishing constraint ('without rewriting authoritative task state') that makes triggering for the wrong skill unlikely.

3 / 3

Total

9

/

12

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.

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