CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A dense, well-structured reference with executable examples and a clear setup sequence; its main weakness is monolithic inline API content with no progressive disclosure to separate reference files.

Suggestions

Move the full Standard Components catalog and/or the Key Exports table into a separate reference file (e.g. references/COMPONENTS.md, references/API.md) and link to them from SKILL.md so the overview stays lean.

Keep only the most-used components and exports inline as examples, pointing to the reference file for the complete list.

Add clearly signaled one-level-deep references (e.g. "Full component reference: see COMPONENTS.md") so detail is discoverable without bloating the main skill body.

DimensionReasoningScore

Conciseness

Lean reference-style content — bullet lists and tables for components, providers, and exports — with no padding explaining what React Native or JSON is; every section adds information Claude would not already know.

3 / 3

Actionability

Provides a complete, copy-paste-ready Quick Start (catalog → registry → providers → Renderer) plus concrete JSON snippets for the Pressable/setState pattern, dynamic prop expressions, and external-store controlled mode.

3 / 3

Workflow Clarity

The Quick Start sequences the setup unambiguously (defineCatalog → defineRegistry → wrap in StateProvider/VisibilityProvider/ActionProvider → Renderer); no destructive or batch operation is present, so the absence of validation checkpoints does not cap the score.

3 / 3

Progressive Disclosure

Sections are well-organized, but ~180 lines of inline API reference (full standard-component catalog, providers table, and key-exports table) live entirely in SKILL.md with no references to deeper files, matching the score-2 anchor of inline content that could be split out.

2 / 3

Total

11

/

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 description: concrete actions, natural trigger terms, explicit what-and-when guidance, and a distinct package-scoped niche. Third-person voice is maintained throughout with no vague filler.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "turns JSON specs into native mobile UIs", "building React Native UIs from JSON", "creating mobile component catalogs", "rendering AI-generated specs on mobile" — matching the score-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly states what it does ("React Native renderer for json-render that turns JSON specs into native mobile UIs") and when to use it ("Use when working with @json-render/react-native, building React Native UIs from JSON..."), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "React Native", "JSON specs", "native mobile UIs", "mobile component catalogs", "AI-generated specs" — with good variation rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to a named package and platform ("@json-render/react-native", "native mobile UIs"), giving it a clear niche unlikely to collide with web or generic JSON-render skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
vercel-labs/json-render
Reviewed

Table of Contents

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.