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.

The content is concise, well-structured, and provides a concrete decision enum plus a required-checks checklist appropriate for a simple instruction-only review gate. Its main weakness is that the checks are not explicitly mapped to the output decisions.

DimensionReasoningScore

Conciseness

The body is lean and efficient with zero padding or concept explanations; Inputs, the four-value Output enum, and the Required Checks each earn their place and assume Claude's competence.

5 / 5

Actionability

Concrete guidance is present via the explicit decision enum and a specific required-checks checklist, but the criteria for judging each check remain high-level, leaving minor gaps in fully executable instruction.

4 / 5

Workflow Clarity

Inputs -> Output -> Required Checks is a clear sequence, and the Required Checks list functions as a validation checklist for this single-purpose review gate; the minor gap is the absence of an explicit pass/fail decision flow tying checks to the output enum.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, the content is cleanly organized into well-labeled sections (Inputs, Output, Required Checks), satisfying the simple-skill exception for progressive disclosure.

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.

The description is specific and distinct with a clear 'what', but it lacks an explicit 'Use when...' trigger clause, which caps its completeness and weakens its trigger-term quality. Adding a concrete trigger phrase would lift the two lowest dimensions.

Suggestions

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

Add natural phrasings users would actually say, such as 'plan readiness', 'review a plan', or 'is this task packet ready', to improve trigger-term quality.

Optionally name 1-2 more concrete review actions (e.g. 'verify acceptance criteria, surface unresolved risks') to push specificity toward a 4.

DimensionReasoningScore

Specificity

Names the domain ('planner task packets') and one concrete action ('Review ... for readiness') plus a constraint ('without rewriting authoritative task state'), but does not list several specific actions, so it sits at the 1-2 concrete actions anchor rather than comprehensive coverage.

3 / 5

Completeness

It clearly states the 'what' but provides no explicit 'Use when...' trigger, and the rubric caps completeness at 3 when such explicit trigger guidance is absent.

3 / 5

Trigger Term Quality

Relevant keywords exist ('planner', 'task packets', 'readiness', 'review') but common natural phrasings a user would say (e.g. 'is this plan ready', 'check my plan') are missing, so it lands at 'some relevant keywords but missing variations'.

3 / 5

Distinctiveness Conflict Risk

The 'planner task packets for readiness ... without rewriting authoritative task state' framing carves a fairly distinct niche with only minor overlap risk against generic review/planning skills.

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.

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.