返回详情页

aim

对比查看原文与翻译

🇺🇸

原文

英文
🇨🇳

翻译

中文
Read the data and propose the intent behind it, for the user to confirm.
读取数据并推测用户的潜在意图，供用户确认。

Goal

目标

The result is a proposal the user only confirms, revises, or rejects — never a question. Asking makes the user compose a sentence they did not have ready; proposing lets them answer with a yes. If the turn ends with them writing that sentence anyway, the skill missed.
最终输出应为用户只需确认、修改或拒绝的提议——绝对不能是问题。提问会让用户不得不组织一段他们尚未准备好的表述；而提议则允许用户只需回复“是”即可。如果最终用户还是需要自行组织表述，说明该技能未发挥作用。

Workflow

工作流程

  1. Read every piece of the handed-over data end to end before proposing anything.
  2. State the intent you read, in one line grounded in what the data actually shows.
  3. State briefly what you would do next on that intent.
  4. Ask only to confirm — right, wrong, or adjust.
  1. 在提出任何提议前，完整通读所有提交的数据。
  2. 用一句话陈述你读取到的意图，需基于数据实际呈现的内容。
  3. 简要说明针对该意图你下一步会采取的行动。
  4. 仅请求用户确认——是否正确、错误或需要调整。

Rules

规则

  • Read before proposing. A proposal without reading is a guess.
  • Ground it in the data. Point at what you read, not what you assumed.
  • One intent per turn. If two are plausible, propose the likelier and name the other in a clause.
  • Confirm, don't compose. If the turn ends with the user assembling a sentence, redo the proposal.
  • If the data is too thin to propose from, say so and stop. Do not fall back to asking.
  • 先读取再提议。未读取数据就提出的提议只是猜测。
  • 基于数据内容。要指出你从数据中读到的信息，而非你的假设。
  • 每次只提出一个意图。如果有两个合理的意图，优先提出更可能的那个，并在分句中提及另一个。
  • 请求确认，而非让用户表述。如果最终用户仍需自行组织句子，请重新拟定提议。
  • 如果数据过于单薄无法推测意图，请直接说明并停止操作。不要退化为提问。

Verification

验证

The user's next reply is short — a yes, a correction, or a small adjustment. If they had to explain what they wanted from scratch, the proposal was wrong, or was really a question in disguise.
用户的下一次回复应简短——比如“是”、修正内容或小幅调整。如果用户不得不从头解释他们的需求，说明提议有误，或者该提议本质上是伪装成提议的问题。