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
Security Assessment
About expo-skill-feedback
expo-skill-feedback is a utility skill for Expo's open-source skill collection that lets users submit feedback about an Expo skill — or about Expo itself — and control the bundled anonymous usage telemetry. It solves two related problems: capturing concrete, actionable feedback when a skill is useful, confusing, broken, or missing context, and giving users explicit, informed control over whether any usage data is sent at all.
Feedback is submitted by running a bundled Node.js script with a rating (useful, confusing, bug, idea, or other), a short text note, and the name of the skill being rated, with an --about flag to distinguish issues with a skill from issues with Expo itself and a --dry-run flag to preview the payload. Feedback is delivered to the Expo team via PostHog. Telemetry is off by default and strictly opt-in: nothing — neither feedback nor the automatic skill_invoked event — is sent until the user explicitly enables it, and the skill is instructed never to enable it on its own. A dedicated script toggles telemetry on, off, or reports status, with environment-variable and CI overrides (including honoring DO_NOT_TRACK), and CI never sends. The documentation is explicit that only the skill name, rating, note, platform, and a hash of a random local install id are transmitted — never code, prompts, file paths, secrets, or personal data.
The skill targets developers using Expo skills who want to report their experience and administrators who care about data-collection transparency. Its privacy-forward, opt-in, no-exfiltration design is exemplary; the only external transmission is anonymous, minimal, consent-gated feedback to the project's own analytics.
FAQ
Is telemetry on by default?
No. It is off by default and opt-in — nothing is sent until the user explicitly enables it, and the skill is told never to enable it on its own.
What data gets sent?
Only the skill name, your rating and note, the platform, and a hash of a random local install id — never code, prompts, file paths, secrets, or personal data.
How do I submit feedback?
Run the bundled skill-feedback Node script with a --rating, --text note, and the --skill being rated; --dry-run previews the payload without sending.
Can I turn tracking off or check its status?
Yes. The telemetry script supports --on, --off, and --status; environment variables (including DO_NOT_TRACK=1) and CI can also override the saved state, and CI never sends.
Where does the feedback go?
To the Expo team via PostHog, the project's own analytics service.
Install expo-skill-feedback
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
expo/skills