devtools-solid

SolidJS adapter for the json-render devtools inspector. Use whenever the user wants to add, configure, or troubleshoot @json-render/devtools-solid in a SolidJS json-render app, including spec inspection, state editing, action and stream timelines, catalog browsing, or DOM picking.

Quality

92%

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%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, well-structured body that gets a SolidJS user from install to a working mounted panel with minimal tokens and a clear pointer to shared capabilities. The only gap is that the mount example assumes spec(), messages(), and catalog are already defined without any hint.

Suggestions

Add a one-line note clarifying that spec(), messages(), and catalog come from the user's existing json-render setup so the mount snippet is fully self-explanatory.

Optionally name the shared capabilities file via a link (e.g. [devtools/SKILL.md](skills/devtools/SKILL.md)) so the one-level reference is navigable rather than a bare path.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or basic-concept explanations; every line delivers install or mount guidance. Not 4 because there are no instances of over-explanation to trim.	5 / 5
Actionability	Provides a concrete install command and copy-paste mount code with props, but references spec(), messages(), and catalog without defining them — minor gaps. Not 5 because those assumed bindings keep it from being fully self-contained copy-paste.	4 / 5
Workflow Clarity	Simple single-purpose skill sequenced as Install then Mount, both unambiguous; no destructive or batch operations so the validation cap does not apply. Not 4 because the sequence is fully clear with no checkpoint gaps for this scope.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and a single clearly-signaled one-level reference to skills/devtools/SKILL.md for shared capabilities. Not 4 because content is appropriately split and navigation is easy with no inline bulk that belongs elsewhere.	5 / 5
	Total	19 / 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, concise description that explicitly states both what the skill does and when to use it, with a concrete package trigger and a comprehensive list of supported capabilities. Its only weak spot is trigger-term coverage, which lacks synonyms beyond the core phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions — 'add, configure, or troubleshoot' plus 'spec inspection, state editing, action and stream timelines, catalog browsing, or DOM picking' — giving comprehensive coverage. Not 4 because the action list is broad and specific rather than having minor gaps.	5 / 5
Completeness	Explicitly answers what ('SolidJS adapter for the json-render devtools inspector' with capabilities) and when ('Use whenever the user wants to add, configure, or troubleshoot...') with concrete trigger phrases. Not 4 because both what and when are concrete and explicit.	5 / 5
Trigger Term Quality	Includes the concrete package trigger '@json-render/devtools-solid' plus natural verbs, but lacks synonyms or common variations users might say. Not 5 because coverage of natural terms is good but not comprehensive with synonyms.	4 / 5
Distinctiveness Conflict Risk	Targets a specific SolidJS package with distinct triggers, creating a clear niche with minimal conflict risk. Not 4 because the SolidJS + package-name scoping makes overlap with other skills minimal.	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/devtools-solid/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.