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.
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 capabilities and metrics, and provides explicit trigger conditions. The description uses appropriate third-person voice, includes highly relevant technical trigger terms that developers would naturally use, and occupies a clear, distinct niche.
| 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 second sentence serves as an explicit trigger clause. | 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', 'jank', 'frame drops'. These are highly specific and natural keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on React Native performance optimization. The combination of React Native + performance + specific technical terms like Hermes, FlashList, bridge overhead makes it very 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 to detailed reference files. Its main weaknesses are that the inline content is more descriptive than actionable (most concrete guidance is deferred to references), and it includes some unnecessary meta-explanation (skill format section, grep examples). Adding a few more executable inline examples and trimming meta-content would significantly improve it.
Suggestions
Add 1-2 executable code examples inline for the most critical patterns (e.g., FlashList usage, React Compiler setup) rather than deferring everything to reference files.
Remove the 'Skill Format' section — it describes the reference file structure which Claude can discover on its own when reading those files.
Remove the 'Searching References' section with basic grep commands, as Claude already knows how to search files.
Add validation checkpoints to the Quick Reference workflows, e.g., 'After bundle analysis, verify the largest modules account for the expected percentage before optimizing.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary meta-content (explaining the skill format, impact rating definitions) and the 'Searching References' section with basic grep commands that Claude already knows. The reference tables are useful but could be more compact. | 2 / 3 |
Actionability | The Quick Reference sections provide some concrete commands (bundle analysis, DevTools access), but most guidance is high-level bullet points ('Use atomic state', 'Enable tree shaking') without executable code examples. The actual actionable content is deferred to reference files rather than provided inline. | 2 / 3 |
Workflow Clarity | The Problem → Skill Mapping table provides clear diagnostic workflows, and the priority ordering is helpful. However, there are no explicit validation checkpoints or feedback loops for multi-step processes like bundle optimization or profiling — steps are listed but lack 'verify before proceeding' gates. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: concise overview with quick reference patterns inline, well-organized reference tables with clear file naming conventions, and a problem-to-skill mapping for navigation. All references are one level deep with clear signaling. | 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
05d40bb
- 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.