react-native-best-practices

Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.

Quality

92%

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

Quality

Content

85%

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

A well-structured, highly actionable overview with clear workflow sequencing and exemplary progressive disclosure via indexed reference files. The only weakness is version-pinned details that are time-sensitive and not isolated in a deprecated section.

Suggestions

Move version-pinned guidance (FlashList v2, Expo SDK 52+, React Native 0.78) into a dedicated 'Version notes' or 'Deprecated/old patterns' section so the main guidance stays evergreen.

Consider centralizing version thresholds in one place so future SDK updates require editing a single section rather than scattered guardrails.

Dimension	Reasoning	Score
Conciseness	Mostly lean with terse tables and bullets, but carries several time-sensitive version pins ('FlashList v2', 'Expo SDK 52+', 'React Native 0.78 and earlier') outside any deprecated/old-patterns section, which the rubric flags for conciseness.	2 / 3
Actionability	Provides fully executable commands ('agent-device react-devtools profile start', 'npx react-native bundle ...', 'npx source-map-explorer output.js') and concrete, copy-paste-ready fixes per category.	3 / 3
Workflow Clarity	The 'Optimization Workflow' sequences Measure → Optimize → Re-measure → Validate with an explicit validation checkpoint and a feedback loop ('If metrics did not improve, revert and try the next suggested fix').	3 / 3
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references: an annotated References table per prefix and a Problem→Skill mapping; all referenced files exist under references/.	3 / 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 concise, third-person description that names both the capability set and explicit application triggers with strong natural keyword coverage. It clearly answers what and when with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities—'FPS, TTI, bundle size, memory leaks, re-renders, and animations' plus 'Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules'—rather than vague language.	3 / 3
Completeness	States what it does ('Provides React Native performance optimization guidelines for...') and when to use it via the explicit trigger clause 'Applies to tasks involving...'.	3 / 3
Trigger Term Quality	Covers natural terms a RN developer would actually say—'jank', 'frame drops', 're-renders', 'memory leaks', 'bundle size', 'TTI', 'FlashList', 'Hermes'—with good breadth of variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear React Native performance niche with distinct triggers (Hermes, FlashList, jank, frame drops, bridge overhead) unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: callstackincubator/agent-skills
Path: skills/react-native-best-practices/SKILL.md
Commit: f6b87e3

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.