# Evidence-Grounded Cover Letter Prompt

> A reusable prompt that turns a pasted job posting plus your own experience notes into a tailored cover letter draft with gap flags and source checks.

## Install

Copy the content below into your project:

# Evidence-Grounded Cover Letter Prompt

A reusable prompt that turns a pasted job posting plus your own experience notes into a tailored cover letter draft with gap flags and source checks.

## Start here

This reusable prompt helps you draft a cover letter using two inputs you paste into an ordinary AI chat that accepts text: (1) the full job posting text, and (2) your own raw experience notes. Nothing is sent or applied for you.

1. Copy the complete prompt (appended with this asset).
2. Paste it into the chat, then paste the job posting and your experience notes below it (or where the prompt asks).
3. Add optional preferences if you have them: tone, length limit, things to emphasize or avoid.
4. Read the output in order: extraction, requirement map, draft, then gap and check report.

**Check the output before using it:** the role title and company name match the posting exactly; every number and tool name comes only from your notes; no requirement is claimed without a matching note; unsourced lines are marked for you to fix.

source reviewed; runtime not tested

## Introduction

Writing a tailored cover letter usually means re-reading the posting, hunting for matching experience, and resisting the urge to overstate. This prompt structures that work: it extracts the posting's own wording, maps your notes to each requirement, drafts plain prose, then reports gaps instead of inventing achievements.

## Prerequisites and permissions

- A text-accepting AI chat; no terminal or API setup is needed.
- The full job posting text and your own experience notes.
- You control what you paste. Avoid sharing sensitive personal data such as ID numbers, home address, or private contact details.
- The prompt only produces a draft. It cannot apply, submit, email, or contact anyone. Keep final review and sending in your own hands.

## Limitations

- Output quality depends entirely on what you supply; missing inputs should prompt the tool to stop and ask.
- Strength labels (strong / partial / none) are the tool's judgement of your pasted notes, not verified facts.
- The number and tool rules mean a note like "cleaned up data" should trigger a request for detail, not a guessed figure.
- The worked example in the prompt is labelled fictional; it is not a tested result.

## FAQ

**What if I only paste the posting?** The prompt should stop and ask for experience notes rather than fill in experience for you.

**Can I use the draft as-is?** No. Treat it as a starting point; confirm every claim against your own records and fill in all placeholders before sending.

## Attribution

Original TokRepo prompt, licensed CC BY 4.0. External reference material retains its own rights. Reference: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>). The complete prompt and translation are appended with this asset.

## Complete reusable prompt

You are helping me draft a cover letter. You write from the material I supply; you do not add facts about me, the employer, or the role that are not in my input.

INPUTS I WILL PASTE
1. JOB POSTING — the full text of the listing (responsibilities, requirements, any stated values or process notes).
2. MY EXPERIENCE NOTES — raw bullets about roles, projects, skills, results, tools, and motivation. Include numbers only if I give them.
3. OPTIONAL — my preferred tone (default: warm-professional), length limit, and anything I want emphasized or avoided.

If the posting or my experience notes are missing, stop and ask for them. If a section is unreadable or truncated, say so and ask me to re-paste rather than guessing.

STEP 1 — EXTRACT (show me this first)
From the posting, list: the role title and company name exactly as written; the top 5–7 requirements or responsibilities in the posting's own phrasing; and any named tools, methods, or keywords. Do not paraphrase requirements into different claims.

From my notes, list: which of those requirements each item plausibly supports, and which requirements have NO supporting item. Flag any bullet that is vague (e.g. 'improved processes') and ask me for one concrete detail I could truthfully add.

STEP 2 — MAP
Produce a short table: Requirement | My supporting evidence | Strength (strong / partial / none). For 'none' rows, do not invent experience. Instead propose a neutral line I could use to show adjacent capability or willingness to learn, clearly labelled as an option for me to accept or reject.

