expo-skill-feedback
Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest "ACTIONABLE_FEEDBACK". Optionally add either or both: --category "CATEGORY" and --subject "SUBJECT". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; or when the user explicitly asks to enable or disable telemetry, check its status, or understand what it collects.
- License 许可
- MIT
- 最近更新
- 2026-08-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- expo-skill-feedback
- description
- Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest "ACTIONABLE_FEEDBACK". Optionally add either or both: --category "CATEGORY" and --subject "SUBJECT". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; or when the user explicitly asks to enable or disable telemetry, check its status, or understand what it collects.
02 资源文件 4
- 参考文档agents/openai.yaml251 B
- 脚本scripts/skill-event.cjs7.9 KB
- 脚本scripts/telemetry_common.cjs7.0 KB
- 脚本scripts/telemetry.cjs3.0 KB
03 SKILL.md 正文
Expo Skill Feedback
Help Expo improve by sharing specific feedback about what worked well or what fell short. Feedback submission is independent of usage telemetry and does not require enabling it.
Submit feedback
npx --yes submit-expo-feedback@latest "<ACTIONABLE_FEEDBACK>"
Add either optional flag independently when it provides useful context:
npx --yes submit-expo-feedback@latest --category "<CATEGORY>" --subject "<SUBJECT>" "<ACTIONABLE_FEEDBACK>"
--category defaults to unknown, and --subject may be omitted when there is no specific target.
When including them, choose the values that most precisely identify what the feedback is about:
| Category | Subject |
|---|---|
skills |
Exact skill name from its frontmatter, such as expo-router |
docs |
Full Expo documentation URL |
mcp |
Exact MCP tool name used |
expo-cli |
Full Expo CLI command, such as npx expo install |
eas-cli |
Full EAS CLI command, such as eas build |
unknown |
Concise Expo product, package, feature, or other topic |
In the final argument, say what helped and why, or provide the relevant context, expected behavior, and what happened instead. Do not include secrets, source code, personal data, long prompts, or stack traces.
Usage telemetry
Automatic skill usage telemetry is separate from feedback and off by default. Never enable it
without an explicit user request. Use the following script with --on, --off, or --status:
node "${CLAUDE_PLUGIN_ROOT}/skills/expo-skill-feedback/scripts/telemetry.cjs" --status
Environment equivalents are EXPO_SKILLS_TELEMETRY=1 to enable and
EXPO_SKILLS_TELEMETRY=0 or DO_NOT_TRACK=1 to disable. CI never sends telemetry.
Submitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
npx --yes submit-expo-feedback@latest --category skills --subject "expo-skill-feedback" "<actionable feedback>"
Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
04 同仓库更多 Skills
expo-web-to-native
Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage, window) map to native. This is the end-to-end migration guide; use the `expo-dom` skill for the DOM-component mechanism itself.
expo-upgrade
Framework (OSS). Guidelines for upgrading Expo SDK versions and fixing dependency issues
expo-ui
Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android rendered from React in an Expo or React Native app. Covers universal cross-platform components (Host, Column, Row, Button, Text, List, and more imported from @expo/ui), drop-in replacements for popular React Native community libraries (BottomSheet, DateTimePicker, Slider, Menu, etc.), and platform-specific SwiftUI (@expo/ui/swift-ui, iOS only) and Jetpack Compose (@expo/ui/jetpack-compose, Android only) trees and modifiers. Use when adding or reviewing @expo/ui Host/RNHostView trees, building native-feeling UI where standard React Native components fall short (grouped settings forms with toggles, sections, menus, sheets, pickers, sliders), choosing between universal and platform-specific components, or replacing an RN community UI library with a native @expo/ui equivalent. Not for custom native modules, Expo Router navigation, Reanimated, or data fetching.
expo-tailwind-setup
Framework (OSS). Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
expo-skill-eval
Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional). Use when the user wants to eval an Expo skill, test that a skill produces working code, benchmark a skill with device screenshots, or verify a skill's output renders correctly.
expo-router
Framework (OSS). Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder organization, Link with previews and context menus, native Stack, page titles, modals and form sheets, NativeTabs, headers and toolbars, and header search bars.