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.
85
78%
Does it follow best practices?
Impact
98%
2.88xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/react-native-brownfield-migration/SKILL.mdQuality
Discovery
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 strong skill description that clearly defines a specific niche (brownfield migration of native mobile apps to React Native/Expo), names concrete actions and artifacts, and includes an explicit 'Use when' clause with relevant trigger scenarios. The description is concise, uses third-person voice, and contains highly distinctive terminology that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: incremental adoption strategy, migrate native iOS/Android apps to React Native/Expo, packaging XCFramework/AAR artifacts, integrating into host apps, and using @callstack/react-native-brownfield for initial setup. | 3 / 3 |
Completeness | Clearly answers both 'what' (provides incremental adoption strategy to migrate native apps to React Native/Expo using brownfield library) and 'when' (explicit 'Use when' clause covering planning migration steps, packaging artifacts, and integrating 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 high-level intent terms ('migration') and specific technical terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: specifically targets brownfield migration from native iOS/Android to React Native/Expo using a named library (@callstack/react-native-brownfield), with specific artifact types (XCFramework/AAR). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 at progressive disclosure and navigation, serving as an effective routing document to detailed reference files. However, it lacks concrete executable examples in the main file and has validation gaps in its workflow steps. There is also some redundancy between the 'When to Apply', 'Quick Reference', and 'Problem -> Skill Mapping' sections.
Suggestions
Add at least one concrete executable command example (e.g., the brownfield CLI init command or a packaging command) to make the SKILL.md itself actionable rather than purely navigational.
Specify explicit validation steps in the Migration Strategy — e.g., 'Run `npx react-native-brownfield doctor` to verify setup' or describe what successful artifact generation output looks like.
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.
| Dimension | Reasoning | Score |
|---|---|---|
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 tree (Path Selection Gate) and structured migration steps, but lacks any concrete executable commands or code examples. All actual implementation details are deferred to reference files, so the SKILL.md itself gives directional guidance rather than copy-paste-ready instructions. | 2 / 3 |
Workflow Clarity | The migration strategy outlines a 5-step sequence and the path selection gate provides a decision flow, but validation checkpoints are vague ('validate startup/runtime', 'validate each packaging command') without specifying how to validate or what success looks like. For a multi-step process involving artifact generation and integration, explicit validation steps and error recovery loops are missing. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure — the SKILL.md serves as a clear overview/router with well-organized tables mapping problems to specific reference files. References are one level deep, clearly signaled with both a quick reference table and a problem-to-skill mapping table, making navigation straightforward. | 3 / 3 |
Total | 9 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- callstackincubator/agent-skills
- Commit
ace14e4
- 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.