react-native

React Native renderer for json-render that turns JSON specs into native mobile UIs. Use when working with @json-render/react-native, building React Native UIs from JSON, creating mobile component catalogs, or rendering AI-generated specs on mobile.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/react-native/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.

The body is a dense, actionable reference with executable examples and clean section structure. Its main gap is progressive disclosure: everything is inlined in SKILL.md with no one-level-deep reference files for the component catalog and exports.

Suggestions

Move the full Standard Components catalog and/or the Key Exports table into reference files (e.g. references/components.md, references/exports.md) and link to them from SKILL.md so the overview stays lean.

Tighten the opening paragraph (currently restates the frontmatter description) and remove redundant sentences like the restated "Components do not use a statePath prop" guidance where $bindState is already documented.

Complete the Quick Start example so it runs as-is: add the missing `Ionicons` import and a type for the `spec` prop, raising actionability to fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is information-dense (component lists, exports table, executable examples) and does not explain concepts Claude already knows, but the opening line restates the frontmatter description and a few sections could be trimmed, keeping it just short of fully lean.	4 / 5
Actionability	The Quick Start is near copy-paste-ready TSX and the JSON snippets for visibility, setState, and dynamic props are concrete, but minor gaps (e.g. `Ionicons` used without an import, `spec` prop untyped) prevent a fully executable 5.	4 / 5
Workflow Clarity	The Quick Start gives a coherent sequence (define catalog -> define registry -> wrap in providers -> render) and the skill is non-destructive so no validation cap applies, though it is a reference doc rather than a multi-step workflow with explicit checkpoints.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but ~180 lines are entirely inline with no bundle files or external references; the full standard-component catalog and the large Key Exports table are content that could live in separate reference files.	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.

The description is well-formed: third-person voice, clear what/when structure, and distinct package-scoped triggers. Its only weakness is specificity, as it names one main action rather than enumerating the renderer's several concrete capabilities.

Dimension	Reasoning	Score
Specificity	"turns JSON specs into native mobile UIs" names the domain and one concrete action, but does not enumerate several specific capabilities (e.g. data binding, visibility, actions), so it stops at 1-2 concrete actions rather than a comprehensive list.	3 / 5
Completeness	It explicitly states what ("React Native renderer for json-render that turns JSON specs into native mobile UIs") and when ("Use when working with ... building ... creating ... or rendering ...") with concrete trigger phrases, satisfying both halves clearly.	5 / 5
Trigger Term Quality	Trigger phrases "working with @json-render/react-native", "building React Native UIs from JSON", "creating mobile component catalogs", and "rendering AI-generated specs on mobile" give good natural keyword coverage, though a few synonymous phrasings users might say are missing.	4 / 5
Distinctiveness Conflict Risk	The narrow niche (React Native renderer for the json-render ecosystem) plus package-specific triggers make it clearly distinguishable from other skills with minimal conflict risk.	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/react-native/SKILL.md
Commit: 0f6798b

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