planner-task-packet

Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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_planner/skills/planner-task-packet/SKILL.md

Quality

Content

88%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 an exceptionally concrete, executable specification with clear validation checkpoints and route-specific contracts. Its only weaknesses are minor restatement of the post-detail rules and a monolithic inline structure.

Dimension	Reasoning	Score
Conciseness	Dense and rule-driven with no concept padding, though the post-detail rules are restated a few times and could be tightened slightly.	4 / 5
Actionability	Provides exact fenced templates, exact readiness/route values, exact JSON field shapes, and executable verification commands, all copy-paste ready.	5 / 5
Workflow Clarity	Multi-route workflow with explicit fail-closed validation checkpoints and route-specific readiness shapes, plus feedback loops for the bounded post-detail exception.	5 / 5
Progressive Disclosure	Clean section structure with no nested references and no external bundle files needed, though the inline contract detail is somewhat monolithic for a ~210-line skill.	4 / 5
	Total	18 / 20 Passed

Description

56%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 but lacks any 'when to use' trigger guidance and relies on internal CCB terminology rather than natural user phrases. Its strongest dimension is specificity; its weakest is trigger term quality and completeness.

Suggestions

Add a 'Use when ...' clause stating the natural situations that activate this skill (e.g. converting a user request or frontdesk intake into a reviewable plan artifact).

Introduce user-facing trigger terms alongside the CCB jargon (e.g. 'plan', 'task packet', 'readiness check', 'clarification questions').

Reword in third-person action voice consistently and keep the concrete action list while trimming the niche acronyms for the trigger phrase.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions within a specific domain ('Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is clear but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Terms like 'CCB workflow', 'task packets', and 'readiness recommendations' are internal jargon rather than phrases a user would naturally say; natural trigger terms and synonyms are absent.	2 / 5
Distinctiveness Conflict Risk	A highly specific niche ('without mutating authoritative state') makes overlap unlikely, though the jargon could collide with sibling planning skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_planner/skills/planner-task-packet/SKILL.md
Commit: 01d5b1c

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.