Content
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body offers one good executable component example and clean section organization, but it is weighed down by a large non-instructional YAML config block, abstract high-level guidance, and a complete absence of any sequenced workflow or validation steps for a complex domain. It reads more as agent configuration than as focused skill instruction.
Suggestions
Remove or relocate the large YAML configuration block out of the SKILL.md body so the instructional content is not buried under non-instructional boilerplate.
Add a concrete multi-step workflow with validation checkpoints for the risky operations the skill covers (e.g. native module changes: scaffold -> implement -> build on both platforms -> verify), since missing validation for destructive/platform-specific changes caps workflow clarity.
Split deeper material (native module integration, navigation patterns, platform-specific styling) into reference files under references/ and link to them from the body to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The instructional markdown is reasonably lean, but ~140 of the body's ~230 lines are a non-instructional YAML config block (triggers, constraints, emoji-echoing hooks) that adds bulk, and some best-practice bullets restate React Native basics Claude already knows — so it is mostly efficient but could be tightened. | 2 / 3 |
Actionability | A complete, copy-paste-ready JSX component example with imports, hooks, and Platform.select is provided, but the surrounding guidance ('Implement navigation and state management', 'Optimize images and assets') is abstract with no specific commands or workflows — concrete but incomplete. | 2 / 3 |
Workflow Clarity | There is no multi-step workflow or validation checkpoint anywhere; the numbered list is a set of responsibility areas, not a sequence, and the skill claims a complex multi-step domain (RN dev across iOS/Android, native modules) with no sequencing — matching the 'steps unclear or missing' anchor. | 1 / 3 |
Progressive Disclosure | Sections are clearly organized (responsibilities, best practices, component patterns, platform considerations) and no bundle files exist, but a broad domain like React Native development keeps potentially separable material (native modules, navigation, styling) inline with no reference files to split it out. | 2 / 3 |
Total | 7 / 12 Passed |