Name: clarity
Rating: 81.5 (1 reviews)
Author: majiayu000

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

73%

Does it follow best practices?

Impact

85%

1.26x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/1-clarity-ioku24-autorankr/SKILL.md

The canonical home for this skill is clarity in majiayu000/claude-skill-registry

Quality

Content

67%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.

A well-structured, actionable protocol skill with clear sequenced workflows and concrete templates. Its primary weakness is moderate redundancy across the two parallel clarity protocols and repeated section headers, which inflates the token budget without adding guidance value.

Suggestions

Collapse the Messy Input Protocol and Full Clarity Protocol into a single section that branches by clarity level, removing the repeated 'Ask and document:' headers under WHAT/WHY/HOW.

Trim the example dialog to the minimum needed to show the WHAT/WHY/SCOPE extraction and confirm step.

Consider moving the full active-context.md output template into a reference file and signaling it here, to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and does not explain concepts Claude already knows, but carries noticeable redundancy: two parallel protocols (Messy Input vs Full Clarity), repeated 'Ask and document:' headers under each WHAT/WHY/HOW step, and a fairly long example dialog that could be trimmed.	3 / 5
Actionability	Provides concrete, executable guidance — a WHAT/WHY/SCOPE extraction template, tiered Efficiency Rules, a complete active-context.md output template, and a worked example dialog — with only minor gaps (placeholder brackets and slightly abstract prompts like 'Ask 1-2 specific questions').	4 / 5
Workflow Clarity	Clear multi-step sequences in both protocols with an explicit confirm checkpoint ('Confirm briefly: Is that right?') and tiered clarity rules; not a 5 because there is no explicit validate-fix-retry feedback loop, though the skill is not destructive/batch so the cap-3 rule does not apply.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Messy Input Protocol, Full Clarity Protocol, Output Requirements, Rules, Transition) with no buried or nested references; falls short of 5 only because the bulky active-context.md template is inlined and no reference files are signaled.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A strong description that clearly states both what the skill does and when to trigger it using natural, user-facing language. Its main weakness is that the stated actions are behavioral rather than concrete technical operations, which limits specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('clarity') and a couple of concrete actions ('Establish clarity', 'Handles messy voice input efficiently', extract core intent), but the actions are behavioral/abstract rather than the multiple concrete technical actions a 4 or 5 would list.	3 / 5
Completeness	Explicitly answers both 'what' ('Establish clarity before starting work', 'Handles messy voice input efficiently') and 'when' ('Use when beginning any significant task, when input is vague or stream-of-consciousness, or when requirements seem unclear') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes several natural trigger phrases a user would actually encounter ('input is vague', 'stream-of-consciousness', 'requirements seem unclear', 'significant task'), with only minor synonym gaps; not a 5 because it lacks the comprehensive synonym/extension coverage of the top anchor.	4 / 5
Distinctiveness Conflict Risk	Has a clear named niche ('clarity', 'first system in the 5-system framework') with distinct triggers, but 'beginning any significant task' is broad enough to risk overlap with general planning/startup skills, keeping it short of 5.	4 / 5
	Total	16 / 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: majiayu000/claude-skill-registry-data
Path: data/1-clarity-ioku24-autorankr/SKILL.md
Commit: a1e9f44

Reviewed: about 19 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.