react-native

React Native mobile patterns, platform-specific code

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, highly actionable patterns catalog with executable examples and clean sectioning; its only gaps are the absence of any multi-step workflow with validation checkpoints and lack of progressive disclosure into reference files.

Dimension	Reasoning	Score
Conciseness	The body is lean: code examples with terse inline comments and short rule lists, no explanations of what React Native or basic libraries are, so every token largely earns its place as in the 3 anchor.	3 / 3
Actionability	Examples are complete, executable TypeScript/TSX (Button, useHome, Zustand store, React Query hooks, RNTL tests, Platform.select) plus a concrete file-naming convention for platform splits, matching the copy-paste-ready 3 anchor.	3 / 3
Workflow Clarity	The skill is a patterns catalog with well-organized sections rather than a multi-step process, and contains no sequenced workflow with validation checkpoints; it clears the 2 anchor (clear sections, no destructive/batch sequence requiring feedback loops) but lacks the explicit validate->fix->retry flow needed for 3.	2 / 3
Progressive Disclosure	All content lives inline in a single ~240-line SKILL.md with no bundle/reference files and no one-level-deep references; sections are well organized, but material (e.g. full testing or state-management guides) that could be split out is inline, fitting the 2 rather than the 3 anchor which requires well-signaled external references.	2 / 3
	Total	10 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear, distinctive niche but is a noun phrase lacking concrete actions and an explicit 'Use when' trigger in the description field itself, leaving it adequate rather than strong.

Suggestions

Rewrite as concrete actions, e.g. 'Write and debug React Native components, manage navigation, state, and platform-specific iOS/Android code.'

Add an explicit trigger clause to the description: 'Use when working on React Native (.tsx/.jsx) mobile apps, ios/ or android/ builds, or platform-specific code.'

Include natural trigger variations users say — 'React Native', 'mobile app', 'iOS/Android build', '.tsx' — to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'React Native mobile patterns, platform-specific code' names the domain clearly but lists no concrete actions or capabilities — it is a noun phrase, not a set of actions, so it falls short of the multi-action anchor at 3 yet is more concrete than the vague anchor at 1.	2 / 3
Completeness	It states what the skill covers ('mobile patterns, platform-specific code') but the description field itself has no 'Use when...' trigger clause; per the guidelines a missing explicit trigger caps completeness at 2, and it is not weak enough on 'what' to drop to 1.	2 / 3
Trigger Term Quality	'React Native' is a natural term users would say, but the description misses common variations and trigger phrasings (e.g. 'mobile app', 'iOS/Android build', '.tsx'), placing it at 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	'React Native mobile patterns, platform-specific code' carves a clear niche unlikely to trigger for non-mobile or non-RN skills, matching the distinct-trigger anchor at 3.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 5 hours 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.