solid

SolidJS renderer for json-render. Use when building @json-render/solid catalogs/registries, wiring Renderer providers, implementing bindings/actions, or troubleshooting Solid-specific reactivity patterns.

Quality

75%

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/solid/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 dense, actionable reference with strong executable examples and clear reactivity guidance. It is weakened by inline API enumeration that could be offloaded to reference files and by the absence of any sequencing or validation checkpoints.

Suggestions

Move the Providers, Hooks, and Built-in Actions enumerations into a referenced reference file (e.g. API.md) and keep SKILL.md as a concise overview with one-level-deep links.

Tighten the inline API lists to the few entries users actually need up front, trimming tokens that compete with conversation context.

Add a short ordered 'build a component' workflow (define catalog -> register component -> wire provider -> render) so the multi-step path is sequenced rather than implied by section order.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code and terse bullets with little conceptual padding, but the Providers, Hooks, and Built-in Actions sections enumerate APIs as inline lists without enough context to be self-contained, so it could be tightened rather than scoring a 3.	2 / 3
Actionability	Provides multiple copy-paste-ready executable snippets (Quick Start, defineCatalog, defineRegistry, useBoundProp, useUIStream) plus concrete binding expression forms, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Content is organized into labeled sections with explicit do/don't guidance in 'Solid Reactivity Rules', but it is a reference rather than a sequenced multi-step workflow and lacks validation checkpoints, so it sits at the 'steps listed but no checkpoints' level.	2 / 3
Progressive Disclosure	It is a single well-sectioned file with no nested references, but the full API and hook enumerations live inline rather than being split into referenced files, fitting the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

85%

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, specific description with an explicit Use-when trigger and a clear niche. Its main weakness is trigger-term coverage that leans heavily on specialized jargon rather than natural user phrasing.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'building @json-render/solid catalogs/registries, wiring Renderer providers, implementing bindings/actions, troubleshooting Solid-specific reactivity patterns' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what ('SolidJS renderer for json-render') and when via an explicit 'Use when ...' clause, satisfying both halves of the anchor.	3 / 3
Trigger Term Quality	Terms like 'SolidJS renderer', 'Renderer providers', and 'reactivity patterns' are relevant but technical and niche, lacking common layperson variations a broader user base might say; not a score 3 because coverage of natural variations is thin.	2 / 3
Distinctiveness Conflict Risk	Scoped to the SolidJS + json-render niche with triggers tied to that ecosystem, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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/solid/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.