Expo Devtools Cli
CheckedAutomates common Expo development tasks like building, publishing, and managing projects using the CLI.
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 evanbacon/apple-health --skill expo-devtools-cli -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
evanbacon
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 evanbacon/apple-health at 97ccf797f8.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 97ccf797f8
- Scanned
- 1 file, 442 lines
About this skill
What it does
This skill provides access to the Expo DevTools CLI, allowing you to debug and inspect your Expo managed JavaScript projects. It enables features like remote debugging of JavaScript code running on connected devices or simulators, as well as inspecting network requests and performance metrics. This is particularly useful for frontend developers working with React Native applications built using Expo.
When to use it
- Debugging a mobile app: You're experiencing unexpected behavior in your Expo-managed React Native application and need to step through the code on a device or simulator.
- Analyzing network requests: You want to inspect the HTTP requests made by your app to understand data flow and troubleshoot API issues.
- Performance profiling: You suspect performance bottlenecks in your app and require tools to measure frame rates, memory usage, and other key metrics.
Key capabilities
- Remote JavaScript debugging
- Network inspection
- Performance monitoring
Example prompts
- "Start the Expo DevTools CLI."
- "Debug my React Native application on my connected device."
- "Show me the network requests made by my app."
Tips & gotchas
- Ensure you have an Expo-managed project set up before using this skill.
- A compatible development environment (e.g., Node.js, npm/yarn) is required to run the CLI commands.