CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-native-architecture

Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecting React Native projects.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

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

A lean, well-structured overview body with executable quick-start commands and excellent progressive disclosure to a real, one-level-deep references file. The weakest area is workflow clarity: the setup sequence lacks any verification step confirming the project actually runs.

Suggestions

Add a verification step to Quick Start, e.g., "Run `npx expo start` and confirm the app loads on a simulator before adding features", to give the setup workflow a validation checkpoint.

Include one small concrete snippet or command for the headline capabilities (native modules, offline sync) in SKILL.md so the top-level file is actionable on its own, not just via references.

Trim or collapse the Expo-vs-Bare comparison table to the decision-relevant rows, since much of that comparison is knowledge Claude already has.

DimensionReasoningScore

Conciseness

The body is efficient — a directory tree, a compact comparison table, quick-start commands, one code sample, and terse Do's/Don'ts. Minor over-explanation remains (the Expo-vs-Bare RN table and its rationale bullets cover knowledge Claude largely already has), keeping it below anchor 5.

4 / 5

Actionability

Quick Start provides executable commands ("npx create-expo-app@latest my-app -t expo-template-blank-typescript", "npx expo install ...") and a complete root layout code sample. Gaps keep it at anchor 4: the project structure is a descriptive tree rather than commands, and headline topics like native module integration and offline sync are only named in the body, with the how-to deferred to references.

4 / 5

Workflow Clarity

Quick Start sequences create project → install dependencies → write root layout, but no verification checkpoint (e.g., "npx expo start" to confirm the app boots) is given, matching anchor 3's 'steps listed but checkpoints missing or implicit' rather than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The ~100-line SKILL.md is a genuine overview with one clearly signaled, one-level-deep reference ("Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient"). The referenced file exists and contains no nested references, matching anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

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

A strong description: concrete capability list paired with an explicit 'Use when' clause carrying natural trigger phrases. The only gaps are a few missing synonyms (iOS/Android, app development) and body topics not surfaced in the what-clause.

Suggestions

Add common user phrasings such as "iOS"/"Android" or "mobile app development" to the trigger clause for broader natural matching.

Mention one or two more of the body's actual capabilities (state management, performance optimization) so the what-clause's coverage is comprehensive.

DimensionReasoningScore

Specificity

"Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns" lists several concrete capability areas. It falls short of anchor 5's comprehensive coverage because body topics like state management, testing, and CI/CD releases are absent from the description.

4 / 5

Completeness

It explicitly answers "what" ("Build production React Native apps with Expo, navigation, native modules, offline sync...") and "when" with concrete trigger phrases ("Use when developing mobile apps, implementing native integrations, or architecting React Native projects"), matching the anchor-5 example pattern; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural terms like "React Native", "Expo", "mobile apps", and "native integrations" give good keyword coverage. A few natural variations users would say ("iOS", "Android", "app development") are missing, so it does not reach anchor 5's synonym/extension-level coverage.

4 / 5

Distinctiveness Conflict Risk

"React Native... with Expo" plus offline sync and native modules carves out a clear niche with distinct trigger terms; there is minimal overlap risk with generic mobile, web, or backend skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/frontend-mobile-development/skills/react-native-architecture/SKILL.md

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.