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.
Install with Tessl CLI
npx tessl i github:callstackincubator/agent-skills --skill react-native-brownfield-migration87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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, well-crafted skill description that clearly defines a specific niche (brownfield React Native migration) with concrete actions and explicit trigger conditions. The main weakness is that trigger terms lean heavily technical, which may miss users who describe their needs in more casual language like 'add React Native to my existing app' or 'hybrid mobile development'.
Suggestions
Add more natural language trigger terms like 'convert existing app', 'add React Native to native app', 'hybrid mobile app', or 'brownfield migration' to capture users who may not use technical artifact names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'incremental adoption strategy', 'migrate native iOS or Android apps', 'packaging XCFramework/AAR artifacts', 'integrating them into host apps'. Names specific technologies and artifact types. | 3 / 3 |
Completeness | Clearly answers both what (provides incremental adoption strategy for migrating native apps to React Native/Expo) and when ('Use when planning migration steps, packaging XCFramework/AAR artifacts, and integrating them into host apps'). Has explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'React Native', 'Expo', 'iOS', 'Android', 'XCFramework', 'AAR', but these are fairly technical. Missing more natural user phrases like 'convert app', 'brownfield migration', 'hybrid app', or 'add React Native to existing app'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: specifically targets brownfield React Native migration with @callstack/react-native-brownfield library. The combination of native-to-RN migration, specific artifact types (XCFramework/AAR), and the named library creates clear differentiation from general React Native or mobile development skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that excels at organization and progressive disclosure, providing clear navigation through a complex brownfield migration workflow. The main weakness is the lack of concrete, executable code examples in the main file—the actionability relies heavily on the referenced files rather than providing immediate copy-paste guidance. The guardrails and path selection gate demonstrate good workflow design.
Suggestions
Add at least one concrete CLI command example in the Migration Strategy section (e.g., the actual brownfield CLI command for initial setup)
Include a minimal executable code snippet showing the basic integration pattern, even if detailed examples are in reference files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of concepts Claude would already know. Every section serves a clear purpose with no padding or verbose descriptions of what React Native or brownfield migration is. | 3 / 3 |
Actionability | The skill provides clear workflow steps and decision trees, but lacks concrete executable code examples. The migration strategy is procedural but abstract—no actual CLI commands, code snippets, or copy-paste ready examples are included in the main file. | 2 / 3 |
Workflow Clarity | The multi-step migration process is clearly sequenced with a mandatory path selection gate, explicit validation step ('Validate each packaging command before moving to host integration'), and incremental rollout strategy. The workflow includes decision points and error prevention through the guardrails section. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview pointing to 10 well-organized reference files. The Quick Reference table and Problem->Skill Mapping provide clear one-level-deep navigation. Content is appropriately split between the overview and detailed reference files. | 3 / 3 |
Total | 11 / 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 | |
- 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.