CtrlK
BlogDocsLog inGet started
Tessl Logo

react-native-brownfield-migration

Implements an accepted incremental brownfield migration from native iOS or Android to React Native or Expo using @callstack/react-native-brownfield. Use after the brownfield path has been selected, when setting up the integration, packaging XCFramework or AAR artifacts, or adding React Native surfaces to native hosts.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

A well-structured router skill with strong progressive disclosure and a clear, validated multi-step workflow. It loses points only on token efficiency (two overlapping file tables) and actionability (executable detail deferred to references).

Suggestions

Collapse the 'Quick Reference' and 'Problem -> Skill Mapping' tables into a single table (or keep one as a navigation table and fold problem-to-file guidance into a short bulleted list) to remove the duplicated enumeration of the 10 reference files.

Either trim 'When to Apply' to only items not already in the frontmatter description, or drop the section and rely on the description's triggers to avoid restating the same when-clauses.

Add at least one concrete, executable packaging or integration command (e.g. the brownfield CLI invocation) inline in the body so the highest-traffic step is actionable without opening a reference file.

DimensionReasoningScore

Conciseness

Mostly efficient with no concept over-explanation, but the 'Quick Reference' and 'Problem -> Skill Mapping' tables both enumerate the same 10 reference files, and 'When to Apply' repeats the frontmatter description — duplicative tokens that could be tightened.

2 / 3

Actionability

Concrete guidance exists (path-gate criteria from package.json/app.json, placeholder resolution, 'validate each packaging command'), but the body is a router and executable code/commands are deferred to reference files rather than being copy-paste ready here.

2 / 3

Workflow Clarity

The 5-step Migration Strategy is clearly sequenced, with a 'Must Run First' Path Selection Gate and explicit validation checkpoints ('Validate each packaging command before moving to host integration', agent-device startup/runtime verification).

3 / 3

Progressive Disclosure

A concise overview routes to 10 well-named, one-level-deep reference files that all exist on disk, organized through both a Quick Reference table and canonical-doc links for easy navigation.

3 / 3

Total

10

/

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.

A precise, well-scoped description that states concrete capabilities and an explicit 'Use when...' trigger tied to a specific library and artifact types. It clearly distinguishes itself from sibling skills and is unlikely to conflict.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'setting up the integration', 'packaging XCFramework or AAR artifacts', 'adding React Native surfaces to native hosts' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Implements an accepted incremental brownfield migration...using @callstack/react-native-brownfield') and when ('Use after the brownfield path has been selected, when setting up the integration...').

3 / 3

Trigger Term Quality

Covers the natural terms a developer would say for this need — 'brownfield migration', 'native iOS or Android', 'React Native or Expo', 'XCFramework', 'AAR', 'React Native surfaces'.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and tool-anchored (@callstack/react-native-brownfield, XCFramework/AAR packaging), with triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

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.