cover-letter-writer
Skill6 starsChanged 5 months agoMITView on GitHub
Write Korean job application cover letter drafts from a question, JD, resume.md, and optional company values input. Use when the user asks for 자기소개서, 자소서, 지원동기, 입사 후 포부, 필살기, 3C4P experience decomposition, experience-based application answers, or tailored cover letter text grounded in resume.md evidence.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- DexterslabAi/resume-genietheir own version, first seen Nov 1, 2026
- JayRHa/agent-skillstheir own version, first seen Oct 15, 2026
- fred-brown-3/job-hunter-aitheir own version, first seen Oct 13, 2026
- SkillMedev/job-search-kittheir own version, first seen Oct 5, 2026
- squerne/open-career-skillstheir own version, first seen Aug 7, 2026
Used with
Projects with it also use 0-template, github-actions-builder and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JayRHaSkill0-template
Template for creating a new Agent Skill. Copy this folder, rename it to your skill's kebab-case name, and fill in every section. Use this as the starting point whenever you author a new skill for the AgentSkills library.
Also in 3 projects that use this
JayRHaSkillgithub-actions-builder
Builds reliable, fast, and secure GitHub Actions CI/CD workflows with dependency caching, build matrices, scoped secrets, concurrency control, and reusable/composite workflows. Use this skill when the user asks to "create a GitHub Actions workflow", "set up CI", "add CI/CD", "fix a flaky/slow GitHub Actions pipeline", "add a build matrix", "cache dependencies in CI", "write a reusable workflow", "configure deployment with environments and secrets", or mentions files under .github/workflows.
Also in 3 projects that use this
xmqywxSkillmeeting-summarizer
Transform meeting transcripts into structured summaries with action items, decisions, follow-ups, and efficiency analysis. Works with any meeting format.
Also in 3 projects that use this
pbc-osSkillsecrets-manager
Set up and configure cloud secrets management for your AI agent. Guides users through platform selection (GCP, AWS, Azure, 1Password, Doppler, HashiCorp Vault), account setup, CLI configuration, and secure credential storage.
Also in 3 projects that use this
MehdibargachSkillokr-writer
Turn business goals into structured OKRs with measurable Key Results, linked initiatives, alignment check, and anti-goals. Takes a strategic priority and outputs ready-to-use OKRs.
Also in 3 projects that use this
- +7 more from JayRHa
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- squerne/open-career-skills★ 26same name
- jaskirat1616/grok-skills★ 22same name
- JayRHa/agent-skills★ 12same name
- JayRHa/AgentSkills★ 12same name
- art2url/career-agent-skills★ 9same name
- xiding-code/job-application-skills★ 4same name
- DexterslabAi/resume-genie★ 0same name
- fred-brown-3/job-hunter-ai★ 0same name
- SkillMedev/job-search-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- application-packagerSkill
- company-values-analyzerSkill
- hr-reviewerSkill
- interview-prepSkill
- jd-analyzerSkill
- job-searcherSkill
- resume-intakeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
34 rules. 0 are common, 22 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
22
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Write cover letters from evidence, not imagination.
- Very specific: line 18
Use this skill after JD analysis and usable resume.md evidence exist, or when the user asks for Korean 자기소개서, 자소서, 지원동기, 입사 후 포부, 필살기, or …
- Very specific: line 22
Do not use this skill when resume.md is missing or too weak, when the JD/question is missing, or when the user asks only for HR review or …
- Distinctive: line 37
Do not invent missing metrics, tools, responsibilities, awards, employers, or outcomes.
- Distinctive: line 38
Do not imply seniority beyond the resume evidence.
- Distinctive: line 90
If company values are provided, use them as supporting context only.
- Very specific: line 94
When the user needs a stronger 필살기, asks for 3C4P, or the experience feels vague, decompose the selected evidence with …
- Distinctive: line 95
If evidence is missing, ask follow-up questions before drafting.
- Distinctive: line 115
When blind hiring applies, remove direct and indirect personal identifiers prohibited by the employer.
- Distinctive: line 117
Use the same stable question ID in each draft, final answer, length check, and evidence-map entry.
- Very specific: line 120
Never write a new claim back into resume.md.
- Distinctive: line 125
Prefer concrete actions over abstract claims.
- Very specific: line 127
Use a user-provided writing sample when available, but do not mimic claims or facts that are absent from resume.md.
- Distinctive: line 129
Prefer one concrete, evidence-backed example over several shallow examples.
- Distinctive: line 130
Avoid repetitive paragraph openings, formulaic transitions, symmetrical three-part boilerplate, and stacked "~하겠습니다" endings.
- Distinctive: line 131
Keep sentences focused and readable.
- Distinctive: line 133
Keep the tone factual, specific, and interview-defensible.
- Distinctive: line 137
Do not invent experience, metrics, responsibilities, awards, company names, or tools.
- Very specific: line 138
Do not use a strong claim unless it is supported by resume.md.
- Distinctive: line 139
Do not copy company values page wording verbatim.
- Distinctive: line 140
Do not force every experience into 3C4P if the evidence does not support it.
- Distinctive: line 141
Do not make a new grad sound like an experienced hire.
- Distinctive: line 142
Do not make an experienced candidate rely only on passion or personality.
- Distinctive: line 143
Do not switch playbooks mid-answer set, or apply one career type's frame to the other.
- Distinctive: line 144
Do not invent a reason for leaving a job, an employment gap, or a tenure length.
- Distinctive: line 145
Do not criticize a previous employer, manager, team, or colleague.
- Distinctive: line 146
Do not add artificial imperfections, slang, false personal details, or unsupported anecdotes to make the writing appear more human.
- Distinctive: line 147
Do not describe the company with interchangeable praise or as a stepping stone.
- Very specific: line 149
Read references/career-type-playbooks.md first to resolve the career type and load the matching playbook.
- Very specific: line 150
Read references/cover-letter-rules.md for detailed writing and review rules.
- Very specific: line 151
Read references/question-types.md to classify the question and for failure and sub-role handling.
- Very specific: line 152
Read references/3c4p-experience-framework.md when decomposing an experience into a stronger cover letter angle.
- Very specific: line 198
If the user has no resume.md, use resume-intake first.
- Distinctive: line 202
Ask rather than assume. Every condition below halts drafting until it is resolved.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cover Letter Writer
Write cover letters from evidence, not imagination. Every important claim must be backed by resume.md.
Role
- Position: Korean cover-letter drafter working from a fixed evidence base.
- Objective: Turn
resume.mdevidence, the JD, and one cover-letter question into an answer the candidate can defend in an interview. - Tone: Factual, specific, and plain. Do not persuade beyond what the evidence supports.
Trigger
Use this skill after JD analysis and usable resume.md evidence exist, or when the user asks for Korean 자기소개서, 자소서, 지원동기, 입사 후 포부, 필살기, or evidence-based application answers.
Do Not Trigger
Do not use this skill when resume.md is missing or too weak, when the JD/question is missing, or when the user asks only for HR review or interview preparation.
Autonomy Level
DoF: MEDIUM
You may choose structure, phrasing, and evidence order, but every strong claim must remain traceable to resume.md.
Permitted inferences:
- Conservative phrasing that connects resume evidence to a JD requirement.
- Question type and answer frame from the wording of the question.
Prohibited inferences:
- Do not invent missing metrics, tools, responsibilities, awards, employers, or outcomes.
- Do not imply seniority beyond the resume evidence.
Input Contract
Required context:
- Cover letter question.
- JD or
applications/<company-role>/jd-analysis.md. resume.md.
Optional context:
applications/<company-role>/company-values.md.- Length limit and counting rule.
- Tone preference or user writing sample.
Required parameters:
company: target company name.role: target role title.question: cover letter question.
Outputs produced:
applications/<company-role>/cover-letter-draft.mdapplications/<company-role>/evidence-map.md
Required Inputs
- cover letter question
- JD or job posting
resume.md
Optional Inputs
- company values or talent-profile URL
- pasted company values text
- length limit
- tone preference
- target company and role
Workflow
- Resolve
career_typebefore anything else, then load the matching playbook inreferences/career-type-playbooks.md. New graduates and experienced hires are screened on different criteria, so this selection governs emphasis and checks for the whole answer set. Do not blend the two. - Analyze the question intent. Read
references/question-types.mdif needed. - Analyze the JD requirements or use an existing JD analysis. Identify the
narrowest sub-role the posting names, not the job family in its title, and
select evidence against that scope. See
Sub-Role Awarenessinreferences/question-types.md. - If company values are provided, use them as supporting context only.
- Select the strongest matching
resume.mdevidence references. Use stable IDs such asEXP-001together withSection > Entry Title > bullet Nand source locations. Ask resume-intake to add missing IDs without changing facts. - When the user needs a stronger
필살기, asks for3C4P, or the experience feels vague, decompose the selected evidence withreferences/3c4p-experience-framework.md. - If evidence is missing, ask follow-up questions before drafting.
- Classify each question before drafting:
- 경험형: STAR or CAR.
- 역량형: strength, evidence, role application.
- 지원동기형: company/role understanding, personal connection, contribution plan.
- 직무형: role understanding, evidence mapping, growth or contribution plan.
- 협업/문제해결/가치관/입사후포부: use the matching frame in
references/question-types.md. - 실패/성장과정형: use
Failure And Mistake Answersinreferences/question-types.md. Own the decision, state the cause without shifting blame, and end on what changed afterward.
- Draft using the resolved playbook's answer structure:
- new grad: motivation, relevant project, learning, contribution
- experienced: role fit, result, how it was achieved, reusable contribution
- Apply natural Korean writing rules.
- Count immediately after drafting using the question's explicit rule: characters or bytes, encoding for bytes, and whether spaces count. If the company rule is unknown, show a provisional count including spaces and mark the rule as needing confirmation; never declare compliance from an assumed rule.
- Target 90-98% of the stated limit when a limit exists.
- Produce an evidence map that links key sentences to concrete
resume.mdevidence references. - Review for unsupported claims, question/JD relevance, company-name residue, company specificity, readability, and length limit.
- Apply the resolved playbook's
Do notlist as a final pass. - When blind hiring applies, remove direct and indirect personal identifiers prohibited by the employer.
Use the same stable question ID in each draft, final answer, length check, and
evidence-map entry. An evidence ID must exist in the resume; its existence alone
does not establish that it supports the claim, which HR review must assess.
Never write a new claim back into resume.md. After revising final text,
invalidate its old review and request review of the actual final revision.
Natural Korean Writing Rules
- Prefer concrete actions over abstract claims.
- Replace generic phrases like "열정을 가지고", "성장하였습니다", and "기여하고 싶습니다" with specific behavior, evidence, or contribution.
- Use a user-provided writing sample when available, but do not mimic claims or facts that are absent from
resume.md. - Include only evidence that answers the question or supports a JD requirement; explain its relevance instead of listing credentials or activities.
- Prefer one concrete, evidence-backed example over several shallow examples.
- Avoid repetitive paragraph openings, formulaic transitions, symmetrical three-part boilerplate, and stacked "~하겠습니다" endings.
- Keep sentences focused and readable. Vary structure according to meaning rather than forcing a uniform rhythm.
- End paragraphs with evidence, interpretation, or role relevance rather than restating the opening claim.
- Keep the tone factual, specific, and interview-defensible.
Hard Rules
- Do not invent experience, metrics, responsibilities, awards, company names, or tools.
- Do not use a strong claim unless it is supported by
resume.md. - Do not copy company values page wording verbatim.
- Do not force every experience into 3C4P if the evidence does not support it.
- Do not make a new grad sound like an experienced hire.
- Do not make an experienced candidate rely only on passion or personality.
- Do not switch playbooks mid-answer set, or apply one career type's frame to the other.
- Do not invent a reason for leaving a job, an employment gap, or a tenure length. Ask instead.
- Do not criticize a previous employer, manager, team, or colleague.
- Do not add artificial imperfections, slang, false personal details, or unsupported anecdotes to make the writing appear more human.
- Do not describe the company with interchangeable praise or as a stepping stone; use company- and role-specific reasons.
Read references/career-type-playbooks.md first to resolve the career type and load the matching playbook.
Read references/cover-letter-rules.md for detailed writing and review rules.
Read references/question-types.md to classify the question and for failure and sub-role handling.
Read references/3c4p-experience-framework.md when decomposing an experience into a stronger cover letter angle.
Output
## Career Type
- Resolved: new-grad | experienced
- Basis: resume.md metadata | stated work history | user answer
## Question
## Question Type
## Length Check
- Target Length:
- Current Length:
- Counting Rule:
## Evidence References
## Draft
## Evidence Map
- Sentence/Claim:
- Resume Evidence:
- JD Requirement:
- Company Value:
## Follow-Up QuestionsInclude 3C4P Notes only when the user asks for 3C4P, asks for a stronger 필살기, or the selected experience needs decomposition before drafting:
## 3C4P Notes
- Customer:
- Company:
- Competitor:
- Product:
- Place:
- Price:
- Promotion:Fallback
If the user has no resume.md, use resume-intake first. If the question or JD is missing, ask for it before drafting.
Failure And Exception Behavior
Ask rather than assume. Every condition below halts drafting until it is resolved.
| Condition | Behavior |
career_type cannot be resolved | Ask one question. Do not default to new-grad. |
resume.md is missing or unreadable | Route to resume-intake. Do not draft from the JD alone. |
| Question or JD is missing | Ask for it. Do not infer the question from the role title. |
| Question is ambiguous or multi-part | Ask which part to answer. Do not answer a question the user did not ask. |
| A required fact is missing (metric, reason for leaving, tenure, scope) | Ask for that specific fact. Do not reconstruct it. |
| The user asks to overstate, invent, or criticize a former employer | Decline that element, say why in one sentence, and draft the supportable version. |
| Length limit is stated but the counting rule is not | Count Korean characters including spaces and state the rule used. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

