Content
14%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is dominated by an excessively large YAML frontmatter full of configuration that Claude cannot meaningfully use, while the actual body content is thin and generic. The body lists high-level responsibilities and best practices that Claude already knows, provides only one basic component example, and lacks any concrete workflows, validation steps, or progressive disclosure structure for the complex domain of React Native development.
Suggestions
Remove or drastically reduce the YAML frontmatter to essential metadata only, and invest those tokens in actionable body content with specific workflows (e.g., step-by-step guide for adding a new screen with navigation, integrating a native module, or configuring push notifications).
Add explicit multi-step workflows with validation checkpoints for common tasks like 'npx react-native run-ios' verification, pod install validation, and build error recovery loops.
Replace generic best practices bullets with concrete, executable examples — e.g., show a complete React Navigation setup, a FlatList optimization pattern, or a platform-specific permission request flow.
Create supporting reference files (e.g., NAVIGATION.md, NATIVE_MODULES.md, PLATFORM_SETUP.md) and link to them from the main skill to enable progressive disclosure of complex topics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is bloated with an enormous YAML frontmatter that Claude cannot act on (hooks, triggers, optimization settings, examples, integration metadata). The body itself lists generic best practices Claude already knows ('use functional components with hooks', 'test on both iOS and Android') and the component example is a basic boilerplate that adds little unique value. | 1 / 3 |
Actionability | The component pattern code example is executable and copy-paste ready, which is good. However, the 'key responsibilities' and 'best practices' sections are vague bullet points without concrete commands, specific library versions, or detailed implementation guidance. There's no actionable workflow for tasks like setting up navigation, integrating native modules, or handling permissions. | 2 / 3 |
Workflow Clarity | There is no multi-step workflow defined. The skill lists responsibilities and best practices as bullet points but provides no sequenced process for any task (e.g., creating a screen, adding a native module, setting up navigation). No validation checkpoints or error recovery steps are included in the body content despite the complexity of cross-platform mobile development. | 1 / 3 |
Progressive Disclosure | The content is a monolithic file with no references to supporting documents. There are no links to detailed guides for navigation setup, native module integration, platform-specific configurations, or any other advanced topics. Everything is crammed into one file with no structure for discovery, and no bundle files exist to support it. | 1 / 3 |
Total | 5 / 12 Passed |