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

76%

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/vue/SKILL.md

Quality

Content

71%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-structured, mostly executable reference for the Vue renderer with a clear quick-start path. Main gaps are the inlined ~200-line API reference that belongs in a separate reference file, a redundant Key Exports table, and several under-exampled one-liner sections.

Suggestions

Move the Providers, Composables, and Key Exports tables into a references/ file (e.g., references/api.md) and keep only key examples inline, adding well-signaled links.

Remove or merge the Key Exports table with the Providers/Composables tables to eliminate duplicated token cost.

Add a short executable example each for the one-line sections (Streaming, Event System, Dynamic Prop Expressions) so every feature is actionable.

Dimension	Reasoning	Score
Conciseness	Lean, code-first prose with no explanations of known concepts, but the 'Key Exports' table largely duplicates the Providers and Composables tables, and pinned versions ('vue ^3.5.0', 'zod ^4.0.0') are time-sensitive information outside any deprecated section. Efficient overall — anchor 4, not 5.	4 / 5
Actionability	The catalog, registry, and SFC render examples are complete and copy-paste ready, but sections like Streaming ('useUIStream and useChatUI return Vue Refs'), Event System, and Dynamic Prop Expressions are single-line mentions with no executable example. Mostly executable with minor gaps — anchor 4, not 5.	4 / 5
Workflow Clarity	A clear, ordered setup path (install → create catalog → define registry → render specs) with unambiguous steps. No validation checkpoints, but nothing here is destructive or batch, so the cap does not apply; it falls short of anchor 5 because there are no explicit feedback loops or checkpoints.	4 / 5
Progressive Disclosure	Sections are well-organized, but roughly 200 lines of API reference (Providers, Composables, Key Exports tables) are inlined in SKILL.md with no external reference files at all — no references/, scripts/, or assets/ bundle exists. This matches anchor 3 ('content that should be separate is inline'), not anchor 4 which expects the bulk split out.	3 / 5
	Total	15 / 20 Passed

Description

82%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 with an explicit, multi-trigger 'Use when' clause and consistent Vue/json-render scoping. Its only weakness is a thin 'what' — a single capability statement that enumerates few concrete actions.

Suggestions

List 2-3 more concrete capabilities in the 'what' clause (e.g., 'with state binding, visibility conditions, and action handling') to lift specificity.

Add a couple of natural synonym terms (e.g., 'JSON-driven UI', 'spec-based rendering') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Vue 3 renderer for json-render') and one concrete capability, but lists no further actions such as state binding, visibility, or actions. It is above anchor 2 (which expects only generic actions) but below anchor 4, which requires several specific actions.	3 / 5
Completeness	Explicitly answers what ('Vue 3 renderer for json-render') and when, with a concrete multi-clause 'Use when building Vue UIs from JSON specs, working with @json-render/vue, defining Vue component registries, or rendering AI-generated specs in Vue.' This matches anchor 5; anchor 4 would require a less specific 'when' clause.	5 / 5
Trigger Term Quality	Covers natural phrases users would say: 'building Vue UIs from JSON specs', 'defining Vue component registries', 'rendering AI-generated specs in Vue', plus the package name. Missing common variations/synonyms, so it falls short of anchor 5's comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Clear niche (json-render Vue renderer) with distinct triggers; the Vue qualifier appears in every trigger phrase, minimizing conflict with sibling renderers or generic Vue skills. Fits anchor 5.	5 / 5
	Total	17 / 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: 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.