Back to Details

evidence-based-citations

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
The user wants every field value or factual claim you produce in the current response to be backed by an official, verifiable source. Apply this skill to the response that triggered it; do not assume it stays active for the rest of the conversation unless the user clearly asks for it to.
用户要求你在当前回复中给出的每个字段值或事实声明都必须有官方、可验证的来源支撑。将此技能应用于触发它的回复；除非用户明确要求，否则不要假设它在后续对话中持续生效。

Output format

输出格式

For each field or claim, respond with exactly these four labeled lines:
  • Field: the field name (or a short description of the claim)
  • Value: the value you are assigning (or the claim itself)
  • Quote: the exact verbatim text from the source that supports the value
  • Source: the official URL where the quote can be found
When there are multiple fields, repeat the block once per field. Keep blocks separated by a blank line.
对于每个字段或声明，严格按照以下四个带标签的行进行回复：
  • Field：字段名称（或声明的简短描述）
  • Value：你指定的值（或声明本身）
  • Quote：来自来源的精确原文，用于支撑该值
  • Source：可找到该引用内容的官方URL
当存在多个字段时，每个字段重复上述模块，模块之间用空行分隔。

Source selection rules

来源选择规则

  1. Prefer primary sources, in this order:
    • Official product / project documentation
    • Standards documents (RFCs, W3C specs, ISO standards)
    • Official API references
    • Source code in the project's own repository
  2. Accept secondary sources (blog posts, Stack Overflow, forum threads, news articles, third-party tutorials) only as a last resort, and clearly label them as such in Source.
  3. The Quote field must contain text that actually appears at the Source URL. Do not paraphrase inside the quote, and do not stitch together text from different parts of the page without making the cut explicit (e.g. with 
    …
    ).
  4. If you cannot find an official source for a value, say so explicitly:
    • Source: 
      No official source found.
      Then either omit the value, mark it as unverified, or ask the user how to proceed. Never invent a quote or URL.
  1. 优先选择一手来源，优先级顺序如下：
    • 官方产品/项目文档
    • 标准文档（RFC、W3C规范、ISO标准）
    • 官方API参考文档
    • 项目自有代码库中的源代码
  2. 仅在万不得已时才接受二手来源（博客文章、Stack Overflow、论坛帖子、新闻文章、第三方教程），并且必须在Source中明确标注。
  3. Quote字段必须包含确实出现在Source URL中的文本。不要在引用中改写内容，也不要拼接页面不同部分的文本，除非明确标注截断（例如使用
    …
    ）。
  4. 如果无法找到某个值的官方来源，请明确说明：
    • Source：
      No official source found.
      然后可以选择省略该值、标记为未验证，或询问用户如何处理。绝对不要编造引用或URL。

When to fetch

何时抓取来源

  • If you have a browser / fetch tool available, retrieve the source page and copy the quote directly from it before responding.
  • If you do not have a fetch tool, always respond with 
    Source: No official source found.
    rather than citing URLs from memory. LLMs cannot reliably verify URL accuracy or quote fidelity without actually fetching the page, even when a URL feels familiar.
  • 如果有浏览器/抓取工具可用，请先获取来源页面并直接从中复制引用内容，再进行回复。
  • 如果没有抓取工具，请始终回复
    Source: No official source found.
    ，而不是凭记忆引用URL。即使URL看起来很熟悉，LLM在未实际抓取页面的情况下也无法可靠地验证URL的准确性或引用内容的真实性。

Example

示例

User: What HTTP status code indicates a successful request, per the HTTP semantics RFC?
用户：根据HTTP语义RFC，哪个HTTP状态码表示请求成功？

What this skill is not

此技能不适用的场景

  • It is not a general "be careful with facts" reminder. Apply the strict four-field format only when the user has invoked this skill or is clearly asking for evidence-backed answers.
  • It does not change how you write code, edit files, or run tools. It only governs how you report values and claims back to the user.
  • 它不是一般性的“注意事实准确性”提醒。只有当用户调用此技能或明确要求提供有证据支撑的回答时，才使用严格的四字段格式。
  • 它不会改变你编写代码、编辑文件或运行工具的方式。它仅规范你向用户报告值和声明的方式。