CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-error-messages

Use when writing, reviewing, or rewriting user-facing error messages, validation messages, form errors, empty/error states, auth errors, failure notifications, retry/support copy, CLI errors, or API errors humans will read. Helps make errors specific, actionable, non-blaming, accessible, and safe without leaking sensitive details.

99

1.08x
Quality

100%

Does it follow best practices?

Impact

99%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A lean, well-organized instruction skill: concrete templates and good/avoid copy pairs drive actionability, a Quick Start plus Final Check give a clear validated workflow, and detail is appropriately offloaded to two real, clearly-signaled reference files. No wasted tokens on concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is dense and information-driven (Do/Avoid tables, anatomy table, concrete copy blocks) with no padded prose explaining what error messages are or other concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides a concrete message-shape template, a 4-point identification checklist, good/avoid copy pairs, anatomy patterns, and copy-paste-ready example blocks for validation, security, CLI, and generic-fallback cases — fully actionable for an instruction skill.

3 / 3

Workflow Clarity

Quick Start sequences identify-audience/failure/cause/recovery then write-to-shape, and the Final Check section supplies an explicit 6-question verification checklist before shipping; this is not a destructive/batch operation so no cap applies.

3 / 3

Progressive Disclosure

The References section signals two one-level-deep files with clear, condition-based navigation ("Open ... when auditing many messages", "Open ... when rewriting multiple messages"), and both referenced files exist in ./references/.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 precise, third-person description with an explicit 'Use when' trigger, broad natural keyword coverage, and a distinctive error-message niche. It cleanly answers both what the skill does and when to invoke it without verbosity or over-claims.

DimensionReasoningScore

Specificity

Lists many concrete action types ("writing, reviewing, or rewriting user-facing error messages, validation messages, form errors ... CLI errors, or API errors") and concrete qualities ("specific, actionable, non-blaming, accessible, and safe without leaking sensitive details"), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ("Helps make errors specific, actionable, non-blaming, accessible, and safe without leaking sensitive details") and when ("Use when writing, reviewing, or rewriting user-facing error messages ..."), with a present 'Use when' clause so completeness is not capped at 2.

3 / 3

Trigger Term Quality

Natural trigger terms a user would say ("error messages", "form errors", "auth errors", "CLI errors", "API errors", "validation messages", "retry/support copy") give good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The error-message-copy niche is clearly scoped across validation, form, auth, CLI, and API contexts, making it unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
joshuadavidthomas/agent-skills
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.