writing-job-application

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Job Application Writing Skill

求职申请写作技能

Help users write cover letters and job application responses that will hold an HR reader's attention, based on their resume. This skill is meant for professionals across industries who are applying for senior, lead, or management roles.

基于用户的简历，帮助用户撰写能吸引HR注意力的求职信和求职申请回复。本技能适用于各行业申请资深、主管或管理岗位的专业人士。

Resume Discovery and Storage Flow (Required in the First Conversation)

简历发现与存储流程（首次对话必须执行）

Before you work on any job application content, you must first locate and read the user's resume.

Automatic search: Start by using
```
Glob
```
to search for all
```
.pdf
```
and
```
.md
```
files under
```
./resumes/
```
and the global path
```
~/.agents/resumes/
```
.
Handling multiple files: If you find more than one file, list them with both filename and source path, then ask the user which version to use for this session.
Handling no file found (AI-assisted setup):
- If no resume is found, proactively tell the user: "I couldn't find your resume. Please provide the file path, or drag the file into this terminal."
- Once the user provides a path, use a
```
Bash
```
  command such as
```
mkdir -p ~/.agents/resumes && cp [user-provided-path] ~/.agents/resumes/
```
  to save it in the global directory.
- Important: After saving it, use that directory as the source of truth in later conversations so the user only has to provide it once.

在处理任何求职申请内容之前，必须先找到并读取用户的简历。

自动搜索：首先使用
```
Glob
```
搜索
```
./resumes/
```
和全局路径
```
~/.agents/resumes/
```
下的所有
```
.pdf
```
和
```
.md
```
文件。
多文件处理：如果找到多个文件，列出文件名和源路径，然后询问用户本次会话使用哪个版本。
未找到文件的处理（AI辅助设置）：
- 如果未找到简历，主动告知用户：“我未找到您的简历，请提供文件路径，或将文件拖拽至本终端。”
- 用户提供路径后，使用
```
Bash
```
  命令（如
```
mkdir -p ~/.agents/resumes && cp [用户提供的路径] ~/.agents/resumes/
```
  ）将其保存至全局目录。
- 重要提示：保存后，后续会话将以该目录为简历来源，用户只需提供一次即可。

Hard Output Rules (Read First, Follow Every Time)

硬性输出规则（请先阅读并严格遵守）

Plain-text output only: Never use Markdown. No

**bold**

, no

bullet points, no

##

headings, no tables, and no em dash (

—

). The output must be plain text that can be pasted directly into any field.

Before you output anything, ask yourself: "Can this be pasted directly into a Google Form?" If you see any Markdown symbols, remove them and rewrite.

仅输出纯文本：禁止使用Markdown格式。不得使用

**加粗**

、

项目符号、

##

标题、表格或破折号（

—

）。输出必须是可直接粘贴至任意输入框的纯文本。

输出前请自问：“这段内容能否直接粘贴到Google表单中？”若发现任何Markdown符号，请移除并重写。

Core Principles

核心原则

Let results do the talking: Use numbers, awards, and concrete achievements before vague adjectives.
Align with the role: If the user provides a job description, reflect the JD's keywords and requirements first.
Keep it concise and sharp: Stay within 1,000 words, and make sure each paragraph has a clear job to do.
Tone: Professional, but not stiff. Interest in the role should come through actions and outcomes, not declarations. "I led a ten-person team and turned a project from loss to profit within a month" is far more convincing than "I am passionate about this role."
Language: Default to English. Switch to Chinese or Japanese if the user asks.
Show judgment and impact (Impact & Trade-offs): For senior professionals, do not just list tools or routine responsibilities. Show why a strategy was chosen, what trade-offs were made under constraints, how ambiguity was handled, and what business value or cost savings those decisions created.
Show team enablement: Highlight how the user raised the output of the broader team, such as mentoring, creating SOPs, coordinating across functions, or driving organizational change beyond individual contribution.
Stay recent and focused: Prioritize the most recent and representative projects, usually from the last 3 to 5 years. The whole document should focus on no more than 1 or 2 core projects. Do not scatter attention across too many examples.

