Expo Upgrade

What it does

This skill organizes an SDK upgrade as a set of linked application changes rather than a single package-version edit. It references framework transitions, native architecture and deprecated packages, and includes cleanup and configuration considerations. Its value is in identifying which application boundaries need inspection before an upgrade is called successful.

Best for

A planned Expo SDK migration or an application that stopped building after dependency updates. Establish the current versions, target version and platform requirements, then identify custom native code and existing patches.

Tradeoffs and requirements

Upgrade advice is especially sensitive to release dates and known regressions. A pinned source snapshot is evidence of what was reviewed, not proof that its target version remains the best choice later. Native generation steps may replace manually maintained files, so changes need a reviewable backup and diff.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/expo/skills/tree/05754e71d02abe0d2d7a2fb5259ccac41f5ea59c/plugins/expo/skills/expo-upgrade --skill expo-upgrade

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Destructive Command — review the source context.
• Network Access — review the source context.
• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

81/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

64/100

64

Originality

80/100

80

Static Safety

35/100

35

Suggested workflow

Create a reproducible baseline, review the relevant version-specific changes, update compatible dependencies and inspect generated native changes. Run the same important user journeys before and after the migration.

How to judge the result

Check fresh installation, native builds, startup memory, navigation and any affected media or animation paths. Confirm production behavior on real target devices where a simulator or build result is insufficient.