clear-cove-task-design

Use when orchestration or planning agents are producing task plans, task prompts, or TASK.md instructions that must be unambiguous, verifiable, and resistant to hallucination. Applies CLEAR (Concise, Logical, Explicit, Adaptive, Reflective) to structure and write agent task files, then adds CoVe (Chain of Verification) checks where accuracy risk is meaningful. Activates on draft task prompts, swarm plans, migration tasks, and multi-step plans requiring independently executable steps.

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

This is a strong, highly actionable skill that provides a complete framework for writing agent task prompts with clear workflows, validation checkpoints, and a ready-to-use template. Its main weakness is length — the migration-specific section and detailed template could benefit from being split into referenced files for better progressive disclosure. Minor conciseness improvements could be made by removing some framing language and reducing redundancy between sections.

Suggestions

Extract the Migration and Data Conversion Tasks section into a separate MIGRATION.md file and reference it from the main skill with a one-line summary.

Remove or compress the 'Success Criteria' section at the end, as it largely restates what the CLEAR guidelines and template already encode.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and well-structured, but contains some redundancy (e.g., success criteria at the end largely restates what CLEAR+CoVe already cover) and explanatory framing that Claude doesn't need (e.g., 'Treat every task file as an LLM prompt with operational consequences'). The migration section is thorough but adds significant length; some of the inline lint-failure message templates could be trimmed.	2 / 3
Actionability	The skill provides a complete, copy-paste-ready task prompt template in markdown, concrete linting rules, specific verification commands (e.g., grep examples, assert statements, script paths), and a clear output protocol. The CLEAR acronym is operationalized with specific do/don't guidance rather than abstract descriptions.	3 / 3
Workflow Clarity	The workflow is clearly sequenced: CLEAR first to structure, then CoVe where accuracy risk exists, then linting rules before finalizing. The CoVe section includes an explicit generate→verify→revise feedback loop. The 'Your Output Responsibilities' section provides a clear 4-step process with labeled change tracking. Migration tasks include an explicit deletion gate as a validation checkpoint.	3 / 3
Progressive Disclosure	The content is well-organized with clear headers and logical section progression, but it is monolithic — everything lives in a single file with no references to supporting documents. The migration section and the full template could reasonably be split into separate referenced files. For a skill of this length (~200+ lines), inline inclusion of all content reduces scannability.	2 / 3
	Total	10 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured description that clearly defines its niche in agent task planning and prompt writing with specific methodologies. Its main weakness is the heavy use of specialized terminology (CLEAR, CoVe, 'hallucination resistance') that users may not naturally use when requesting this skill, which could reduce discoverability. The explicit 'Use when' and 'Activates on' clauses are strong, providing clear trigger guidance.

Suggestions

Add more natural-language trigger terms that users might actually say, such as 'write agent instructions', 'create task steps', 'plan agent workflow', or 'break down tasks for agents' alongside the specialized terminology.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: structuring/writing agent task files using CLEAR methodology, adding CoVe checks, handling draft task prompts, swarm plans, migration tasks, and multi-step plans. These are concrete, well-defined actions.	3 / 3
Completeness	Clearly answers both 'what' (applies CLEAR framework to structure task files, adds CoVe verification checks) and 'when' (explicitly states 'Use when orchestration or planning agents are producing task plans...' and 'Activates on draft task prompts, swarm plans, migration tasks'). Has explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'task plans', 'task prompts', 'TASK.md', 'swarm plans', 'migration tasks', and 'multi-step plans'. However, it relies heavily on specialized jargon (CLEAR, CoVe, 'hallucination resistance') that users may not naturally use, and misses simpler trigger terms a user might say like 'write instructions', 'plan steps', or 'agent instructions'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: agent task prompt/plan writing with specific methodologies (CLEAR + CoVe). The combination of orchestration agents, TASK.md files, and verification checks creates a unique profile unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Jamie-BitFlight/claude_skills
Commit: 2f639b2

Reviewed: 3 days 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.