clarity

Establish clarity before starting work. Use when beginning any significant task, when input is vague or stream-of-consciousness, or when requirements seem unclear. Handles messy voice input efficiently. This is the first system in the 5-system framework.

1.26x

Quality

58%

Does it follow best practices?

Impact

85%

1.26x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/1-clarity/SKILL.md

Quality

Discovery

40%

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 description identifies when to use the skill reasonably well but fails to explain what concrete actions it performs. The phrase 'Establish clarity' is abstract and doesn't help Claude understand the specific capabilities. The reference to a '5-system framework' suggests organizational context but doesn't aid skill selection.

Suggestions

Replace 'Establish clarity' with specific actions like 'Asks targeted clarifying questions, summarizes user intent, and creates structured task briefs'

Add more natural trigger terms users might say: 'I'm not sure what I need', 'help me think through this', 'confused about requirements'

Clarify what 'Handles messy voice input efficiently' means in practice - does it parse transcripts, extract key points, or restructure rambling input?

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Establish clarity' and 'Handles messy voice input efficiently' without specifying concrete actions. It doesn't explain what the skill actually does - no verbs describing specific operations like 'asks clarifying questions', 'summarizes requirements', or 'creates structured briefs'.	1 / 3
Completeness	Has a 'Use when...' clause covering when to trigger (beginning tasks, vague input, unclear requirements), but the 'what' is weak - 'Establish clarity' doesn't explain the concrete actions taken. The mention of '5-system framework' adds context but doesn't clarify capabilities.	2 / 3
Trigger Term Quality	Contains some relevant terms like 'vague', 'stream-of-consciousness', 'voice input', and 'requirements unclear' that users might naturally express. However, it's missing common variations like 'confused', 'not sure what I want', 'rambling', or 'help me figure out'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'beginning any significant task' and 'vague input' provides some distinctiveness, but 'Establish clarity' is generic enough to potentially conflict with planning, requirements gathering, or general conversation skills. The '5-system framework' reference helps but isn't sufficient alone.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

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

This skill provides strong actionable guidance with clear workflows and good examples, particularly the Messy Input Protocol section which demonstrates efficient handling of unclear requests. However, it suffers from some verbosity in the Full Clarity Protocol section and could benefit from better progressive disclosure by moving detailed templates to separate reference files.

Suggestions

Move the detailed active-context.md template to a separate TEMPLATES.md file and reference it briefly

Condense the Full Clarity Protocol steps - the 'Ask and document' pattern is repetitive and could be a single bulleted list per step

Add links to the referenced systems (Identity, Priority, Execution, Reset) rather than just naming them

Dimension	Reasoning	Score
Conciseness	The skill has some efficient sections (like the Messy Input Protocol example) but includes unnecessary verbosity in the Full Clarity Protocol with repetitive 'Ask and document' patterns and overly detailed output templates that could be condensed.	2 / 3
Actionability	Provides concrete examples with exact formats, specific markdown templates for output, clear decision trees (clear request → skip, slightly unclear → one-line confirm), and copy-paste ready active-context.md structure.	3 / 3
Workflow Clarity	Clear sequential steps (Steps 1-4 for full protocol), explicit decision points for when to use messy input protocol vs skip it, and clear transition guidance to other systems. The efficiency rules provide good validation checkpoints.	3 / 3
Progressive Disclosure	Content is reasonably structured with sections, but the Full Clarity Protocol could be split into a separate reference file. References to other systems (Identity, Priority, Execution, Reset) are mentioned but not linked. The active-context.md template is inline when it could be a separate reference.	2 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: majiayu000/claude-skill-registry-data
Commit: 2bbaa03

Reviewed: 13 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.