react-native

React Native mobile patterns, platform-specific code

Quality

43%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/react-native/SKILL.md

Quality

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 concrete actions, lacks a 'Use when...' clause, and doesn't include sufficient trigger terms for reliable matching.

Suggestions

Add specific concrete actions the skill covers, e.g., 'Creates React Native components, handles platform-specific styling for iOS and Android, configures native modules, sets up navigation stacks.'

Add an explicit 'Use when...' clause with 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 user-facing keywords and file extensions like 'iOS', 'Android', 'cross-platform', 'Expo', 'mobile app', '.tsx', 'native modules' 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 specify what actions are performed (e.g., creating components, handling navigation, configuring native modules).	1 / 3
Completeness	The 'what' is extremely vague ('patterns' and 'platform-specific code' don't explain what the skill actually does), and there is no 'when' clause or explicit trigger guidance at all.	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 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, but 'mobile patterns' and 'platform-specific code' are broad enough to potentially overlap with native iOS/Android development 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 TypeScript examples and clear section organization. However, it over-explains patterns Claude already knows (basic React hooks, functional components, explicit typing) and lacks workflow guidance for when/how to apply these patterns in sequence. The content would benefit from trimming well-known patterns and adding decision-making guidance or splitting into overview + detailed reference files.

Suggestions

Trim sections that explain patterns Claude already knows well (functional components, useState, explicit props interfaces) and focus on project-specific conventions or non-obvious patterns.

Add a decision workflow for state management: when to use local state vs Zustand vs React Query, with concrete criteria rather than just 'escalate when needed'.

Split detailed testing patterns and state management examples into separate reference files, keeping SKILL.md as a concise overview with links.

Add validation/verification guidance — e.g., how to verify a new component works (run tests, check TypeScript compilation, test on both platforms).

Dimension	Reasoning	Score
Conciseness	The skill is reasonably structured but includes patterns Claude already knows well (functional components, useState, React Query basics, Zustand setup). The anti-patterns list at the end is mostly common knowledge. Some sections like explicit props interfaces and 'local state first' are unnecessary to spell out for Claude.	2 / 3
Actionability	All code examples are fully executable TypeScript/TSX with proper imports, typed interfaces, and complete implementations. The testing examples are copy-paste ready with assertions, and the platform-specific code shows concrete StyleSheet patterns.	3 / 3
Workflow Clarity	The skill presents patterns and examples but lacks any workflow sequencing — there's no guidance on when to apply which pattern, no decision tree for state management escalation (useState → Zustand → React Query), and no validation steps for ensuring components work correctly after creation. For a patterns-focused skill this is acceptable but not ideal.	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 testing patterns or state management details) could be split into separate files. However, the sections are well-organized with clear headers.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: 7e5f7a2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.