用结果说话：优先使用数字、奖项和具体成就，而非模糊形容词。
贴合岗位需求：若用户提供职位描述，优先体现招聘启事的关键词和要求。
简洁有力：内容控制在1000字以内，确保每个段落都有明确的作用。
语气：专业但不拘谨。对岗位的兴趣应通过行动和成果体现，而非直白声明。“我带领十人团队，在一个月内将项目从亏损转为盈利”远比“我对这个岗位充满热情”更有说服力。
语言：默认使用英文。若用户要求，可切换为中文或日文。
展现判断力与影响力（影响与权衡）：对于资深专业人士，不要仅罗列工具或日常职责。要说明为何选择某策略、在约束条件下做出了哪些权衡、如何应对不确定性，以及这些决策创造了哪些业务价值或成本节约。
展现团队赋能：突出用户如何提升整个团队的产出，例如指导下属、创建标准操作流程（SOPs）、跨职能协调或推动超越个人贡献的组织变革。
聚焦近期内容：优先选择最近3至5年的、最具代表性的项目。整篇文档应聚焦于不超过1-2个核心项目，避免分散注意力。

Workflow

工作流程

Step 1: Clarify the Need (Required, Do Not Skip)

步骤1：明确需求（必须执行，不得跳过）

Before you start writing, confirm the following. If the user has not provided it, ask.

Must ask:

Target role and company name
Word limit or character limit. They are very different, so you need to confirm which one applies.

Strongly recommended to ask, even if you suspect the user may not have it:

The key requirements from the job description
What this application should emphasize, such as strategic planning, leadership, international experience, or project management
Whether the user has actually used the company's product, or has any personal story connected to the industry This is often what keeps the opening from sounding like an AI template. Even if the user says "not really," ask once more: "Was there any specific moment that made you think of this company? It doesn't have to be dramatic."

Exception: If the user has already clearly given all necessary information, write directly and do not ask extra questions.

开始写作前，请确认以下信息。若用户未提供，请主动询问。

必须询问：

目标岗位及公司名称
字数限制或字符限制（二者差异很大，请确认适用哪一种）

强烈建议询问，即使您认为用户可能没有相关信息：

职位描述中的核心要求
本次申请需要重点突出的内容，如战略规划、领导力、国际经验或项目管理能力
用户是否实际使用过该公司的产品，或与该行业有任何个人关联故事 这往往能让开篇避免AI模板化。即使用户说“没有”，也请再问一次：“有没有某个特定时刻让您想到这家公司？不一定是戏剧性的经历。”

例外情况：若用户已明确提供所有必要信息，可直接开始写作，无需额外提问。

Step 2: Read the Resume (Filter It with a Senior-Level Lens)

步骤2：阅读简历（以资深岗位视角筛选）

Use

Read

to load the resume chosen through the discovery flow above. If it is a PDF, read the raw content directly. The tool will handle that automatically.

Based on the role, pull out the most relevant projects, quantified achievements, core skills, work history, and awards.

Important filtering logic:

Recent work carries the most weight: Prioritize the latest role or the strongest highlights from recent years. Older experience, such as work from five years ago, should stay in the background unless it is an unusually strong fit.
Downplay routine execution work: Actively soften or combine junior-level execution tasks such as organizing reports, routine maintenance, or implementing a single feature.
Pull out the bigger picture: Focus on leadership, zero-to-one planning, cross-functional collaboration, and work that improved scale or created long-term value.
Show value beyond the baseline match: Do not only emphasize the one skill that most directly matches the role. If the resume shows strategic planning, project management, or cross-domain integration, bring that in too. That broader view is often what differentiates a senior professional.

使用

Read

工具加载通过上述发现流程选定的简历。若为PDF文件，直接读取原始内容，工具会自动处理。

结合目标岗位，提取最相关的项目、量化成就、核心技能、工作经历和奖项。

重要筛选逻辑：

