react-native
React Native mobile patterns, platform-specific code
43
43%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/react-native/SKILL.mdQuality
Discovery
22%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 description is far too terse and vague to be effective for skill selection. It names the technology domain (React Native) but fails to describe concrete actions, lacks a 'Use when...' clause, and doesn't include sufficient trigger terms for reliable matching. It reads more like a tag or category label than a functional skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Implements navigation, handles platform-specific styling for iOS/Android, creates native module bridges, manages app state in React Native projects.'
Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user is building React Native apps, working with iOS/Android platform differences, Expo, or mobile UI components.'
Include natural keyword variations users might say: 'React Native', 'RN', 'mobile app', 'iOS', 'Android', 'Expo', 'native modules', 'cross-platform mobile'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'patterns' and 'platform-specific code' without listing any concrete actions. It doesn't describe what the skill actually does (e.g., 'creates navigation flows', 'implements native modules', 'handles platform-specific styling'). | 1 / 3 |
Completeness | The 'what' is extremely weak (just 'patterns' and 'code'), and there is no 'when' clause at all. There's no explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | 'React Native' and 'mobile' are natural keywords users would say, and 'platform-specific' is somewhat relevant. However, it's missing common variations like 'iOS', 'Android', 'expo', 'native modules', '.tsx', or specific patterns users might ask about. | 2 / 3 |
Distinctiveness Conflict Risk | 'React Native' provides some specificity that distinguishes it from general React or web development skills. However, 'mobile patterns' and 'platform-specific code' are broad enough to potentially overlap with native iOS/Android skills or general mobile development skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, executable React Native patterns with good code examples, but it largely documents standard conventions that Claude already knows. It lacks workflow guidance for multi-step processes (e.g., creating a new feature end-to-end) and could benefit from focusing on project-specific conventions or non-obvious patterns rather than general React Native best practices. The content would be stronger if trimmed to only novel, project-specific guidance.
Suggestions
Remove sections covering standard React Native knowledge (basic useState, functional components, explicit props) and focus on project-specific conventions or non-obvious patterns that Claude wouldn't already know.
Add a workflow section with sequenced steps for common tasks like 'adding a new screen' or 'adding a new feature end-to-end' with validation checkpoints (e.g., run tests, check types).
Split detailed testing examples and state management patterns into separate reference files, keeping SKILL.md as a concise overview with links.
Add decision criteria for when to use each state management approach (local vs Zustand vs React Query) as a quick-reference table rather than separate code blocks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes patterns Claude already knows well (basic useState, functional components, explicit props interfaces). The project structure tree and many code examples cover standard React Native conventions that don't add novel knowledge. Some sections like 'Props Interface Always Explicit' and 'Local State First' are unnecessary for Claude. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript/TSX with proper imports, typed interfaces, and complete implementations. The examples cover components, hooks, state management, testing, and platform-specific code with copy-paste ready patterns. | 3 / 3 |
Workflow Clarity | The skill presents patterns and examples but lacks any workflow sequencing for common multi-step tasks like setting up a new screen, adding a feature end-to-end, or debugging platform-specific issues. There are no validation checkpoints or decision trees for when to escalate state management or split platform-specific files. | 2 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents. At ~200 lines covering project structure, components, state management, testing, platform code, and anti-patterns, some sections (like detailed testing examples or state management patterns) could be split into separate reference files. However, the section headers provide reasonable organization. | 2 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
65efb33
- 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.