yaml

YAML wire format for json-render with streaming parser, prompt generation, and AI SDK transform. Use when working with @json-render/yaml, YAML-based spec streaming, yaml-spec/yaml-edit fences, or YAML prompt generation.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/yaml/SKILL.md

Quality

Content

65%

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 reference for the yaml package with strong executable code examples. It is held back by repetition of the fence-type taxonomy across sections and by being a monolithic single file with no progressive disclosure to deeper reference materials.

Suggestions

Consolidate the four fence types into a single authoritative section and reference it from the others to remove the repeated yaml-spec/yaml-edit/yaml-patch/diff listings.

Split the low-level streaming parser and full Key Exports reference into a separate REFERENCE.md (one level deep) so SKILL.md stays a concise overview.

Add a short guided workflow (e.g., pick mode -> generate prompt -> pipe transform -> verify patches) so the feature catalog reads as a sequenced process rather than isolated sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference material, but the four fence types are restated across four places (Key Concepts, AI SDK Transform, Fence Constants, Key Exports) and the exports table reiterates detail already given, matching the 'mostly efficient but could be tightened' anchor rather than the every-token-earns-its-place top anchor.	2 / 3
Actionability	Provides multiple concrete, copy-paste-ready TypeScript examples with real imports and option objects (yamlPrompt, pipeYamlRender, createYamlStreamCompiler push/flush/reset, fence constants), matching the 'fully executable code; specific examples; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Sequences are present (the compiler lifecycle of push, flush, reset is clearly ordered) but the document is a feature catalog rather than a guided multi-step workflow and includes no validation checkpoints or feedback loops, matching the 'steps listed but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	Sections are well organized but the skill is a single ~140-line monolithic file with no bundle files and no one-level-deep references, and API-reference-level detail (low-level streaming parser, full export table) is inline rather than split into separate files, matching the middle anchor.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 tightly scoped, third-person description that clearly states both capability and explicit usage triggers for a niche library. It is slightly held back by feature-name phrasing and package-specific jargon rather than natural user vocabulary.

Dimension	Reasoning	Score
Specificity	Quotes name concrete capabilities ("streaming parser", "prompt generation", "AI SDK transform", "YAML wire format") but these are named features rather than a list of specific user-facing actions, matching the 'names domain and some actions, but not comprehensive' anchor; not a 3 because it lacks the multi-action concreteness of 'extract text, fill forms, merge documents'.	2 / 3
Completeness	Explicitly answers both what ("YAML wire format for json-render with streaming parser, prompt generation, and AI SDK transform") and when ("Use when working with @json-render/yaml, YAML-based spec streaming, yaml-spec/yaml-edit fences, or YAML prompt generation") via an explicit 'Use when' clause, matching the top anchor.	3 / 3
Trigger Term Quality	Includes relevant triggers ("@json-render/yaml", "YAML prompt generation") but leans on package-specific jargon ("yaml-spec/yaml-edit fences", "YAML-based spec streaming") that users would not naturally say, matching the 'some relevant keywords but missing common variations' anchor rather than broad natural coverage.	2 / 3
Distinctiveness Conflict Risk	The niche is tightly scoped to the @json-render/yaml package and specific fence types, giving a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the top anchor.	3 / 3
	Total	10 / 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/yaml/SKILL.md
Commit: 9d3dfc8

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