react-three-fiber

React Three Fiber 3D renderer for json-render. Use when working with @json-render/react-three-fiber, building 3D scenes from JSON specs, rendering meshes/lights/models/environments, or integrating Three.js with json-render catalogs.

Quality

82%

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

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable reference with executable examples and clean sectioning, but it is a single inline document with no progressive file disclosure and embeds version numbers that hurt conciseness. Workflow sequencing is implicit rather than checkpointed.

Suggestions

Move version-pinned peer dependencies into a short note or a separate reference, or mark them as time-sensitive, to avoid penalizing conciseness.

Split the full component prop reference and materialSchema into a referenced file (e.g. REFERENCE.md) so SKILL.md stays a lean overview.

Make the catalog→registry→render workflow explicit as numbered steps with a validation checkpoint (e.g. confirm the registry keys match the catalog definitions) before rendering.

Dimension	Reasoning	Score
Conciseness	Mostly lean and reference-style with no concept explanations Claude already knows, but the Dependencies section embeds time-sensitive version numbers (">= 8.0.0", "^19.0.0", "^4.0.0") outside any deprecated/old-patterns section, which the guidelines penalize.	2 / 3
Actionability	Provides complete, copy-paste-ready executable examples for catalog/registry setup, ThreeCanvas, manual Canvas, custom schemas, and a full JSON spec format — concrete and specific.	3 / 3
Workflow Clarity	The catalog-then-registry-then-render sequence is present via inline code comments, but there are no explicit validation checkpoints or feedback loops; checkpoints are only implicit.	2 / 3
Progressive Disclosure	Well-organized into clear sections, but at ~175 lines with no bundle/reference files, content that could be split out (full component prop listing, materialSchema dump) is inline rather than one level deep in referenced files.	2 / 3
	Total	9 / 12 Passed

Description

100%

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, third-person description that names concrete capabilities and provides explicit, multi-trigger "Use when" guidance tied to a specific package. No fluff or over-claims; unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "building 3D scenes from JSON specs", "rendering meshes/lights/models/environments", "integrating Three.js with json-render catalogs" — rather than vague language.	3 / 3
Completeness	Explicitly states what ("React Three Fiber 3D renderer for json-render") and when via a clear "Use when working with..." clause with multiple triggers.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered: "3D scenes", "meshes/lights/models/environments", "Three.js", plus the explicit package name "@json-render/react-three-fiber" as a strong trigger.	3 / 3
Distinctiveness Conflict Risk	Narrow niche coupling React Three Fiber to json-render with the package name named explicitly, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 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/react-three-fiber/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.