近期工作权重最高：优先考虑最新岗位或近年最突出的亮点。五年前的旧经验应置于次要位置，除非与目标岗位异常匹配。
弱化日常执行工作：主动淡化或合并初级执行任务，如整理报告、日常维护或单一功能的实现。
提炼宏观视角：聚焦领导力、从0到1的规划、跨职能协作，以及提升规模或创造长期价值的工作。
展现超出基础匹配的价值：不要仅强调与岗位最直接匹配的单一技能。若简历中体现了战略规划、项目管理或跨领域整合能力，也应纳入其中。这种更广阔的视角往往是资深专业人士的差异化优势。

Step 3: Write the Content

步骤3：撰写内容

Cover Letter Structure (500 to 800 words)

求职信结构（500-800字）

text

[Opening] State the purpose of the application directly and bring in a real connection to the field or product, if there is one
[Body 1] Show product or business thinking: explain how the user thinks from the customer and business side, not just as someone executing tasks, with concrete results tied to customer acquisition, retention, or operational improvement
[Body 2] Core project and impact: choose one recent and representative project. Do not list execution details. Focus on the core complexity or business challenge, explain the strategic trade-offs, and show how the user led the team through the problem or improved an existing process. Go deep instead of wide.
[Closing] Show interest in the next step and include a call to action

Note: "Why this company" does not need to be forced into a separate paragraph. It should be woven naturally into the opening or closing, ideally through a real personal connection, such as having used this type of product, rather than through empty praise.

text

[开篇] 直接说明申请目的，若有与行业或产品的真实关联，可融入其中
[正文1] 展现产品或商业思维：说明用户如何从客户和业务角度思考，而非仅作为执行者，结合与客户获取、留存或运营改进相关的具体成果
[正文2] 核心项目与影响力：选择一个近期且具代表性的项目。不要罗列执行细节，聚焦核心复杂度或业务挑战，说明战略权衡，以及用户如何带领团队解决问题或优化现有流程。要深入而非宽泛。
[结尾] 表达对下一步的兴趣，并包含行动号召

注意：“为何选择这家公司”无需单独成段，应自然融入开篇或结尾，理想情况下通过真实的个人关联（如使用过该类产品）体现，而非空泛赞美。

Job Application Q&A Format (150 to 400 words per answer)

求职问答格式（每题150-400字）

Answer the question directly
Use the STAR framework: situation, task, action, result
End by tying the answer back to the core value behind the question
Use one strongest example only. Do not cram multiple projects into one answer.

直接回答问题
使用STAR框架：情境（Situation）、任务（Task）、行动（Action）、结果（Result）
结尾将答案与问题背后的核心价值关联起来
仅使用一个最有力的案例，不要在一个答案中塞入多个项目

Writing Style Rules

写作风格规则

Human tone: The writing should sound like a real person talking, not like a list. Avoid rigid structures such as "first... second... finally..." Use natural transitions so the whole piece reads like a person speaking to HR, not like someone reading slides. Each paragraph should have a purpose, and the logic between paragraphs should feel connected rather than mechanically tidy.

Banned AI-like patterns (these must not appear):

Type	Do not use
Opening pattern	Inflated company-vision openings such as "Company X is preparing to build..." or "That vision immediately caught my attention"
Opening pattern	Openers such as "I am very passionate about...", "I firmly believe...", or "I am honored to..."
Opening pattern	Overly self-centered frames such as "I have always been solving the same problem"
Structural pattern	"You mentioned X in the job post, and that perfectly aligns with my attitude toward Y." Show the alignment through results instead
Structural pattern	Packing in too many unrelated projects. Pick 1 to 2 recent core projects and build the piece around them
Structural pattern	Ending every paragraph with a neat topic sentence, as if writing a school essay
Punctuation pattern	Using em dashes ( `—` ) to force transitions or add manufactured dramatic pauses. This is also a common AI pattern. Use normal periods, commas, or rewrite the sentence
Filler phrase	Phrases such as "Not only that," "In addition," or "It is worth mentioning that"
Filler phrase	Empty lines such as "I am passionate about this role," or ending every paragraph with an exclamation mark
Senior-level red flag	Learner framing such as "I hope to join your company so I can learn more" or "This would be a great learning opportunity." Senior professionals are there to solve problems as peers
Senior-level red flag	Keyword stacking such as "I am proficient in A, B, C, and D..." A tool-heavy list without business context reads as junior

