upgrading-react-native
Upgrades React Native apps to newer versions by applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. Use when upgrading React Native, bumping RN version, updating from RN 0.x to 0.y, or migrating Expo SDK alongside a React Native upgrade.
79
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 an excellent skill description that clearly defines a specific niche (React Native version upgrades), lists concrete actions performed, and includes an explicit 'Use when...' clause with natural trigger terms covering common variations of how users would request this task. It uses proper third-person voice throughout and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. | 3 / 3 |
Completeness | Clearly answers both what (applying diffs, updating dependencies, migrating native config, resolving CocoaPods/Gradle, handling breaking APIs) and when (explicit 'Use when...' clause with multiple trigger scenarios including version bumping and Expo SDK migration). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'upgrading React Native', 'bumping RN version', 'updating from RN 0.x to 0.y', 'migrating Expo SDK', 'React Native upgrade', 'CocoaPods', 'Gradle'. These are terms developers naturally use when discussing RN upgrades. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: React Native version upgrades specifically. The mention of rn-diff-purge, CocoaPods, Gradle, and Expo SDK migration makes it very unlikely to conflict with general React, mobile development, or dependency management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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 serves effectively as an orchestration hub for a complex multi-step process. It provides executable commands in the quick start, clear workflow sequencing, and excellent progressive disclosure through well-organized reference links. The content is concise, assumes Claude's competence, and every section earns its place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what React Native is or how upgrades work conceptually. Every section serves a clear purpose: routing to the right sub-skill, providing executable commands, or mapping problems to solutions. The tables are compact and informative. | 3 / 3 |
Actionability | The quick start block provides fully executable, copy-paste-ready commands for detecting the current version, fetching the diff, reviewing changes, installing dependencies, running pod install, and validating builds on both platforms. The numbered upgrade sequence gives concrete steps with clear references for each. | 3 / 3 |
Workflow Clarity | The typical upgrade sequence is clearly numbered with logical ordering (route → diff → dependencies → React → Expo → verify). The quick start includes explicit validation steps (both platforms must build successfully) with concrete build commands. The problem-to-skill mapping table provides clear routing for different scenarios. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: the SKILL.md serves as a concise overview and router, with all detailed content delegated to clearly-signaled, one-level-deep reference files. The quick reference table and problem→skill mapping table make navigation easy. All link references are consistently defined at the bottom. | 3 / 3 |
Total | 12 / 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
a5c8f21
- 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.