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

96%

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

92%

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

The body is concise, highly actionable, and clearly sequenced for a non-destructive reference skill. Its main weakness is progressive disclosure: the entire directive API reference lives inline in SKILL.md with no separate reference files or signaled deeper material.

Suggestions

Move the per-directive 'Built-in Directives' reference (examples + field tables) into a references/REFERENCE.md and keep SKILL.md as a Quick Start overview with a signaled link, lifting progressive_disclosure toward the one-level-deep anchor.

Optionally extract the i18n factory configuration detail into a references/I18N.md linked from the createI18nDirective section, since it is the most configuration-heavy topic.

Add a short 'Validation' note (e.g., confirm a directive name does not collide with built-in keys before registering) to make the custom-directive workflow's implicit checkpoint explicit, if you want workflow_clarity to be unambiguously a 3.

Dimension	Reasoning	Score
Conciseness	The body is lean reference material — code/JSON examples plus compact 'Fields:' lines and an exports table — with no preamble explaining what directives or Intl formatters are, matching the 'lean and efficient; every token earns its place' anchor rather than the 'some unnecessary explanation' score-2 anchor.	3 / 3
Actionability	Provides copy-paste-ready TypeScript imports, a full defineDirective example with a zod schema, JSON spec examples for every directive, and concrete React provider/createRenderer wiring, matching the 'fully executable code; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The Quick Start and Wiring sections give an unambiguous linear sequence (import → wire into prompt → wire into renderer) and there are no destructive or batch operations requiring validation checkpoints, so the simple-skill carve-out applies; it is not the score-2 'sequence present but checkpoints missing' case because none are needed.	3 / 3
Progressive Disclosure	Sections are well organized, but the full 8-directive API reference is inlined in SKILL.md with no signaled one-level-deep references and no bundle files to split into, matching the 'content that should be separate is inline' anchor rather than the 'appropriately split; one-level-deep references' anchor at 3; it is above the monolithic/nested-reference score-1 anchor.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete, clearly answering both what the skill does and when to use it with a distinct, low-conflict niche. Voice is third person with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities — 'formatting, math, string manipulation, and i18n' plus 'defining custom directives with defineDirective' and adding specific directives to specs — matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 anchor.	3 / 3
Completeness	Explicitly states what it does ('Pre-built custom directives for json-render — formatting, math, string manipulation, and i18n') and when to use it ('Use when working with...'), matching the 'clearly answers both what AND when' anchor and not the score-2 'when only implied' anchor.	3 / 3
Trigger Term Quality	Enumerates the natural terms a user of this library would say — the package name '@json-render/directives', 'defineDirective', and every directive token ($format, $math, $concat, $count, $truncate, $pluralize, $join, $t) — giving strong coverage rather than the 'some relevant keywords but missing variations' anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to the @json-render/directives package and specific directive tokens, forming a clear niche unlikely to fire for unrelated skills, rather than the 'somewhat specific but could overlap' anchor.	3 / 3
	Total	12 / 12 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: 9d3dfc8

Reviewed: about 12 hours 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.