What problem does it solve? Expo users and AI agents lack a direct channel to report what worked, what broke, or where documentation and tooling fell short, and they need transparent control over whether anonymous usage telemetry is collected. ## Core Features & Use Cases - Actionable Feedback Submission: Send categorized feedback about Expo skills, docs, MCP tools, Expo CLI, or EAS CLI via the submit-expo-feedback CLI with optional category and subject flags. - Eval Candidate Reporting: Report real-world Expo tasks that an AI agent repeatedly failed at, using a structured Task/Expected/Actual/Wrong approach/Evidence format, with user approval required before submission. - Telemetry Control: Check, enable, or disable anonymous PostHog usage telemetry, which is off by default and only activates through explicit opt-in via script or environment variable. - Use Case: After an AI agent fails three times to configure an expo-router deep link and you fix it manually, use this Skill to submit the failure as an eval candidate so Expo can turn it into a regression test. ## Quick Start Ask the assistant to submit feedback that the expo-router skill was missing deep-linking context, or to check the current Expo skills telemetry status.
