Labsco
Labsco/Repos/expo/expo
REPO PACKAGE

expo expo

OFFICIAL
expo · publisher50,451 repository starsMIT · Freegithub.com/expo/expo
3skills
1ready to use

None of the three touch what most people come to this repository for — the SDK, the CLI, or Expo Router as an app-building tool. android-e2e-testing drives an Android emulator over ADB to check Expo Router behavior after a native change. deep-code-review reads the surrounding codebase before judging a pull request and posts its findings back to GitHub. expo-api-docs turns Expo's own TSDoc conventions — the @platform, @example, and @deprecated annotations, third-person prose, and export patterns its documentation generator expects — into a skill that fires when someone adds a public API to an expo-* package.

This is for people contributing code to expo/expo itself, not for developers using Expo to ship a React Native app — those developers get nothing from any of the three. Two need something beyond a bare install: deep-code-review needs a GitHub token to post its review, and android-e2e-testing needs a working Android SDK and emulator on the machine that runs it. Only expo-api-docs runs with nothing else installed.

READ THE FULL ANALYSIS

Expo's own readme says nothing about any of this. The project readme describes the SDK, the CLI, EAS, and how to contribute code; it does not mention skills, an agent, or Claude anywhere. These three exist as ordinary files in the repository, and we found them by reading the repository directly, not because Expo has announced or documented them as a feature.

Who this is not for. If you came here because you build apps with Expo, none of the three skills below will help you — they review pull requests, drive an Android emulator, and enforce a documentation style, all scoped to this one repository's own contribution process.

1Work with nothing else to set up.
50,451Stars on the GitHub repository, at last check.