CtrlK
BlogDocsLog inGet started
Tessl Logo

react-native-brownfield-migration

Provides an incremental adoption strategy to migrate native iOS or Android apps to React Native or Expo using @callstack/react-native-brownfield for initial setup. Use when planning migration steps, packaging XCFramework/AAR artifacts, and integrating them into host apps.

65

Quality

78%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/react-native-brownfield-migration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

This skill excels as a routing/overview document with strong progressive disclosure and clear navigation to reference files. However, it lacks concrete executable guidance in the main file itself — no CLI commands, code snippets, or specific validation steps are provided. The content has some redundancy between the Quick Reference table, Problem->Skill Mapping table, and When to Apply section that could be consolidated.

Suggestions

Add at least one concrete CLI command example in the Migration Strategy section (e.g., the initial `npx react-native-brownfield` setup command) to improve actionability.

Add explicit validation/verification steps to the migration strategy workflow, such as specific commands to verify packaging output before proceeding to host integration.

Consolidate the 'When to Apply' section into the overview or remove it, as it largely duplicates information already conveyed by the Problem->Skill Mapping table.

DimensionReasoningScore

Conciseness

The content is mostly efficient but has some redundancy — the 'When to Apply' section largely restates what's already clear from the overview and problem mapping table. The Quick Reference and Problem->Skill Mapping tables overlap significantly. However, it avoids explaining basic concepts Claude already knows.

2 / 3

Actionability

The skill provides a clear decision framework and references to detailed files, but the SKILL.md itself contains no executable code, commands, or concrete examples. The migration strategy is described at a high level without specific CLI commands or code snippets. The actual actionable content is deferred entirely to reference files which are not provided.

2 / 3

Workflow Clarity

The 5-step migration strategy provides a reasonable sequence, and the Path Selection Gate adds a decision checkpoint. However, there are no explicit validation steps between stages (e.g., how to verify packaging succeeded before host integration), and step 3 says 'Validate each packaging command' in guardrails but doesn't specify how. Missing feedback loops for these potentially destructive/complex operations caps this at 2.

2 / 3

Progressive Disclosure

Excellent progressive disclosure structure: the SKILL.md serves as a clear overview and routing document with well-organized tables mapping problems to specific reference files. All references are one level deep, clearly signaled with both a Quick Reference table and a Problem->Skill Mapping table. Navigation is intuitive and well-structured.

3 / 3

Total

9

/

12

Passed

Description

100%

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 is a well-crafted skill description that clearly defines a specific niche (brownfield React Native migration), lists concrete actions and artifacts, and includes an explicit 'Use when' clause with relevant trigger terms. The description is concise yet comprehensive, covering the what, when, and how with domain-specific terminology that developers would naturally use.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: incremental adoption strategy, migrating native iOS/Android apps to React Native/Expo, using @callstack/react-native-brownfield for initial setup, packaging XCFramework/AAR artifacts, and integrating into host apps.

3 / 3

Completeness

Clearly answers both what ('provides an incremental adoption strategy to migrate native iOS or Android apps to React Native or Expo using @callstack/react-native-brownfield') and when ('Use when planning migration steps, packaging XCFramework/AAR artifacts, and integrating them into host apps').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'migrate', 'iOS', 'Android', 'React Native', 'Expo', 'brownfield', 'XCFramework', 'AAR', 'host apps'. These cover both platform-specific and framework-specific terms a developer would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche combining brownfield migration, specific library (@callstack/react-native-brownfield), specific artifact types (XCFramework/AAR), and specific platforms (iOS/Android to React Native/Expo). Very unlikely to conflict with other skills.

3 / 3

Total

12

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

10

/

11

Passed

Repository
callstackincubator/agent-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.