Upgrading Expo
CheckedAutomates Expo website upgrades on SLC frontend deployments, ensuring consistent branding and feature parity across platforms.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add gigs-slc/react-native-skills --skill upgrading-expo -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
gigs-slc
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned gigs-slc/react-native-skills at becef4d0f9.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- becef4d0f9
- Manifest
- skills/upgrading-expo/SKILL.md
- Scanned
- 4 files, 298 lines
About this skill
What it does
This skill facilitates upgrading Expo projects. It automates tasks associated with updating Expo SDK versions, resolving potential compatibility issues, and ensuring a smooth transition to newer releases. This includes handling dependency updates and addressing breaking changes that might arise during the upgrade process.
When to use it
- You need to update your Expo project's SDK version to benefit from new features or bug fixes.
- Your project is experiencing compatibility issues due to an outdated Expo SDK.
- You want to streamline the upgrade process and minimize manual intervention.
- You are migrating a React Native project to use Expo.
Key capabilities
- Automated Expo SDK version updates
- Dependency resolution during upgrades
- Handling of breaking changes introduced in new versions
- Migration from other React Native projects
Example prompts
- "Upgrade my Expo project to the latest stable SDK."
- "What are the potential breaking changes when upgrading to Expo SDK 49?"
- “Migrate this existing React Native project to use Expo.”
Tips & gotchas
This skill assumes a working Expo project. It’s recommended to back up your project before initiating an upgrade, as unexpected issues can sometimes occur during the process.