assess-react-native-migration

Assesses whether and how an existing mobile product should migrate to React Native. Use when auditing one or more product repositories for migration readiness, including products whose iOS, Android, and other clients live in separate directories or repositories; choosing brownfield, greenfield, or a checkpoint-based path; defining a representative trial; or preparing a baseline and ROI decision before implementation. When product scope or material evidence is unavailable, grills the stakeholder with exactly one question per turn instead of sending a questionnaire.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

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

The body is a tightly-structured, read-only assessment workflow with explicit gates and concrete decision tables rather than verbose concept explanation. It is highly actionable and well-sequenced; the only slack is mild repetition of the gate format and no use of separate reference files for the larger evidence tables.

Suggestions

Consolidate the repeated two-line '**Question:** / **Why it matters:**' template into a single canonical definition to reduce restatement across the First Response Gate and Evidence Mode sections.

Consider moving the eight-row evidence dimension table and the path-selection table into a reference file (e.g. references/EVIDENCE.md) referenced one level deep, keeping SKILL.md as a lean overview.

Add a brief example of the expected citation format ('repository name + file path + line number') so the evidence-citing instruction is unambiguously executable.

Dimension	Reasoning	Score
Conciseness	Dense directive prose that assumes Claude's competence and avoids explaining React Native basics, but the two-line question-gate format is restated in several places and a few prose rules could be tightened without losing clarity.	4 / 5
Actionability	Provides exact output templates (the markdown question blocks), decision tables with explicit 'Recommend when' criteria, named artifacts (MIGRATION.md, SCREENS.tsv, STATE_AND_STORAGE.tsv, etc.), and concrete acceptance criteria — fully actionable for an instruction-only assessment skill.	5 / 5
Workflow Clarity	Clear end-to-end sequence (scope → evidence mode → collect evidence → choose path → checkpoint → economics → output) with explicit validation gates (Scope gate, First Response Gate, Interview turn gate, and per-section gates) and feedback loops (challenge vague answers, re-ask highest-impact unknown).	5 / 5
Progressive Disclosure	Well-organized with clear section headers and one clearly-signaled one-level cross-skill reference to react-native-brownfield-migration; no bundle files exist, and the inline decision/evidence tables are core rather than reference material, leaving only minor organization room.	4 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and uses third-person voice with an explicit 'Use when' clause covering concrete trigger scenarios. Trigger-term coverage is strong but could add a few more natural synonyms to reach full marks.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('auditing one or more product repositories for migration readiness', 'choosing brownfield, greenfield, or a checkpoint-based path', 'defining a representative trial', 'preparing a baseline and ROI decision', 'grills the stakeholder with exactly one question per turn') — comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Clearly answers 'what' ('Assesses whether and how an existing mobile product should migrate to React Native') and 'when' via an explicit 'Use when...' clause enumerating concrete trigger scenarios.	5 / 5
Trigger Term Quality	Good natural-term coverage ('migrate to React Native', 'migration readiness', 'iOS, Android', 'brownfield, greenfield', 'ROI decision') with a few natural synonyms missing such as 'port to React Native' or 'cross-platform'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (React Native migration assessment decision phase) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: callstackincubator/agent-skills
Path: skills/assess-react-native-migration/SKILL.md
Commit: 61e6e7d

Reviewed: 5 days 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.