Skip to content
TrustedSkillsbeta
Back to all skills

Expo Dev Client

Official
expo·vlatest·frontend·MIT

Official expo skill covering Expo, client-side for building frontend UIs and user experiences.

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 expo/skills --skill expo-dev-client -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

expo

Matched to the vendor's own GitHub organisation.

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 expo/skills at d4f484024f.

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

Scanned
2 files, 162 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

The expo-dev-client skill allows developers to run and debug Expo apps directly on a device without needing to install the app from the App Store or Google Play. It provides tools for live reloading, debugging, and inspecting the app's performance in real time.

When to use it

  • When testing an Expo app on a physical device during development.
  • When you need to debug JavaScript errors or inspect the app’s runtime behavior.
  • When using features like hot reload or remote debugging without packaging the app for distribution.

Key capabilities

  • Live reloading of code changes in real time.
  • Debugging with Chrome DevTools via a WebSocket connection.
  • Running apps directly on iOS and Android devices without building a production APK or IPA.
  • Support for Metro bundler integration.

Example prompts

  • "Run the Expo app on my phone using expo-dev-client."
  • "Enable live reload for my Expo project with expo-dev-client."
  • "Debug JavaScript errors in my Expo app using the dev client."

Tips & gotchas

  • Ensure your device is connected to the same Wi-Fi network as your development machine.
  • The expo-dev-client requires a Metro bundler instance running on your local machine.