Skip to content
TrustedSkillsbeta
Back to all skills

Upgrading Expo

Listed
jstarfilms·vlatest·frontend·ISC

Automatically optimizes expo website assets (images, bundles) for faster loading and improved user experience.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add j-star-films-studios/vibecode-protocol-suite --skill upgrading-expo --full-depth -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jstarfilms

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 jstarfilms/vibecode-protocol-suite at 18e133d0e8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
18e133d0e8
Manifest
assets/.agent/skills/web-dev-standards/upgrading-expo/SKILL.md
Scanned
0 files
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates the process of upgrading Expo projects. It handles dependency updates, configuration adjustments, and potential migration steps required for successful upgrades to newer versions of Expo SDKs. This ensures a smoother upgrade experience with reduced manual effort and fewer errors.

When to use it

  • You need to update your Expo project to a newer SDK version to access new features or address security vulnerabilities.
  • You're experiencing compatibility issues due to outdated dependencies in your Expo project.
  • You want to streamline the upgrade process, minimizing potential downtime and manual configuration changes.
  • Your team wants to standardize Expo upgrades across multiple projects.

Key capabilities

  • Automated dependency updates
  • Configuration adjustments for newer SDK versions
  • Migration assistance for breaking changes

Example prompts

  • "Upgrade my Expo project to the latest stable version."
  • "Update my Expo project's dependencies to be compatible with Expo SDK 49."
  • “Run an upgrade check and report any potential issues before I proceed.”

Tips & gotchas

This skill assumes you have a valid Expo project. It’s recommended to back up your project before running the upgrade process, as unexpected issues can sometimes arise during major version upgrades.