expo-skill-feedback

Submit feedback on Expo skills and control opt-in anonymous usage telemetry.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill expo-skill-feedback-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-skill-feedback
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/expo-skill-feedback
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill expo-skill-feedback-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Expo users and AI agents lack a direct channel to report what worked, what broke, or what was missing in Expo skills, docs, CLI, and MCP tools, and they need transparent control over whether anonymous usage telemetry is collected. ## Core Features & Use Cases - Actionable Feedback Submission: Send structured feedback via npx submit-expo-feedback with optional --category (skills, docs, mcp, expo-cli, eas-cli, evals) and --subject flags. - Eval Candidate Reporting: Report Expo tasks 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 usage telemetry (off by default) using the bundled telemetry.cjs script or the EXPO_SKILLS_TELEMETRY environment variable. - Use Case: An AI agent fails three times to configure an Expo Router deep-linking setup and the user fixes it manually; the agent shows the user a proposed eval-candidate report, gets approval, and submits it with the failing app's SDK and package versions attached automatically. ## Quick Start Ask the agent to submit feedback about an Expo skill or CLI command that helped or failed, or ask it to check the current Expo skills telemetry status.

Frequently Asked Questions about expo-skill-feedback

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

FAQPage Schema
How do I submit feedback about an Expo skill or CLI command?

Run npx --yes submit-expo-feedback@latest with your actionable feedback as the final argument. Optionally add --category (skills, docs, mcp, expo-cli, eas-cli, evals, or unknown) and --subject naming the exact skill, URL, or command the feedback targets.

How do I report an Expo task that an AI agent failed to complete?

Report it as an eval candidate with --category evals and a structured message containing Task, Expected, Actual, Wrong approach, and Evidence fields. Show the user the exact submission and get approval first; never submit from headless or CI runs.

Is Expo skills telemetry enabled by default?

No, telemetry is off by default and strictly opt-in. Nothing is sent until you run telemetry.cjs --on or set EXPO_SKILLS_TELEMETRY=1, and telemetry never emits from CI environments.

How do I disable Expo skills telemetry tracking?

Run node telemetry.cjs --off from the skill's scripts directory, which removes the opt-in marker file. You can also set EXPO_SKILLS_TELEMETRY=0 or DO_NOT_TRACK=1, which force telemetry off regardless of the marker.

What data does Expo skills telemetry collect?

It sends a skill_invoked event to PostHog containing the skill name, agent harness, OS, CPU architecture, and a hashed anonymous installation ID. No personal data, source code, or prompts are included, and the installation ID itself is never transmitted.

What should I not include in Expo feedback submissions?

Do not include secrets, source code, personal data, long prompts, or stack traces in feedback. Describe code behavior in words rather than pasting it, and keep eval-candidate Task descriptions free of your product or business context.