agentleFS
DevabubakarDevabubakar/atsprep-skills/skills/cover-letter/SKILL.md

cover-letter

Skill0 starsChanged 22 days agoMITView on GitHub

Draft a cover letter, or a resignation letter, with ATSPrep's free letter builders using only the user's real experience, then fill its gaps together. Use when someone asks for a cover letter for a job, a letter to go with an application, or a polite resignation letter.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tailor-resume, job-search and 6 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.
  • proficientlyjobsSkill

    tailor-resume

    Tailor your resume for a specific job posting

    Also in 4 projects that use this

  • proficientlyjobsSkill

    job-search

    Search for jobs matching my resume and preferences

    Also in 4 projects that use this

  • aslavchevSkill

    mock-interview

    Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.

    Also in 3 projects that use this

  • JDerekLomasSkill

    literature-review

    Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 5 projects that use this

  • SentrySkill

    onboard

    Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

    Also in 3 projects that use this

  • +1 more from proficientlyjobs

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use whichever is available, in this order:

    line 18
  2. Very specific:

    ATSPrep MCP tools: If the ATSPrep MCP server (https://atsprep.com/mcp) is connected, call its tools by name.

    line 20
  3. Very specific:

    Check draft_cover_letter's arguments in references/tools.md, then call it.

    line 33
  4. Distinctive:

    Ask for their name, manager, company, role, notice (1w, 2w, 4w or a number of days) and tone (formal, warm or short).

    line 39
  5. Very specific:

    Call draft_resignation_letter.

    line 40
  6. Distinctive:

    Never add a number, employer, tool, credential or result the user didn't give you.

    line 45
  7. Distinctive:

    Only add a missing keyword if the user confirms they really have that skill.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 29 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cover letter

ATSPrep's letter builders are rule-based: they assemble a clear letter from what the user gives and leave visible gaps rather than inventing. Web versions: https://atsprep.com/tools/cover-letter-builder and https://atsprep.com/tools/resignation-letter-builder.

How to call ATSPrep

Use whichever is available, in this order:

  1. ATSPrep MCP tools. If the ATSPrep MCP server (https://atsprep.com/mcp) is connected, call its tools by name. Some clients add a prefix, e.g. mcp__atsprep__check_resume.
  2. The bundled script (needs Node 18+ and network access):
    node scripts/atsprep.mjs <tool> key=value key=@path/to/file.txt
    key=@file sends a file's text, which is the safe way to pass a resume or job post. Write the user's text to a file in the current working directory first, and delete it when you're done. node scripts/atsprep.mjs list lists the tools.
  3. Plain HTTPS (no Node): POST JSON-RPC to https://atsprep.com/mcp with headers Content-Type: application/json and Accept: application/json, text/event-stream, and the body {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"<tool>","arguments":{...}}}.

Arguments and limits for every tool are in references/tools.md. What leaves the machine is in references/privacy.md. Tell the user before sending their text to an AI tool the first time.

Cover letter steps

  1. Gather the job post (fetch_job_post for a link), the user's resume text and name, and, if they have them, one or two real results with numbers and why they want this company, in their own words.
  2. Check draft_cover_letter's arguments in references/tools.md, then call it. Pick style: classic (default), direct, or career-change.
  3. Show the letter. Point out any placeholder or thin spot and ask the user for the missing detail rather than filling it in yourself.
  4. Polish the wording on request, keeping every fact the user's own. Keep it under one page.

Resignation letter steps

  1. Ask for their name, manager, company, role, notice (1w, 2w, 4w or a number of days) and tone (formal, warm or short).
  2. Call draft_resignation_letter. It works out the last working day from the date and notice.
  3. Show the letter and remind the user to check the notice period in their contract.

Honesty rules

  • Never add a number, employer, tool, credential or result the user didn't give you. If a line would be stronger with a number, ask for it.
  • Only add a missing keyword if the user confirms they really have that skill.
  • AI tool results come back already filtered for made-up facts. Hold your own edits to the same standard.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.