agentleFS
Sign inStart free
chanjalmechanjalme/claude-skills/skills/cover-letter-loop/SKILL.md

cover-letter-loop

Skill0 starsChanged 5 months agoMITView on GitHub

Use when Christian shares a job post and wants a cover letter. Triggers on 'cover letter', 'apply to this job', 'write a letter for this role', pasting a job description or job URL. Runs the full loop: pull resume facts + vault template, tailor to the post, output a .docx to ~/Downloads/[Company] - Cover Letter.docx, and log the application to the vault job tracker.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Load template: read vault 30 - Resources/Cover Letter Template.md (vault root …

    line 16
  2. Distinctive:

    No em dashes. No AI filler ("I am excited to leverage...").

    line 23
  3. Distinctive:

    Don't claim skills not in his actual history.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Loop

Closes the loop Christian currently does by hand. Job post in, finished document out, application logged.

Inputs needed

A job post (text or URL). If only a URL, fetch it. If key facts are missing (company, role title, salary), ask once as a numbered list.

Procedure

  1. Load template: read vault 30 - Resources/Cover Letter Template.md (vault root /Users/chanjalme/Documents/ClaudeProject/Obsedian/sample/smaple1). Follow its structure exactly.
  2. Load his facts: pull resume/experience from the vault (search "resume", "experience", "LinkedIn"). Do not fabricate experience.
  3. Tailor: map his real experience to the post's top 3-4 requirements. Match tone to the company. Filipino applicant, UTC+8, open to remote/PH roles.
  4. Write the .docx to ~/Downloads/[Company] - Cover Letter.docx using the docx skill.
  5. Log it: append to the vault job tracker (search "job", "applications", "tracker") a row: date, company, role, salary range, link, status=applied.

Style rules

  • No em dashes. No AI filler ("I am excited to leverage..."). Plain, direct, specific.
  • One page. Lead with the single strongest match to the role.
  • Don't claim skills not in his actual history.

Done check

Confirm: file written to the right path, tracker updated. Report both.

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.

Check your setup, free