directives

Pre-built custom directives for json-render — formatting, math, string manipulation, and i18n. Use when working with @json-render/directives, defining custom directives with defineDirective, or adding $format, $math, $concat, $count, $truncate, $pluralize, $join, or $t to specs.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 tight, highly actionable single-file reference with excellent code examples and zero fluff. Its main structural weakness is that the full per-directive API reference lives inline in SKILL.md instead of being split into a one-level-deep references/ file, which would keep SKILL.md as an overview.

Suggestions

Move the per-directive reference (### $format through ### $join, ~140 lines) into a references/api.md file, keeping Quick Start, Defining Custom Directives, Composition, and Wiring in SKILL.md with clearly signaled links.

Add a brief validation note for the directive-name conflict rule (e.g., what error or behavior occurs when a name collides with $state/$cond/etc.) to strengthen the workflow's error-recovery guidance.

In the Wiring section, mention how to verify directives are active (e.g., a minimal spec snippet whose output confirms a directive resolved) so users get a feedback checkpoint after wiring.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: the body is dense with API facts (fields tables, operation enums, defaults like "Division by zero returns 0") with no padding and no explanation of concepts Claude already knows. Every token earns its place.	5 / 5
Actionability	Fully executable: the TypeScript quick start, the defineDirective example, per-directive JSON spec snippets, and the renderer/provider wiring code are all copy-paste ready and cover the common cases (all four renderers, factory spreading).	5 / 5
Workflow Clarity	The wiring workflow (prompt generation → provider/createRenderer → adding factory directives) is clearly sequenced with concrete code for each step. It falls short of 5 because there are no validation or error-recovery checkpoints (e.g., what happens with a conflicting directive name), though no destructive operations make that a minor gap.	4 / 5
Progressive Disclosure	Sections are well organized (Quick Start, Defining Custom Directives, per-directive reference, Composition, Wiring, Key Exports), but ~140 lines of per-directive API reference with fields tables and examples are inlined in SKILL.md — the anchor-3 pattern of API reference that could live in a separate file. A "## Advanced features → See REFERENCE.md" split would fit the anchor-4/5 structure; it is not a 2 because structure and navigation within the file are good, and not a 4 because the bulk detail is inline rather than in a referenced file.	3 / 5
	Total	17 / 20 Passed

Description

92%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: it states concrete capabilities, includes an explicit "Use when..." clause with the exact API terms a user of this library would say, and occupies a distinct niche. The only weakness is thin natural-language synonym coverage (e.g., translate/localize) beyond the API identifiers.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "formatting, math, string manipulation, and i18n" — giving comprehensive coverage of the skill's actions, matching the anchor-5 breadth. It is not a 4 because the capability areas covered are complete rather than having minor gaps.	5 / 5
Completeness	Explicitly answers both what ("Pre-built custom directives for json-render — formatting, math, string manipulation, and i18n") and when ("Use when working with @json-render/directives, defining custom directives with defineDirective, or adding $format... to specs") with concrete trigger phrases. Uses third-person/declarative voice throughout.	5 / 5
Trigger Term Quality	Good keyword coverage with precise API identifiers users would literally type: "defineDirective", "$format, $math, $concat, $count, $truncate, $pluralize, $join, or $t", "@json-render/directives". It falls short of 5 because natural-language synonyms like "translate", "locale-aware", or "pluralize text" are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (json-render directive catalog) with highly distinct triggers — $-prefixed directive keys and defineDirective — that would not naturally invoke any other skill. Minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: vercel-labs/json-render
Path: skills/directives/SKILL.md
Commit: c2600d7

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.