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.
94
Quality
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 technical terminology is appropriate for the target audience and creates a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and metrics: 'FPS, TTI, bundle size, memory leaks, re-renders, and animations' plus specific technologies like 'Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules'. | 3 / 3 |
Completeness | Clearly answers both what ('Provides React Native performance optimization guidelines for FPS, TTI, bundle size...') and when ('Applies to tasks involving Hermes optimization, JS thread blocking... or debugging jank and frame drops'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'React Native', 'performance', 'FPS', 'jank', 'frame drops', 'memory leaks', 're-renders', 'animations', 'Hermes', 'FlashList', 'native modules' - these are all terms developers naturally use when discussing RN performance issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with React Native-specific terminology (Hermes, bridge overhead, FlashList) that wouldn't overlap with general web performance, native iOS/Android, or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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 performance optimization skill that efficiently organizes complex information through tables, priority ordering, and clear references. The content is highly actionable with executable commands and concrete fix recommendations. The main weakness is the lack of explicit validation/verification steps after applying optimizations, which would help confirm improvements were successful.
Suggestions
Add verification steps after each 'Common fixes' section (e.g., 'Re-run FPS measurement to confirm improvement above 60fps')
Include a brief feedback loop in the Problem → Skill Mapping showing how to verify the fix worked before moving on
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and brief code snippets without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary explanations about what React Native is. | 3 / 3 |
Actionability | Provides executable shell commands for profiling and bundle analysis, concrete fix recommendations, and clear problem-to-solution mappings. The grep commands and npx commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | While the Problem → Skill Mapping provides good sequencing for debugging workflows, the skill lacks explicit validation checkpoints. For example, after applying fixes, there's no 'verify improvement' step or feedback loop for confirming optimizations worked. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick reference sections for immediate use, and well-organized tables pointing to detailed reference files. All references are one level deep with clear categorization and impact ratings. | 3 / 3 |
Total | 11 / 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 | |
355d067
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.