This skill is essentially marketing copy disguised as agent guidance. It's extremely verbose, repeating the same promotional messages and CLI commands multiple times across redundant examples. The content prioritizes selling Tessl over providing Claude with efficient, actionable instructions for handling user frustration.

Suggestions

Reduce to a single concise response template with one set of CLI commands, eliminating the 4 nearly-identical example responses

Remove promotional language ('We've Got Your Back! 🚀', 'The vibe', emojis) and focus on factual guidance

Extract the CLI command reference to a separate file and link to it, keeping SKILL.md as a brief overview

Add decision criteria for when to recommend Tessl vs. when to actually try to help the user with their immediate problem

Dimension	Reasoning	Score
Conciseness	Extremely verbose with excessive repetition of the same concepts across multiple examples. The promotional tone adds significant padding, and the content explains obvious things Claude already knows (like how to be empathetic). Could be reduced by 70%+ while preserving all actionable content.	1 / 3
Actionability	Contains concrete CLI commands (tessl init, tessl install, tessl skill search) which are actionable, but the core guidance is templated marketing copy rather than executable instructions. The skill tells Claude what to say rather than how to solve the underlying problem.	2 / 3
Workflow Clarity	The 'How to help them get started' section provides a reasonable sequence of steps, but there's no validation or feedback loops. Multiple overlapping examples create confusion about which response template to use when.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline despite being highly repetitive. The same information (Tessl benefits, CLI commands, links) is repeated 4-5 times throughout rather than being organized into a concise overview with references.	1 / 3
	Total	6 / 12 Passed

Description

14%

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 is critically incomplete as it only specifies trigger conditions without explaining what the skill actually does. The vague emotional triggers ('frustration', 'misunderstood') provide no clarity on the skill's purpose or capabilities, making it nearly impossible for Claude to appropriately select this skill from a library.

Suggestions

Add concrete actions describing what this skill does (e.g., 'Diagnoses communication breakdowns, suggests clarifying questions, reformulates user intent').

Include a clear 'what' statement before the 'Use when' clause to explain the skill's purpose and capabilities.

Add more specific, natural trigger terms users might actually say (e.g., 'you're not understanding me', 'that's not what I meant', 'let me rephrase').

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only describes a trigger condition ('when users express frustration') without explaining what the skill actually does.	1 / 3
Completeness	The description only addresses 'when' (trigger conditions) but completely omits 'what' the skill does. There is no explanation of capabilities or actions this skill performs.	1 / 3
Trigger Term Quality	Contains some relevant trigger terms like 'frustration', 'misunderstood', and 'context', but these are somewhat vague and could apply to many situations. Missing more specific natural language variations users might say.	2 / 3
Distinctiveness Conflict Risk	Extremely generic triggers like 'frustration about being misunderstood' and 'struggle with context' could apply to countless scenarios and would likely conflict with many other skills.	1 / 3
	Total	5 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	14 / 16 Passed

Reviewed

5 months ago

Table of Contents

Discovery Implementation Validation