expo-skill-feedback

Submit feedback and eval candidates for Expo skills and control opt-in usage telemetry.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Expo skills and tooling improve only when users report what worked and what failed, but there is no built-in channel for structured feedback or for flagging tasks where an AI agent repeatedly failed. This Skill provides a standard command-line path to submit actionable feedback, report failed Expo tasks as eval candidates, and manage anonymous usage telemetry. ## Core Features & Use Cases - Structured Feedback Submission: Send actionable feedback via npx submit-expo-feedback with optional --category (skills, docs, mcp, expo-cli, eas-cli, evals, unknown) and --subject flags that precisely target what the feedback is about. - Eval Candidate Reporting: Report tasks an AI agent could not complete cleanly, using a structured Task/Expected/Actual/Wrong approach/Evidence format, with user approval required before submission. - Opt-in Telemetry Control: Check, enable, or disable anonymous skill usage telemetry with telemetry.cjs --status/--on/--off; telemetry is off by default and never sends from CI. - Use Case: An AI agent fails three times to configure an Expo Router deep-linking setup and the user fixes it manually. Use this Skill to draft the eval-candidate report, show it to the user for approval, and submit it with --category evals --subject expo-router. ## Quick Start Ask the assistant to submit feedback on an Expo skill or CLI command, for example by saying "submit feedback that the expo-router skill was missing context about typed routes".

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, command, or URL 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 --subject naming the Expo package or command involved. Structure the message as Task, Expected, Actual, Wrong approach, and Evidence, show it to the user for approval first, and submit at most one candidate per session.

Is Expo skills usage telemetry enabled by default?▼

No, telemetry is off by default and strictly opt-in. It only activates after running telemetry.cjs --on or setting EXPO_SKILLS_TELEMETRY=1, and it never sends data from CI environments or when DO_NOT_TRACK is set.

How do I check or disable Expo skills telemetry?▼

Run node telemetry.cjs --status from the skill's scripts directory to see the current state and why. Use --off to remove the opt-in marker and disable it, or --on to enable anonymous usage events.

What should not be included in Expo feedback submissions?▼

Do not include secrets, source code, personal data, long prompts, or stack traces in feedback. Eval candidate reports must describe the Expo-technical shape of the task, never the user's product or business context, and describe code rather than paste it.