CtrlK
BlogDocsLog inGet started
Tessl Logo

react-native-architecture

Production-ready patterns for React Native development with Expo, including navigation, state management, native modules, and offline-first architecture.

34

Quality

30%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-mobile-developer/skills/react-native-architecture/SKILL.md

The canonical home for this skill is react-native-architecture in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

18%Scale 1-5

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

This skill is essentially a placeholder with no actionable content. It covers a broad and ambitious scope (navigation, state management, native modules, offline-first architecture, CI/CD) but provides zero concrete guidance, code examples, or specific patterns. All substance is deferred to a referenced file that doesn't exist in the bundle, leaving Claude with nothing useful to act on.

Suggestions

Add concrete, executable code examples for at least the core patterns mentioned (e.g., Expo Router navigation setup, offline-first with MMKV/WatermelonDB, EAS Build configuration).

Replace the generic instruction bullets ('Clarify goals', 'Apply best practices') with specific, actionable workflows for each use case, including validation steps.

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns directly in SKILL.md.

Narrow the scope or provide structured sections for each topic area (navigation, state management, native modules, offline-first) with at least a minimal working example for each.

DimensionReasoningScore

Conciseness

The content is relatively short but includes unnecessary sections like 'Do not use this skill when' with trivially obvious guidance ('unrelated to react native architecture'). The instructions section is generic boilerplate ('Clarify goals, constraints, and required inputs') rather than domain-specific content.

3 / 5

Actionability

The skill provides zero concrete code, commands, or specific technical guidance. Instructions like 'Apply relevant best practices and validate outcomes' are entirely vague. There are no executable examples, no specific patterns, no architecture decisions — everything is deferred to a referenced file that doesn't exist in the bundle.

1 / 5

Workflow Clarity

There is no meaningful workflow defined. The four bullet points in Instructions are generic platitudes ('Clarify goals', 'Apply best practices', 'Provide actionable steps') with no sequencing, no validation checkpoints, and no specificity to React Native development.

1 / 5

Progressive Disclosure

The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure in theory. However, the bundle has no files, meaning the reference is broken. The SKILL.md itself contains almost no substantive content — it's an empty shell pointing to a nonexistent resource, making the progressive disclosure structure non-functional.

2 / 5

Total

7

/

20

Passed

Description

41%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.

The description identifies its domain (React Native/Expo) and lists topic areas but reads more like a course syllabus than an actionable skill description. It lacks concrete actions (what it actually does), a 'Use when...' clause for trigger guidance, and natural user-facing keywords like 'mobile app' or 'iOS/Android'. The listed capabilities are categories rather than specific operations Claude would perform.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when building mobile apps with React Native, Expo, or when the user mentions iOS/Android app development, mobile navigation, or offline mobile storage'.

Replace category listings with concrete actions, e.g., 'Generates navigation stacks, configures state management with Redux/Zustand, sets up offline-first data persistence, and integrates native modules in Expo projects'.

Include natural synonyms and related terms users would say, such as 'mobile app', 'iOS', 'Android', 'app.json', 'eas build', 'React Navigation', or 'expo-router'.

DimensionReasoningScore

Specificity

Names the domain (React Native/Expo) and lists several areas (navigation, state management, native modules, offline-first architecture), but these are categories rather than concrete actions. It says 'patterns for' rather than describing what it actually does (e.g., 'generates navigation setup code', 'configures offline storage').

3 / 5

Completeness

Has a reasonable 'what' (production-ready patterns for React Native/Expo development) but completely lacks any 'when' clause or trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 3, and the 'what' is more of a topic listing than a clear capability statement, placing it at 2.

2 / 5

Trigger Term Quality

Includes relevant keywords like 'React Native', 'Expo', 'navigation', 'state management', 'native modules', and 'offline-first', but misses common user phrases and synonyms like 'mobile app', 'iOS', 'Android', 'app development', 'Redux', 'AsyncStorage', or file extensions like '.tsx'.

3 / 5

Distinctiveness Conflict Risk

The combination of 'React Native' and 'Expo' provides some specificity, but 'navigation', 'state management', and 'native modules' are broad enough to overlap with general React skills, mobile development skills, or framework-specific skills. The scope is wide within the React Native domain.

3 / 5

Total

11

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.