vercel-react-native-skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

2.15x

Quality

81%

Does it follow best practices?

Impact

99%

2.15x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

75%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 clean, well-organized reference catalog that uses progressive disclosure effectively and gives concrete, tool-specific directives per rule. It is held back from the top band by minor redundancy in the intro/When-to-Apply sections, no inline code examples, and referenced detail files that are absent from the bundle.

Suggestions

Trim the redundant intro paragraph and "When to Apply" list, which restate the categories shown in the priority table and the triggers already in the description, to tighten token efficiency.

Add 1-2 inline code snippets for the highest-priority rules (e.g., a minimal FlashList example) so Claude can act without opening every rule file.

Ensure the referenced `rules/*.md` files and `AGENTS.md` are included in the skill bundle so the one-level-deep references actually resolve for a reader.

Dimension	Reasoning	Score
Conciseness	The rule catalog is lean (one-line directives each) and avoids over-explaining concepts Claude knows, but the intro paragraph and "When to Apply" list restate categories already shown in the priority table and triggers already in the description, a minor redundancy that keeps it below 5.	4 / 5
Actionability	Each rule is a concrete, actionable directive naming specific tools (FlashList, expo-image, Reanimated, Galeria, Pressable, StyleSheet.create), giving usable decisions; however no inline code examples appear in the body, with implementation deferred to per-rule files, a minor gap versus copy-paste-ready guidance.	4 / 5
Workflow Clarity	Usage is unambiguous (identify the relevant rule from the catalog, then read its file, which contains explanation + incorrect/correct examples + context) and there are no destructive or batch operations requiring validation checkpoints; not a multi-step workflow, so it stops short of 5.	4 / 5
Progressive Disclosure	Well-structured overview with a priority table, quick-reference rule list, and one-level-deep pointers to `rules/*.md` and `AGENTS.md`; however those referenced files are not present in the provided bundle, so the references cannot be verified to resolve, pulling it below 5.	4 / 5
	Total	16 / 20 Passed

Description

87%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, well-structured description that clearly states the skill's purpose and gives explicit, natural trigger conditions for activation. Minor gaps in action specificity and synonym/extension coverage keep trigger quality and specificity at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("building React Native components", "optimizing list performance", "implementing animations", "working with native modules"), though a couple ("building components", "working with native modules") are slightly generic, keeping it just below comprehensive.	4 / 5
Completeness	Explicitly answers both what ("React Native and Expo best practices for building performant mobile apps") and when ("Use when building... Triggers on tasks involving...") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say ("React Native", "Expo", "mobile performance", "native platform APIs", "list performance", "animations", "native modules") with an explicit "Triggers on tasks involving..." clause; missing synonyms/file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (React Native/Expo mobile development) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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/agent-skills
Path: skills/react-native-skills/SKILL.md
Commit: b8caa26

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