vue

Vue 3 renderer for json-render. Use when building Vue UIs from JSON specs, working with @json-render/vue, defining Vue component registries, or rendering AI-generated specs in Vue.

Quality

86%

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 concise, highly actionable reference body with executable code throughout and a clear setup sequence. Its main weakness is progressive disclosure: all API surface is inlined in SKILL.md with no external reference files to offload detail.

Suggestions

Move the Providers, Composables, and Key Exports tables into a single reference file (e.g. references/API.md) and keep SKILL.md as a Quick Start overview that links to it, improving progressive disclosure.

Replace the `{ /* ... */ }` placeholder in the render example with a minimal complete spec so the full flow is copy-paste runnable end to end.

Add a brief validation note (e.g. confirming the registry renders without console errors or that catalog/registry component names match) to give the setup sequence an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean and dense: mostly code and tables with minimal prose, assuming Vue competence (no explanation of what Vue or a renderer is); every section earns its place.	5 / 5
Actionability	Fully executable copy-paste-ready code for defineCatalog, defineRegistry, and the StateProvider/ActionProvider/Renderer render setup, covering the common end-to-end cases.	5 / 5
Workflow Clarity	The Quick Start sequences Catalog -> Registry -> Render clearly and the operation is non-destructive, so no validation cap applies, but there are no explicit verification checkpoints.	4 / 5
Progressive Disclosure	Well-organized section headers, but at ~200 lines with no bundle files the bulk API/composable/export tables are inlined in a single file rather than split into one-level-deep reference files; the under-50-line exception does not apply.	3 / 5
	Total	17 / 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, well-targeted description that concisely answers both what the skill does and when to use it with concrete trigger phrases. Minor room for more synonym/extension coverage but otherwise low conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain ("Vue 3 renderer for json-render") and lists several concrete actions via the trigger clause (building Vue UIs from JSON specs, defining component registries, rendering AI-generated specs), with only minor coverage gaps.	4 / 5
Completeness	Explicitly states the what ("Vue 3 renderer for json-render") and an explicit "Use when..." clause with concrete trigger phrases, matching the anchor for both what and when.	5 / 5
Trigger Term Quality	Good natural-term coverage ("Vue UIs", "JSON specs", "@json-render/vue", "component registries", "AI-generated specs") that a user would plausibly say; a few synonyms are absent so it falls short of anchor 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Vue 3 + json-render) with distinct, library-specific triggers makes misfires unlikely and minimal conflict with other skills.	5 / 5
	Total	18 / 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/vue/SKILL.md
Commit: ea33260

Reviewed: 7 days 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.