CtrlK
BlogDocsLog inGet started
Tessl Logo

type-level-error-messages

Make TypeScript errors readable with template-literal constraint messages. Use when constraining literal object keys or string shapes and the error should point to the offending value.

62

Quality

73%

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 ./.agents/skills/type-level-error-messages/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tightly-written, executable skill that leads with a complete example, explains the non-obvious U+200B brand rationale, and follows through with runtime checks, pitfalls, and references. It is well-structured and actionable with only minor conciseness and workflow-framing improvements available.

DimensionReasoningScore

Conciseness

Mostly lean and assumes TS competence, with only minor over-explanation (e.g., the "wins on readability" recap after the comparison table) that could be trimmed.

4 / 5

Actionability

Provides concrete, near-copy-paste TypeScript (predicate, branded type, helper, runtime check) covering the common cases; the one-line `/* recursive template literal walk */` placeholder in the opening example is later filled in, leaving only minor gaps.

4 / 5

Workflow Clarity

The pattern is sequenced (predicate -> brand -> helper -> runtime check) with explicit pitfalls and a validate-at-runtime checkpoint; as a single-purpose skill it is nearly there, lacking only an explicit validate/retry feedback loop framing for the highest score.

4 / 5

Progressive Disclosure

Well-organized sections with a concise overview and a clearly-signaled one-level-deep Reference section; no bundle files exist, so all content appropriately lives inline.

5 / 5

Total

17

/

20

Passed

Description

67%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 focused, third-person description that conveys both purpose and an explicit use-when clause. It is specific and largely distinct, but the trigger terms skew technical and omit the more natural phrasings a user might actually say.

Suggestions

Add a natural-language trigger phrase (e.g., "Use when TypeScript errors are unreadable and should name the offending value") so users discover it via everyday wording.

Mention the common variations users say ("error message", "bad key", "validation at the type level") alongside the technical "template-literal constraint" framing.

Consider naming the runtime pairing briefly so the "what" covers the full pattern, not just the type-level half.

DimensionReasoningScore

Specificity

"Make TypeScript errors readable with template-literal constraint messages" names the domain and a concrete action (rendering constraint messages via template literals), with only minor coverage gaps (no mention of the predicate/runtime pairing).

4 / 5

Completeness

It states both what ("Make TypeScript errors readable with template-literal constraint messages") and when ("Use when constraining literal object keys or string shapes and the error should point to the offending value"), though the trigger clause is somewhat narrow.

4 / 5

Trigger Term Quality

"constraining literal object keys or string shapes" and "TypeScript errors" are relevant but lean technical; common user phrasings like "error message", "bad key", or file/type extensions are missing.

3 / 5

Distinctiveness Conflict Risk

The template-literal-error-message niche is specific and distinct from general TypeScript skills, with only minor overlap risk against broad TS linting/type-helper skills.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EpicenterHQ/epicenter
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.