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.
82
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/react-native-best-practices/SKILL.mdQuality
Discovery
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.
This is an excellent skill description that clearly defines its scope (React Native performance optimization), lists specific concrete capabilities and metrics, and provides explicit trigger conditions via the 'Applies to' clause. The rich set of domain-specific keywords ensures accurate skill selection, and the narrow focus on React Native performance makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and areas: FPS, TTI, bundle size, memory leaks, re-renders, animations, Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, debugging jank and frame drops. | 3 / 3 |
Completeness | Clearly answers both 'what' (provides React Native performance optimization guidelines for specific metrics) and 'when' (applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops). The 'Applies to' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'React Native', 'FPS', 'TTI', 'bundle size', 'memory leaks', 're-renders', 'animations', 'Hermes', 'JS thread blocking', 'bridge overhead', 'FlashList', 'native modules', 'jank', 'frame drops'. These are highly specific and natural keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting React Native performance specifically, with very specific trigger terms like 'Hermes', 'FlashList', 'bridge overhead', 'jank', and 'frame drops' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured index/overview skill that excels at progressive disclosure and navigation across a large set of reference files. Its main weakness is that the overview itself is light on directly actionable, executable content—most concrete guidance is deferred to reference files. The skill could be tightened by removing meta-sections (Skill Format, When to Apply) and adding more inline executable examples in the Quick Reference sections.
Suggestions
Add executable code examples to the Quick Reference sections (e.g., a FlashList replacement snippet, a Reanimated worklet example) instead of just listing bullet-point fixes.
Remove or condense the 'Skill Format' and 'When to Apply' sections—Claude can infer when to apply these guidelines from context, and the format description is meta-information about reference files that doesn't help with the task.
Add validation/verification steps to the Quick Reference workflows (e.g., 'After applying fix, re-measure FPS to confirm improvement' or 'Verify bundle size reduction with source-map-explorer').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary framing (e.g., the 'Skill Format' section explaining the reference file format, the 'When to Apply' section listing obvious triggers). The reference tables are useful but verbose given the large number of files listed. The grep examples for searching references add marginal value. | 2 / 3 |
Actionability | Provides some concrete commands (bundle analysis, grep searches) and specific fix recommendations, but most guidance is at the 'pointer' level—directing to reference files rather than providing executable solutions inline. The Quick Reference sections list fixes as bullet points without executable code examples for most items. | 2 / 3 |
Workflow Clarity | The Problem → Skill Mapping table provides clear diagnostic workflows with sequenced steps (measure → analyze → fix). However, there are no explicit validation checkpoints or feedback loops for any of the optimization processes. For performance optimization (which can involve destructive changes like bundle configuration), verification steps are missing. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: concise overview with quick reference patterns inline, well-organized reference tables pointing to one-level-deep detail files, clear categorization (js-*, native-*, bundle-*), and a problem-to-skill mapping for navigation. References are clearly signaled and organized. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
2c6f6e8
Table of Contents
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.