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.
65
78%
Does it follow best practices?
Impact
—
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 technologies, and provides explicit trigger conditions via the 'Applies to tasks involving...' clause. The description uses appropriate third-person voice and includes a rich set of natural trigger terms that developers would actually use.
| 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 areas) and 'when' ('Applies to tasks involving...' serves as an explicit trigger clause listing specific scenarios). | 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 all terms developers naturally use when discussing RN performance. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: React Native performance optimization specifically. The combination of RN-specific terms like Hermes, bridge overhead, FlashList, and JS thread blocking makes it very unlikely to conflict with general web performance or other mobile framework 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 SKILL.md itself is more of a directory than an actionable guide — most concrete guidance is deferred to reference files. Adding validation/verification steps to workflows and including a few more executable code examples in the quick reference sections would significantly improve it.
Suggestions
Add verification steps to optimization workflows (e.g., 'After applying fix, re-measure FPS/TTI to confirm improvement exceeds X threshold')
Include 1-2 more complete, executable code examples in the Quick Reference sections (e.g., a FlashList replacement pattern, a Reanimated worklet example) rather than just bullet-point advice
Remove or condense the 'Skill Format' section — it explains the structure of reference files which Claude doesn't need upfront and can discover when reading them
The 'Searching References' grep section adds little value for Claude; consider removing it to save tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-organized and avoids explaining basic concepts, but includes some unnecessary meta-content (e.g., the 'Skill Format' section explaining the format of reference files, the 'Searching References' section with basic grep commands). The reference tables are useful but could be more compact. | 2 / 3 |
Actionability | Provides some concrete commands (bundle analysis, DevTools access) and specific library recommendations, but most guidance is at the 'common fixes' bullet-point level rather than executable code. The actual actionable content is deferred to reference files that aren't provided, making the SKILL.md itself more of a directory than an actionable guide. | 2 / 3 |
Workflow Clarity | The Problem → Skill Mapping table provides clear diagnostic sequences, and the priority ordering is helpful. However, there are no explicit validation checkpoints or feedback loops for any of the optimization workflows — it's 'profile → fix' without verification steps to confirm improvements were achieved. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: concise overview with quick references at the top, well-organized reference tables with clear file naming conventions, impact ratings, and a problem-to-skill mapping for navigation. References are one level deep and clearly signaled with descriptive tables. | 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 | |
- Repository
- freekmurze/dotfiles
- Commit
3974caa
- 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.