CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

arktype

Arktype: runtime validation, discriminated unions with .merge()/.or(), spread keys. Use when mentioning arktype, type(), union types, command/event schemas.

Quality

85%

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

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.

A well-organized, highly actionable pattern catalog: executable code with good/bad contrasts, exact constraints and error messages, and explicit guidance on when to choose each pattern. The main deductions are minor — undefined placeholder identifiers in the flagship example, some rationale padding, and a long single-file body with one unverifiable external reference path.

Suggestions

Make the flagship example fully self-contained by defining or importing DeviceId and CommandId (e.g., a one-line `const DeviceId = type('string')`) so the code is copy-paste executable.

Trim the six-row 'Why this pattern' table and the 'Why derive from constants' bullets to the two or three highest-value points to reduce token overhead.

Move the anti-patterns or the type.enumerated material into a references/ file linked from SKILL.md, and replace or remove the '.agents/skills/typescript/SKILL.md' reference that is not part of this bundle.

DimensionReasoningScore

Conciseness

The body is dense and pattern-focused with minimal concept explanation Claude already knows (the one-line "TypeScript keeps value space and type space separate" aside), and most prose is arktype-specific mechanics like merge override/shallow semantics. It sits at anchor 4 rather than 5 because the six-row "Why this pattern" table and the "Why derive from constants" bullet list are rationale padding that could be trimmed, and it is above anchor 3 since there is no substantial unnecessary explanation.

4 / 5

Actionability

Nearly all guidance is executable TypeScript with good/bad contrast pairs, exact error messages ("ParseError: Spread operator may only be used as the first key"), and anti-pattern fixes. It misses anchor 5 only on minor gaps: the flagship example uses DeviceId/CommandId without importing or defining them, so the code is not copy-paste runnable as written; that fits anchor 4's "concrete code with minor gaps" better than anchor 3's pseudocode level.

4 / 5

Workflow Clarity

This is a pattern-selection reference rather than a multi-step workflow, and each pattern carries unambiguous use conditions ("Recommended" for base.merge(type.or(...)), "Good for 2-3 variants" for chaining, "For 4+ variants, prefer..."). It earns 4 rather than 5 because the simple-skill exception (single unambiguous action) only partly applies to a multi-pattern catalog, and there is no verification step such as checking that switch(cmd.action) narrows correctly; there is no destructive or batch operation that would cap the score.

4 / 5

Progressive Disclosure

With no bundle files present, everything is inline in a single SKILL.md, but it is well organized with clear section headers, consistent per-pattern structure, and a closing References section (including an arktype source link for the merge-distribution claim). This matches anchor 4's "good structure; most content is appropriately placed"; it does not reach anchor 5 because at ~350 lines some material (e.g., the anti-patterns or type.enumerated sections) could live in reference files, and the one non-URL reference path (".agents/skills/typescript/SKILL.md") is not a bundled, clearly signaled file.

4 / 5

Total

16

/

20

Passed

Description

87%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 names the specific library, its key capabilities with exact API syntax, and an explicit 'Use when' clause with concrete trigger terms. The only weakness is modest coverage: a few natural synonyms and a couple of the skill's actual topics (e.g., type.enumerated, inferred-type naming) are left out.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "runtime validation, discriminated unions with .merge()/.or(), spread keys" — naming specific API methods rather than generic language. It falls short of anchor 5 because coverage has gaps: major body topics like type.enumerated(), inferred-type naming, and optional-key syntax are absent; it is above anchor 3 because more than 1-2 specific capabilities are named with exact method syntax.

4 / 5

Completeness

Both parts are explicit: the what ("runtime validation, discriminated unions with .merge()/.or(), spread keys") and the when ("Use when mentioning arktype, type(), union types, command/event schemas") with concrete trigger phrases. This matches anchor 5, which requires both what and when with concrete triggers; it is clearly above anchor 4 where the when is only loosely specified.

5 / 5

Trigger Term Quality

"Use when mentioning arktype, type(), union types, command/event schemas" gives good keyword coverage anchored on the library name itself, which is the natural trigger a user would say. It is below anchor 5 because common synonyms like "schema validation", "runtime types", or "type safety" are missing, and above anchor 3 because the core natural terms (arktype, union types, command/event schemas) are all present.

4 / 5

Distinctiveness Conflict Risk

Arktype is a specific library and the description triggers on its name plus its distinctive APIs (".merge()/.or()", "type()"), giving it a clear niche with minimal overlap risk against generic validation or TypeScript skills. This matches anchor 5 (clear niche with distinct triggers) and is well above anchor 4's minor-overlap profile.

5 / 5

Total

18

/

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

EpicenterHQ/epicenter

Path

.agents/skills/arktype/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.