STEP 3 — DRAFT
Write the letter in plain, specific prose:
- Opening: the exact role title, and the single strongest true reason I am a fit drawn from my notes.
- Body: 2–3 short paragraphs, each anchored to a named requirement from the posting and one item from my notes. Where I gave a number, use it exactly; never round up or extrapolate.
- Close: a brief, non-presumptuous line about next steps, plus my name placeholder.
- Do not use clichés like 'I am writing to express my strong interest' unless I ask. No superlatives I cannot support ('world-class', 'unmatched').
- Keep to my stated length, or 250–350 words by default. One page.

STEP 4 — GAP + CHECK REPORT
After the draft, list:
(a) Requirements with no evidence, and every placeholder I must fill.
(b) Every place a reader could ask 'how do you know that?' — quote the line and the source bullet it came from, or mark it UNSOURCED for me to fix.
(c) Three questions a hiring manager might ask that my draft does not yet answer.
(d) A final self-check: does the letter name the correct role and company; is every claim traceable to my notes; is it within the length target; does it avoid restating the whole résumé?

BOUNDARIES
You are preparing a draft only. You cannot apply, submit, email, or contact anyone. Do not promise outcomes, invent credentials, dates, employers, or metrics, or claim I have skills I did not list. If my notes conflict with each other, flag the conflict instead of choosing silently.

WORKED EXAMPLE (fictional)
Input posting line: 'Support weekly reporting and improve data quality in our CRM.'
My note: 'Cleaned 400 duplicate client records in Salesforce over two weeks.'
Illustrative requirement-map row: Support data quality | 400 duplicate records cleaned in Salesforce in two weeks | strong
Illustrative draft sentence: 'In my last role I cleaned 400 duplicate client records in Salesforce over two weeks, which is the kind of data-quality work your weekly reporting depends on.'
Pass/fail checks on that example: the number 400 and the tool name come only from my note (pass if unchanged; fail if inflated or tool invented). The posting's word 'CRM' is echoed, not replaced by a different system. If my note had said only 'cleaned up data', the correct output would be a request for the record count, not a guessed figure.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 有据可依的求职信撰写提示词

一个可复用的提示词：把粘贴的职位描述与个人经历要点，整理成有针对性、标注证据缺口并可逐条核对的求职信草稿。

## 开始使用

这个可复用的提示词帮你用粘贴进普通 AI 对话（能接受文字即可）的两项输入来起草求职信：(1) 完整的职位描述文本，(2) 你自己的经历要点。它不会替你投递或联系任何人。

1. 复制完整提示词（随本资产一并附上）。
2. 粘贴到对话中，再在下方粘贴职位描述和你的经历要点。
3. 如有偏好可补充：语气、长度限制、想强调或想避免的内容。
4. 按顺序阅读输出：信息提取、要求对照表、草稿、缺口与核对报告。

**使用前先核对：**职位名称与公司名是否与招聘信息完全一致；每个数字和工具名是否只来自你的笔记；是否有要求被无据声称；未注明来源的句子是否已标出待你修正。

source reviewed; runtime not tested

## 简介

写一封有针对性的求职信，通常要反复读招聘信息、找匹配经历，还要克制夸大的冲动。这个提示词把这项工作结构化：先按原文提取要求，再把你的笔记逐条对应，然后写出平实的正文，最后报告缺口而不是编造经历。

## 前提与权限

- 一个能接受文字的 AI 对话即可；无需终端或 API 配置。
- 需要完整的职位描述文本和你自己的经历要点。
- 粘贴内容由你决定。避免分享身份证号、家庭住址、私人联系方式等敏感信息。
- 提示词只产出草稿，不能替你投递、提交、发邮件或联系任何人。最终审阅与发送请由你本人完成。

## 局限

- 输出质量完全取决于你提供的内容；缺少输入时，工具应停下来询问。
- 强度标签（strong / partial / none）是工具对你粘贴笔记的判断，不是已核实的事实。
- 数字与工具规则意味着像“清理了数据”这样的笔记应触发补充细节的询问，而不是猜一个数字。
- 提示词中的示例已标明为虚构，它不是已测试的结果。

## 常见问题

**只粘贴职位描述会怎样？** 提示词应停下来向你要经历要点，而不是替你补写经历。

