CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-analogy

Generate analogy options to explain a concept. Invoke with /cw-analogy or /cw-analogy [concept to explain].

Quality

71%

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 ./skills/cw-analogy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, lean, instruction-only skill that gives concrete generative steps, specified domains, test criteria, and a copy-paste output template. It is strong across all dimensions, consistently scoring 4, with only minor gaps (no regenerate feedback loop, a placeholder Lessons section).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; guidance like "Familiar vehicle, unfamiliar cargo" and "Structural, not surface" is skill-specific rather than generic padding. A few steps ("Understand the concept") and the empty "Lessons" placeholder are slightly trimmable, keeping it at 4 rather than 5.

4 / 5

Actionability

It gives a concrete 5-step process, three specified analogy domains (physical/tangible, human relationships, common activities), explicit test criteria, and a copy-paste output template. As an instruction-only skill the guidance is actionable, but the actual analogy generation relies on Claude's judgment, leaving minor gaps versus fully copy-paste-ready code.

4 / 5

Workflow Clarity

The five steps are clearly sequenced and step 5 ("Test each analogy") acts as a validation checkpoint with explicit criteria. It stops short of 5 because there is no explicit regenerate-on-failure feedback loop after the test step.

4 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections (Purpose, Invocation, How to Generate, Output Format, Principles, What to Avoid) and is self-contained with no need for external references. The empty "Lessons" placeholder and being slightly over the 50-line simple-skill threshold keep it at 4 rather than 5.

4 / 5

Total

16

/

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 clearly states what the skill does and uses a natural trigger term ("analogy"), but it lacks an explicit "Use when..." clause and offers only one concrete action with limited keyword synonyms. It is solid but not comprehensive, landing at the midpoint across most dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to explain, simplify, or illustrate a concept with an analogy or metaphor."

Broaden trigger terms to include synonyms like "metaphor", "comparison", and "simplify" so the description surfaces for more natural phrasings.

Mention a second concrete action (e.g. refining or iterating on a chosen analogy) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Generate analogy options to explain a concept" names the domain and one concrete action, but coverage is not comprehensive (no mention of refining, comparing, or iterating). It fits anchor 3 (domain + 1-2 concrete actions) and falls short of 4 which expects several specific actions.

3 / 5

Completeness

The "what" is clear (generate analogy options), but "when" is only weakly implied via the invocation syntax "Invoke with /cw-analogy" rather than an explicit "Use when..." trigger clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"analogy", "concept", and "explain" are natural terms a user would say, but common synonyms such as "metaphor" or "comparison" are missing. This matches anchor 3 (some relevant keywords, missing variations) rather than 4 (good coverage with a few gaps).

3 / 5

Distinctiveness Conflict Risk

The analogy-generation niche is clear and distinct with the "analogy" trigger, with only minor overlap risk against generic explanation or simplification skills. It is mostly distinct but not at the minimal-conflict level of 5 due to thin trigger coverage.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

EveryInc/compound-writing

Path

skills/cw-analogy/SKILL.md

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.