react-native
React Native mobile patterns, platform-specific code
54
43%
Does it follow best practices?
Impact
Pending
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 too terse and vague to effectively guide skill selection. It names the technology domain (React Native) but fails to describe specific capabilities or provide any trigger guidance for when Claude should select this skill. It reads more like a topic tag than a functional description.
Suggestions
Add specific concrete actions the skill covers, e.g., 'Build React Native components, handle platform-specific styling for iOS and Android, configure native modules, set up navigation stacks, and manage app state.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about React Native, mobile app development, iOS/Android cross-platform code, Expo, or .tsx mobile components.'
Include common file types and tool names users might mention, such as '.tsx', 'Expo', 'Metro bundler', 'react-navigation', to improve trigger term coverage.
| 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., create components, handle navigation, configure native modules). | 1 / 3 |
Completeness | The 'what' is extremely vague ('patterns' and 'platform-specific code' don't describe concrete capabilities), and there is no 'when' clause or explicit trigger guidance at all. Both components are weak or missing. | 1 / 3 |
Trigger Term Quality | 'React Native' and 'mobile' are natural keywords users might say, and 'platform-specific code' is somewhat relevant. However, it's missing common variations like 'iOS', 'Android', 'app development', 'expo', '.tsx', or specific tasks users would mention. | 2 / 3 |
Distinctiveness Conflict Risk | 'React Native' provides some specificity that distinguishes it from general React or web development skills, but '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 is a solid reference skill with excellent, executable code examples covering key React Native patterns. Its main weaknesses are including some patterns Claude already knows (basic React concepts), lack of workflow/process guidance for building features, and being somewhat monolithic when it could split detailed sections into referenced files. The anti-patterns list is useful but largely common knowledge.
Suggestions
Trim sections that cover basic React/TypeScript knowledge Claude already has (e.g., explicit props interfaces, basic useState) and focus on React Native-specific patterns and gotchas.
Add a brief workflow section describing the process for creating a new feature or screen, including validation steps like running tests and checking platform-specific rendering.
Split detailed sections (testing patterns, state management) into separate referenced files to keep SKILL.md as a concise overview with navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some patterns Claude already knows well (e.g., basic useState, explicit props interfaces, functional components). The anti-patterns list at the end is largely common React knowledge. Some sections like 'Props Interface Always Explicit' add little value for Claude. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready TypeScript/React Native code examples throughout — component patterns, hooks, state management with Zustand and React Query, testing with RNTL, and platform-specific code. All examples are concrete and complete. | 3 / 3 |
Workflow Clarity | The skill presents patterns and examples clearly but lacks workflow sequencing — there's no guidance on the process of building a feature, no validation checkpoints (e.g., running tests after changes, verifying platform-specific behavior), and no error recovery steps. For a patterns-focused skill this is acceptable but the absence of any build/test workflow steps limits it. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a logical progression from project structure to components to state to testing. However, at ~200 lines it's a substantial amount of inline content that could benefit from splitting detailed sections (testing, state management) into separate referenced files. The 'Load with: base.md + typescript.md' hint suggests awareness of modularity but the skill itself doesn't reference any supplementary files. | 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
d4ddb03
- 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.