**可以直接用草稿吗？** 不可以。把它当作起点，逐条对照自己的记录核实，并填写所有占位符后再发送。

## 来源与致谢

原创 TokRepo 提示词，采用 CC BY 4.0 许可。外部参考材料保留其自身权利。参考：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)。完整提示词与译文随本资产一并附上。

## 完整可复制提示词

你正在帮我起草一封求职信。你只能依据我提供的材料来写；不得添加我的输入中没有的、关于我、雇主或该职位的事实。

我将粘贴的输入
1. 职位描述——招聘信息的完整文本（职责、要求、任何已声明的价值观或流程说明）。
2. 我的经历要点——关于职位、项目、技能、成果、工具和动机的原始要点。只有我给出数字时才使用数字。
3. 可选——我偏好的语气（默认：温暖专业）、长度限制，以及我想强调或避免的任何内容。

如果缺少职位描述或我的经历要点，停下来向我要。如果某部分无法读取或被截断，如实说明并请我重新粘贴，而不是猜测。

第 1 步——提取（先给我看这一步）
从职位描述中列出：完全按原文写出的职位名称和公司名；用招聘信息自身的措辞列出前 5–7 条要求或职责；以及任何提及的工具、方法或关键词。不要将要求改写成不同的主张。

从我的要点中列出：每一条目大致支撑哪些要求，以及哪些要求没有任何条目支撑。标出任何含糊的要点（例如“改进了流程”），并向我要一个我能如实补充的具体细节。

第 2 步——对照
生成一个简表：要求 | 我的支撑证据 | 强度（strong / partial / none）。对于“none”的行，不要编造经历。而是提出一句中性表述，用来展示相近能力或学习意愿，并清楚标明这是供我接受或拒绝的选项。

第 3 步——起草
用平实、具体的语言写信：
- 开头：准确的职位名称，以及从我的要点中提炼出的、我适合这一职位的最有力且真实的理由。
- 正文：2–3 个短段落，每段都锚定职位描述中一条具名要求和我要点中的一条条目。凡我给出数字的地方，按原样使用；绝不四舍五入或外推。
- 结尾：一句简短、不冒昧的关于后续步骤的话，加上我的姓名占位符。
- 除非我要求，不要使用“I am writing to express my strong interest”之类的套话。不要使用我无法支撑的最高级表述（“world-class”“unmatched”）。
- 遵守我声明的长度，或默认 250–350 词。一页。

第 4 步——缺口 + 核对报告
在草稿之后列出：
(a) 没有证据的要求，以及我必须填写的每个占位符。
(b) 每一处读者可能会问“你怎么知道的？”的地方——引用该句及其来源要点，或标为 UNSOURCED 待我修正。
(c) 招聘经理可能问、而我的草稿尚未回答的三个问题。
(d) 最终自查：信中是否写对了职位和公司；每项主张是否都能追溯到我的要点；是否在目标长度内；是否避免复述整份简历？

边界
你只是在准备草稿。你不能投递、提交、发邮件或联系任何人。不要承诺结果，不要编造资历、日期、雇主或指标，也不要声称我具备我没有列出的技能。如果我的要点彼此冲突，标出冲突，而不是默默替我选择。

示例（虚构）
输入职位描述句：“Support weekly reporting and improve data quality in our CRM.”
我的要点：“Cleaned 400 duplicate client records in Salesforce over two weeks.”
示例性要求对照行：Support data quality | 400 duplicate records cleaned in Salesforce in two weeks | strong
示例性草稿句：“In my last role I cleaned 400 duplicate client records in Salesforce over two weeks, which is the kind of data-quality work your weekly reporting depends on.”
对该示例的通过/不通过检查：数字 400 和工具名只来自我的要点（未改动则通过；若被夸大或工具被编造则不通过）。职位描述中的词“CRM”是呼应原文，而不是被换成另一个系统。如果我的要点只写了“cleaned up data”，正确的输出应是索要记录数量，而不是猜一个数字。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/evidence-grounded-cover-letter-prompt-11ecd8cf
Author: Prompt Lab