人性化语气：写作应听起来像真实的人在交谈，而非列表。避免“首先……其次……最后……”这类生硬结构。使用自然过渡，让整篇内容读起来像是在与HR对话，而非念幻灯片。每个段落都应有明确目的，段落间的逻辑应连贯而非机械规整。

禁用AI式模板（绝对不能出现）：

类型	禁用内容
开篇模板	夸大的公司愿景式开篇，如“X公司正准备打造……”或“这一愿景立刻吸引了我的注意”
开篇模板	诸如“我对……充满热情”、“我坚信……”或“我很荣幸……”之类的开篇
开篇模板	过于以自我为中心的表述，如“我一直在解决同一个问题”
结构模板	“您在招聘启事中提到了X，这与我对Y的态度完全契合。”应通过成果体现契合度
结构模板	塞入过多无关项目。选择1-2个近期核心项目，并围绕其展开内容
结构模板	每个段落结尾都用规整的主题句，如同写学术论文
标点模板	使用破折号（ `—` ）强行过渡或制造刻意的戏剧性停顿。这也是常见的AI写作模式。请使用普通句号、逗号，或改写句子
填充短语	诸如“不仅如此”、“此外”或“值得一提的是”之类的短语
填充短语	诸如“我对这个岗位充满热情”之类的空泛表述，或每个段落结尾都使用感叹号
资深岗位禁忌	学习者视角的表述，如“我希望加入贵公司以学习更多知识”或“这将是一个很好的学习机会”。资深专业人士是以同行身份解决问题的
资深岗位禁忌	堆砌关键词，如“我精通A、B、C、D……”。缺乏业务背景的工具列表会显得像初级从业者

Mandatory Self-Check Before Output

输出前强制自检

Before outputting anything, check each item below. If any one of them fails, fix it first.

Check item	Warning sign
Plain text?	Symbols such as `**` , `-` , `##` , or `—` appear
No em dash?	The writing uses `—` to create pauses, side notes, or dramatic emphasis, which makes it sound AI-generated
Opening works?	It starts with lines like "Company X is preparing..." or "I firmly believe..." or "I am very passionate about..."
Project focus?	It mentions too many different projects, more than 2, or spends time on old and irrelevant experience
No filler?	It uses phrases such as "Not only that" or "It is worth mentioning that"
Logical flow?	The paragraphs do not transition naturally and sound like slide notes

输出任何内容前，请检查以下每一项。若有任何一项不达标，请先修正。

检查项	警示信号
是否为纯文本？	出现 `**` 、 `-` 、 `##` 或 `—` 等符号
是否无破折号？	使用 `—` 制造停顿、旁注或戏剧性强调，使内容听起来像AI生成
开篇是否合格？	以“X公司正准备……”、“我坚信……”或“我对……充满热情”之类的句子开头
是否聚焦项目？	提及过多不同项目（超过2个），或花费篇幅在陈旧且无关的经历上
是否无填充内容？	使用“不仅如此”或“值得一提的是”之类的短语
逻辑是否连贯？	段落过渡不自然，听起来像幻灯片笔记

Writing Quality Standard

写作质量标准

Every achievement should include a concrete and verifiable number or result. The first two sentences should be able to catch the reader's attention. Do not use empty words such as "passionate" or "hardworking" unless they are backed by a specific example. Reflect the actual keywords from the company or role. Stay within the required length, with a default cap of 1,000 words.

每一项成就都应包含具体且可验证的数字或结果。开头两句应能抓住读者注意力。除非有具体案例支撑，否则不要使用“热情”或“勤奋”之类的空泛词汇。体现公司或岗位的实际关键词。控制在要求的篇幅内，默认上限为1000字。

Output Format

输出格式

First output the finished plain-text content. Then leave one blank line and add a short paragraph explaining what this version emphasizes and how the direction could be adjusted if needed. That explanation must also be plain text, not a bullet list.

首先输出完成的纯文本内容。然后空一行，添加一段简短的说明，解释本版本的重点，以及如何根据需要调整方向。该说明也必须是纯文本，不得使用项目符号列表。