expo-skill-feedback

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Expo Skill Feedback

Expo 技能反馈

Help Expo improve by sharing specific feedback about what worked well or what fell short. Feedback submission is independent of usage telemetry and does not require enabling it.

通过分享关于表现出色或有待改进的具体反馈，帮助Expo不断优化。反馈提交与使用遥测相互独立，无需启用遥测即可提交。

Submit feedback

提交反馈

bash

npx --yes submit-expo-feedback@latest "<ACTIONABLE_FEEDBACK>"

Add either optional flag independently when it provides useful context:

bash

npx --yes submit-expo-feedback@latest --category "<CATEGORY>" --subject "<SUBJECT>" "<ACTIONABLE_FEEDBACK>"

--category

defaults to

unknown

, and

--subject

may be omitted when there is no specific target. When including them, choose the values that most precisely identify what the feedback is about:

Category	Subject
`skills`	Exact skill name from its frontmatter, such as `expo-router`
`docs`	Full Expo documentation URL
`mcp`	Exact MCP tool name used
`expo-cli`	Full Expo CLI command, such as `npx expo install`
`eas-cli`	Full EAS CLI command, such as `eas build`
`evals`	Expo package or command the failed task involves, else a capability phrase, such as `expo-router` or `eas build`
`unknown`	Concise Expo product, package, feature, or other topic

In the final argument, say what helped and why, or provide the relevant context, expected behavior, and what happened instead. Do not include secrets, source code, personal data, long prompts, or stack traces.

bash

npx --yes submit-expo-feedback@latest "<ACTIONABLE_FEEDBACK>"

当能提供有效上下文时，可单独添加任一可选参数：

bash

npx --yes submit-expo-feedback@latest --category "<CATEGORY>" --subject "<SUBJECT>" "<ACTIONABLE_FEEDBACK>"

--category

默认值为

unknown

，若无特定目标可省略

--subject

。若添加这两个参数，请选择最能精准描述反馈对象的值：

分类	主题
`skills`	技能开头部分的准确技能名称，例如 `expo-router`
`docs`	Expo文档的完整URL
`mcp`	使用的MCP工具准确名称
`expo-cli`	Expo CLI的完整命令，例如 `npx expo install`
`eas-cli`	EAS CLI的完整命令，例如 `eas build`
`evals`	失败任务涉及的Expo包或命令，若无对应包则用能力描述短语，例如 `expo-router` 或 `eas build`
`unknown`	简洁描述的Expo产品、包、功能或其他主题

在最后一个参数中，请说明哪些内容有帮助及原因，或提供相关上下文、预期行为以及实际发生的情况。请勿包含机密信息、源代码、个人数据、长提示或堆栈跟踪。

Eval candidates: tasks that broke the model

评估候选：导致模型失效的任务

Expo turns hard real-world tasks into agent evals: anything Expo an agent can attempt — framework, EAS, tooling — qualifies, whether or not a skill was involved. The signal worth sending is a task an AI agent could not complete cleanly despite real effort: several failed attempts, a build or screen that never worked, or the user stepping in to fix it manually. Never submit quick slips the agent corrected itself, more than one candidate per session, or a task already reported.

When such a failure happens — or the user says a model failed at an Expo task — show the user the exact submission you intend to send and get approval; the Task field must describe the Expo-technical shape of the task, never the user's product or business context. Without a user to approve it (headless or CI runs), do not submit. Then run from the failing app's directory (the CLI attaches the SDK and package versions, agent harness, and platform automatically) with

--category evals

--subject

naming the Expo package or command involved (a capability phrase only when no single package fits), and this structure in the final argument:

text

Task: <what was asked, self-contained>.
Expected: <observable success criteria>.
Actual: <what the agent did instead>.
Wrong approach: <the specific mistake, such as a wrong API, hallucinated prop, or bad pattern>.
Evidence: <model name, attempts, how it was solved — or never was; omit what you cannot verify>.

A good candidate is solvable (eventually done or clearly doable), verifiable (success is observable), and specific. Mention only environment details the CLI cannot see, such as other key packages or a freshly created app. Describe code; do not paste it. If the command fails with an error naming

evals

as an invalid category, resend once with

--category unknown

and the same subject prefixed

eval-candidate:

; on any other error, do not resend.

Expo将复杂的真实任务转化为Agent评估项：Agent可尝试的任何Expo相关任务——框架、EAS、工具——都符合条件，无论是否涉及技能。值得上报的情况是AI Agent虽付出实际努力但仍无法顺利完成的任务：多次尝试失败、构建或界面始终无法正常工作，或用户不得不手动介入修复。请勿上报Agent自行纠正的小失误、单次会话中多个候选任务，或已上报过的任务。

当出现此类失败——或用户反馈模型在Expo任务中失效时，请向用户展示拟提交的具体内容并获得批准；Task字段必须描述任务的Expo技术形态，绝不能涉及用户的产品或业务上下文。若无用户批准（无头模式或CI运行），请勿提交。然后从故障应用的目录中运行命令（CLI会自动附加SDK和包版本、Agent框架及平台信息），使用

--category evals

，

--subject

指定涉及的Expo包或命令（若无单个对应包则使用能力描述短语），最后一个参数需遵循以下结构：

text

Task: <what was asked, self-contained>.
Expected: <observable success criteria>.
Actual: <what the agent did instead>.
Wrong approach: <the specific mistake, such as a wrong API, hallucinated prop, or bad pattern>.
Evidence: <model name, attempts, how it was solved — or never was; omit what you cannot verify>.

优质的评估候选任务需具备可解决性（最终完成或明显可实现）、可验证性（成功状态可观察）和具体性。仅需提及CLI无法获取的环境细节，例如其他关键包或新建应用。描述代码即可，请勿粘贴代码。若命令因

evals

为无效分类而失败，请重新提交一次，使用

--category unknown

并在原主题前添加前缀

eval-candidate:

；若出现其他错误，请勿重新提交。

Usage telemetry

使用遥测

Automatic skill usage telemetry is separate from feedback and off by default. Never enable it without an explicit user request. Use the following script with

--on

--off

, or

--status

bash

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

Environment equivalents are

EXPO_SKILLS_TELEMETRY=1

to enable and

EXPO_SKILLS_TELEMETRY=0

DO_NOT_TRACK=1

to disable. CI never sends telemetry.

技能自动使用遥测与反馈相互独立，且默认关闭。未经用户明确请求，绝不能启用。使用以下脚本并搭配

--on

、

--off

或

--status

参数：

bash

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

环境变量等效设置：

EXPO_SKILLS_TELEMETRY=1

用于启用，

EXPO_SKILLS_TELEMETRY=0

或

DO_NOT_TRACK=1

用于禁用。CI环境绝不会发送遥测数据。

Submitting Feedback

提交反馈

If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:

bash

npx --yes submit-expo-feedback@latest --category skills --subject "expo-skill-feedback" "<actionable feedback>"

Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.

若你在本技能中发现错误、误导性或过时信息，请上报以帮助Expo改进：

bash

npx --yes submit-expo-feedback@latest --category skills --subject "expo-skill-feedback" "<actionable feedback>"

仅当你有具体且可执行的内容时再提交。请尽可能提供相关上下文。若AI Agent多次失败或用户不得不接管Expo任务，请加载expo-skill-feedback技能并遵循其评估候选流程，而非重复使用上述命令。