expo-skill-eval

Evaluates Expo skills for trigger accuracy, code quality, and runtime rendering on iOS and Android.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/bmiit145/leadBee --skill expo-skill-eval-bmiit145
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-skill-eval
Source: https://github.com/bmiit145/leadBee/tree/main/mobile/.agents/skills/expo-skill-eval
Command: npx skills add https://github.com/bmiit145/leadBee --skill expo-skill-eval-bmiit145

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? It verifies whether an Expo skill actually works end-to-end: whether its description triggers it on realistic prompts, whether the code it generates compiles and lints, and whether the resulting app renders correctly on real simulators and emulators. ## Core Features & Use Cases - Trigger accuracy testing: Runs realistic prompts through claude -p subprocesses and measures recall of the skill under test. - With-skill vs without-skill comparison: Generates apps in fresh Expo fixtures with and without the skill, then grades both against expectations. - Runtime screenshots: Runs generated apps in Expo Go or a development build on iOS simulator, Android emulator, or web, and captures screenshots for visual grading against a design rubric or a target reference screenshot. - Use Case: After editing the expo-ui skill's description, run an eval to confirm it still triggers on UI prompts and that the screens it generates render without error overlays on both platforms. ## Quick Start Ask the agent to eval the expo-ui skill with runtime screenshots on iOS and Android using the latest Expo SDK.

Frequently Asked Questions about expo-skill-eval

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate an Expo skill end-to-end?▼

Run the expo-skill-eval harness, which builds a fresh Expo fixture per prompt, executes the prompt with and without the skill via claude -p subprocesses, runs a static gate, and captures runtime screenshots. Results are graded and rendered in a self-contained HTML viewer.

How do I test whether a skill's description triggers correctly?▼

Use the trigger accuracy phase, which runs realistic should-trigger prompts through claude -p with --plugin-dir pointing at the local plugin and watches for the skill's tool call in the output stream. It measures recall only, and the published expo plugin must be disabled first to avoid collisions.

Can I evaluate a skill that needs custom native code?▼

Yes, choose the development build runner, which uses expo run:ios or expo run:android to compile a native dev client per fixture instead of Expo Go. It is much slower and disk-heavy, so prefer fewer eval cases and a single platform.

Does the eval support web as a platform?▼

Yes, web runs via snapshot-web.sh using expo start --web with Playwright and Chromium, regardless of the chosen runner. Universal @expo/ui components render on web, while platform-specific SwiftUI or Compose trees render blank there.

Why do snapshot runs fail when pinning an older Expo SDK?▼

An SDK older than the device's installed Expo Go makes expo start prompt to install a matching Expo Go, which fails in non-interactive mode and fails every snapshot. Stick with the latest SDK or pre-install a matching Expo Go on the simulator or emulator.

What are the system requirements for running the eval harness?▼

The harness requires macOS with Xcode for iOS simulators, an Android SDK with at least one AVD, and bun. No other device tooling is assumed, and fixtures are cached under ~/.cache/expo-skill-eval for fast reuse.