SkillRepo
Sign InSign Up
Catalog
expo/expo-skill-feedback

expo

expo-skill-feedback

Framework (OSS). Submit feedback on an Expo skill — or on Expo itself — or turn the bundled anonymous usage telemetry on or off (off by default / opt-in; the user saying "enable Expo skills telemetry" in conversation is the switch). Use when an Expo skill was useful, confusing, broken, missing context, or worth improving; when something fell short because of Expo (an SDK bug or confusing framework behavior) rather than the skill; or when the user wants to enable, turn on, opt in to, disable, turn off, opt out of, check the status of, or understand the anonymous usage tracking these skills can send.

global
New~755
v1.0Saved Jul 14, 2026

Expo Skill Feedback

Send anonymous feedback on an Expo skill — or on Expo itself — and turn the bundled usage telemetry on or off. Telemetry is off by default (opt-in) — nothing is sent until it's enabled. Feedback goes to the Expo team via PostHog. Only the skill name, your rating + note, platform, and a hash of a random local install id are sent — never code, prompts, file paths, secrets, or personal data. (A separate automatic skill_invoked event fires when a skill runs once enabled; the switch below controls both.)

Submitting feedback

Be proactive: when a skill was wrong, confusing, outdated, or missing — or the trouble is with Expo itself — send 1-3 concrete sentences. Pass the skill you're rating to --skill (the skill being rated, not expo-skill-feedback):

node "${CLAUDE_PLUGIN_ROOT}/skills/expo-skill-feedback/scripts/skill-feedback.cjs" \
   --skill eas-app-stores --rating useful \
   --text "TestFlight steps were clear and worked first try."
  • --rating: useful · confusing · bug · idea · other
  • --about: skill (default) · expo (the issue is Expo itself, not the skill)
  • --dry-run prints the payload without sending

Never include secrets, source code, long prompts, or stack traces.

If the command refuses because telemetry is off, don't drop the feedback — ask the user once (see Turning it on or off), and resend the same command after they enable.

Turning it on or off

Telemetry is anonymous and off by default (opt-in) — nothing (neither the automatic skill_invoked event nor feedback) is sent until the user enables it. Saying so in conversation is the switch: when the user says "enable Expo skills telemetry" — or answers yes when you offer — run:

node "${CLAUDE_PLUGIN_ROOT}/skills/expo-skill-feedback/scripts/telemetry.cjs" --on

--off turns it off again. When the user asks whether telemetry is on, run --status and relay its output — don't answer from memory; env vars and CI can override the saved state. Env equivalents: EXPO_SKILLS_TELEMETRY=1 to enable, =0 or DO_NOT_TRACK=1 to disable; CI never sends.

Never enable it on your own. If a feedback send was refused because telemetry is off, ask the user once — "Expo skills telemetry is off; enable it (anonymous) and send this?" — and run --on only after an explicit yes. If they decline, drop the feedback silently.

Files6
6 files · 23.0 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Safety

85

Quality

80

Clarity

85

Completeness

78

Summary

This skill enables agents to submit anonymous feedback on Expo skills or the Expo framework itself, and to control opt-in usage telemetry (off by default). Feedback is transmitted via PostHog containing only skill name, rating, note, platform, and a hashed install ID — never code, secrets, or personal data. The skill provides shell commands to send feedback, enable/disable telemetry, and check telemetry status.

Detected Capabilities

shell executionhttp request (PostHog feedback submission)environment variable readfile read (install state)node script execution

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

expo skill feedbackrate skill qualityreport skill issueexpo telemetryenable usage trackingskill too confusingsubmit improvement idea

Risk Signals

INFO

Anonymous telemetry submission via PostHog

SKILL.md line 8, scripts/skill-feedback.cjs
INFO

Environment variables for telemetry control (EXPO_SKILLS_TELEMETRY, DO_NOT_TRACK)

SKILL.md lines 43-45
INFO

Hashed install ID sent with feedback (not plaintext identifier)

SKILL.md line 8

Use Cases

  • Rate an Expo skill as useful, confusing, buggy, or share feature ideas
  • Report issues with Expo framework behavior rather than a specific skill
  • Enable anonymous usage telemetry to help Expo improve skills and framework
  • Disable or check the status of opt-in telemetry
  • Send feedback when a skill is outdated, missing context, or needs improvement

Quality Notes

  • Excellent security posture: telemetry is opt-in (off by default), not opt-out
  • Clear data minimization: only skill name, rating, note, platform, and hashed ID are transmitted — never secrets, code, or personal data
  • Well-documented user controls: users can enable, disable, and check telemetry status via simple commands
  • Explicit guardrails: instructions prohibit automatic enablement without user consent; feedback is dropped silently if telemetry is off and user declines
  • Good edge case handling: CI environments never send telemetry; environment variables can override saved state
  • Supporting scripts are provided but not fully reviewed here (binary/opaque format); telemetry_common.cjs likely contains the PostHog submission logic
  • Clear usage examples with concrete bash commands
  • Appropriate warnings about what NOT to send (secrets, stack traces, source code)
Model: claude-haiku-4-5-20251001Analyzed: Jul 14, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use expo/expo-skill-feedback in your dev environment

Start a Developer trial

Command Palette

Search for a command to run...