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

86%

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

The canonical home for this skill is react-native-best-practices in callstackincubator/agent-skills

Quality

Content

81%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 an efficient, well-organized overview that delegates detail to a verified reference bundle with strong navigation aids. Workflows are sequenced with an implicit measure-first checkpoint, but explicit post-fix validation steps are not stated.

Suggestions

Add a brief verify-after-fix step to the quick-reference workflows (e.g., 'Re-measure FPS/TTI after each change to confirm improvement') to make validation checkpoints explicit.

Consider trimming the 'Skill Format' meta-explanation since the reference file headers already convey the hybrid format.

Link the inline image assets (e.g., flamegraph, treemap screenshots) from the relevant quick-reference sections so visual debugging aids are discoverable from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Lean tables, terse code blocks, and no basic-concept padding; the 'Skill Format' meta-explanation is slightly more than strictly needed but otherwise efficient.	4 / 5
Actionability	Concrete executable commands (react-native bundle, source-map-explorer) and specific fix lists cover common cases, with deeper detail appropriately delegated to reference files.	4 / 5
Workflow Clarity	Clear sequence via 'Profile first' and the Problem→Skill mapping; measurement-before-fix acts as a checkpoint, but explicit verify-after-fix validation is implicit rather than stated.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references; all 28 referenced files exist and are organized by category prefix with impact ratings and a problem→skill map.	5 / 5
	Total	17 / 20 Passed

Description

92%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 specific, complete, and clearly distinguishable, with a strong explicit 'what' and 'when' structure. Trigger term coverage is very strong though a few everyday user phrasings are missing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas (FPS, TTI, bundle size, memory leaks, re-renders, animations), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers 'what' (Provides RN perf optimization guidelines for...) and 'when' (Applies to tasks involving...) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural terms users say (jank, frame drops, re-renders, bundle size, memory leaks) plus technical synonyms (Hermes, FlashList); a few common phrasings like 'app is slow' or 'startup' are absent.	4 / 5
Distinctiveness Conflict Risk	Narrow React Native performance niche with distinct triggers (Hermes, FlashList, bridge overhead) and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 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: freekmurze/dotfiles
Path: config/claude/skills/react-native-best-practices/SKILL.md
Commit: a7899fe

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