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.

Quality

78%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/react-native-brownfield-migration/SKILL.md

Quality

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 narrow, specific domain (brownfield migration of native mobile apps to React Native/Expo), lists concrete actions, and includes an explicit 'Use when' clause with relevant trigger scenarios. The technical terms used are appropriate and match what developers would naturally say when seeking this kind of help.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'incremental adoption strategy', 'migrate native iOS or Android apps to React Native or Expo', 'packaging XCFramework/AAR artifacts', 'integrating them into host apps', and references a specific library '@callstack/react-native-brownfield'.	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', 'migration steps'. These cover the domain well and match how developers would phrase such requests.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche: brownfield React Native migration with specific library reference and specific artifact types (XCFramework/AAR). Very unlikely to conflict with other skills due to the narrow, well-defined domain.	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 is a well-structured navigation/orchestration skill that excels at progressive disclosure and organizing a complex multi-path migration workflow. Its main weaknesses are the lack of concrete executable examples in the body itself (all deferred to references) and insufficient validation/feedback loop detail in the workflow steps. Some content redundancy between the 'When to Apply', Quick Reference, and Problem->Skill Mapping sections could be trimmed.

Suggestions

Add at least one concrete executable command example in the Migration Strategy section (e.g., the initial brownfield setup command) to improve actionability.

Integrate explicit validation checkpoints with specific commands into the Migration Strategy workflow (e.g., 'Run `npx react-native-brownfield verify` to confirm packaging succeeded 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.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and avoids explaining basic concepts, but there's some redundancy between sections (e.g., 'When to Apply' largely restates what's already clear from the overview and problem mapping table; the Quick Reference and Problem->Skill Mapping tables overlap significantly).	2 / 3
Actionability	The skill provides a clear decision tree and migration strategy steps, but lacks any concrete executable code or commands. All actual implementation is deferred to reference files. The path selection gate is actionable as a decision process, but there are no copy-paste-ready commands or code snippets in the main skill body.	2 / 3
Workflow Clarity	The migration strategy outlines a 5-step sequence and the path selection gate provides a clear decision flow. However, validation checkpoints are weak — step 3 says 'validate each packaging command' as a guardrail but doesn't specify how to validate. Step 4 mentions 'validate startup/runtime' but the actual verification process (using agent-device) is buried in guardrails rather than integrated into the workflow with explicit feedback loops.	2 / 3
Progressive Disclosure	Excellent structure with a concise overview pointing to well-organized reference files via two complementary navigation aids (Quick Reference table and Problem->Skill Mapping table). All references are one level deep with clear link definitions. The content is appropriately split between the overview skill and detailed reference files.	3 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: a5c8f21

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.