datocms-feedback

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

DatoCMS Feedback

DatoCMS 反馈

Prefilled

datocms.com/support

URL when a DatoCMS skills/MCP workflow is stuck. Escape hatch, not a fixing workflow.

当DatoCMS Skill/MCP工作流陷入停滞时，预填充

datocms.com/support

链接。这是应急方案，而非修复工作流的流程。

Before doing anything visible

执行任何可见操作前

User explicitly asked to report/file/summarize feedback about DatoCMS skills/MCP → generate immediately.
Frustration or dead end inferred → do not generate. Offer once, wait for confirmation.
Credible retry exists → do not mention feedback. Stay in the active DatoCMS workflow.

Not for trial-and-correction. Single failed command, MCP call, API error, validation response, schema miss, missing env value, or setup failure stays with the active workflow when a retry path exists.

Project/schema/frontend/migration/plugin issue still fixable → route to the relevant DatoCMS skill.

用户明确要求报告/提交/总结关于DatoCMS Skill/MCP的反馈 → 立即生成链接。
推断用户存在不满或工作流陷入死胡同 → 不要生成链接。先提供一次选项，等待用户确认。
存在可靠的重试路径 → 不要提及反馈，继续当前DatoCMS工作流。

不适用于尝试-修正场景。当存在重试路径时，单次命令失败、MCP调用失败、API错误、验证响应、架构遗漏、环境值缺失或设置失败均需留在当前工作流中处理。

项目/架构/前端/迁移/插件问题仍可修复 → 引导至对应的DatoCMS Skill。

If frustration is inferred

若推断用户存在不满

Offer once, then wait:

text

It looks like this may have gone past the normal retry-and-correct loop. Sorry about that. These workflows are still evolving, and clear feedback helps us understand where the experience broke down. If you want, I can build a prefilled DatoCMS support link with the goal, where the skills/MCP flow got stuck, and relevant runtime context.

If the user agrees, generate the URL.

先提供一次选项，然后等待用户回应：

text

看起来这已经超出了常规的重试-修正循环范围，非常抱歉。这些工作流仍在迭代优化中，清晰的反馈能帮助我们了解体验故障点。如果您需要，我可以生成一个预填充的DatoCMS支持链接，包含您的目标、Skill/MCP流程停滞的位置以及相关运行时上下文。

若用户同意，生成该链接。

URL shape

URL 格式

Base:

https://www.datocms.com/support

. Query params URL-encoded via

encodeURIComponent

```
topics=technical-support/ai-integration-issues
```
— fixed slug for skills/MCP feedback (URL-encode the
```
/
```
as
```
%2F
```
). Required — form does not render without it.
```
subject=<short subject>
```
— one line.
```
body=<sanitized message>
```
— see body rules.

Append

#form

anchor — page scrolls to the form on load.

基础地址：

https://www.datocms.com/support

。查询参数需通过

encodeURIComponent

进行URL编码。

```
topics=technical-support/ai-integration-issues
```
— Skill/MCP反馈的固定标识（需将
```
/
```
编码为
```
%2F
```
）。必填项 — 缺少该参数表单无法显示。
```
subject=<简短主题>
```
— 单行文本。
```
body=<脱敏后的内容>
```
— 请遵循正文规则。

追加

#form

锚点 — 页面加载时自动滚动至表单区域。

Body rules

正文规则

Write from the user's point of view.
Include: attempted goal, whether skills/MCP/both were involved, visible runtime context, visible reasoning level, what failed, expected outcome.
Use
```
not visible from this conversation
```
for nonessential missing details.
Ask at most one short question before generating, only when a missing detail is necessary for support to understand the report.
Keep raw details short. Command names, call names, short safe error excerpts only when useful.
No secrets, tokens, auth headers, private content, user-identifying details, full request/response payloads, raw transcript dumps, long local paths.
No apology on DatoCMS's behalf inside the body.
Keep plaintext body under ~4000 chars — encoded URL must fit edge limits (Vercel ~14 KB). Trim if longer.
No
```
Hi DatoCMS support,
```
/
```
Thanks,
```
salutations — the form is not an email.

以用户视角撰写。
包含内容：尝试达成的目标、是否涉及Skill/MCP/两者、可见的运行时上下文、可见的推理层级、故障情况、预期结果。
对于非必要的缺失细节，使用
```
not visible from this conversation
```
表述。
仅当缺失细节对支持团队理解报告至关重要时，在生成前最多提出一个简短问题。
原始细节需简洁。仅保留有用的命令名称、调用名称、简短安全错误片段。
不得包含密钥、令牌、认证头、私有内容、用户识别信息、完整请求/响应负载、原始对话记录、长本地路径。
正文内不得代表DatoCMS致歉。
纯文本正文需控制在约4000字符以内 — 编码后的URL需符合边缘限制（Vercel约14 KB）。若超出需精简。
不得使用
```
Hi DatoCMS support,
```
/
```
Thanks,
```
这类问候语 — 该表单并非邮件形式。

Body shape

正文格式

Unless conversation calls for shorter:

text

I ran into a frustrating issue while trying to use the DatoCMS skills/MCP workflow.

Goal: [goal].
Workflow involved: [skills/MCP/both/not visible from this conversation].

What happened: [short sanitized summary of the loop, wrong routing, repeated misunderstanding, or dead end].

Context:
- Runtime/client: [visible value or not visible from this conversation]
- Runtime identifier: [visible value or not visible from this conversation]
- Reasoning level: [visible value or not visible from this conversation]
- Safe error excerpt: [short excerpt or not included]

Expected: [expected outcome]. Could not get there because: [impact].

Sharing so you can see where the skills/MCP experience broke down.

除非对话要求更简短，否则遵循以下格式：

text

I ran into a frustrating issue while trying to use the DatoCMS skills/MCP workflow.

Goal: [goal].
Workflow involved: [skills/MCP/both/not visible from this conversation].

What happened: [short sanitized summary of the loop, wrong routing, repeated misunderstanding, or dead end].

Context:
- Runtime/client: [visible value or not visible from this conversation]
- Runtime identifier: [visible value or not visible from this conversation]
- Reasoning level: [visible value or not visible from this conversation]
- Safe error excerpt: [short excerpt or not included]

Expected: [expected outcome]. Could not get there because: [impact].

Sharing so you can see where the skills/MCP experience broke down.

Output flow

输出流程

Two steps. Do not build or reveal the URL on step 1.

Step 1 — show draft body. Output the sanitized body text (what lands in the textarea) for review. End with: "Want me to open the prefilled support page in your browser?"

Step 2 — open the link. After user confirms, build the URL and open:

macOS:
```
open '<url>'
```
Linux:
```
xdg-open '<url>'
```
Windows:
```
start '' '<url>'
```

Single-quote the URL — shell would otherwise interpret

and

. Echo the URL on its own line as a clickable fallback.

No "I drafted...", no recap.

分为两步。第一步不得构建或展示URL。

第一步 — 展示草稿正文。 输出脱敏后的正文文本（将填入文本框的内容）供用户审阅。结尾需添加："需要我在您的浏览器中打开预填充的支持页面吗？"

第二步 — 打开链接。 用户确认后，构建URL并打开：

macOS:
```
open '<url>'
```
Linux:
```
xdg-open '<url>'
```
Windows:
```
start '' '<url>'
```

需用单引号包裹URL — 否则shell会解析

和

字符。单独一行输出URL作为可点击的备选方案。

不得添加"我已起草..."这类表述，无需回顾内容。