Skip to content
TrustedSkillsbeta
Back to all skills

Upgrading Expo

Checked
satsigner·vlatest·frontend·MIT

Automates Satsigner Expo account creation and upgrades, streamlining registration for event attendees.

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 satsigner/satsigner --skill upgrading-expo -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

satsigner

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 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 satsigner/satsigner at 02e9db0752.

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

Commit
02e9db0752
Manifest
.claude/skills/upgrading-expo/SKILL.md
Scanned
7 files, 697 lines
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, satsigner-upgrading-expo, appears to be designed for upgrading Expo projects. While specific details aren't provided, its purpose is likely focused on automating or simplifying the process of updating dependencies and configurations within an Expo application environment. It aims to streamline development workflows by handling complex upgrade procedures.

When to use it

  • When you need to update your Expo project to a newer version.
  • To automate repetitive tasks involved in upgrading dependencies.
  • For managing upgrades across multiple Expo projects.
  • When encountering issues during manual Expo upgrades.

Key capabilities

  • Expo Project Upgrades
  • Dependency Management (implied)
  • Configuration Updates (implied)

Example prompts

  • "Upgrade my Expo project to the latest version."
  • "Run an upgrade check on my current Expo setup."
  • "Automate the process of updating all dependencies in my Expo project."

Tips & gotchas

The skill's effectiveness likely depends on a clean and well-structured Expo project. Consult the skill’s documentation (if available) for specific prerequisites or potential compatibility issues with older Expo versions.