agentleFS
ARPeeketiARPeeketi/claude-resume-kit/.claude/skills/make-cl/SKILL.md

make-cl

Skill234 starsChanged 8 months agoMITView on GitHub

Generate a tailored cover letter from an existing session file and finished resume/CV

The file

Show its rules and text

We split this skill into the rules it gives an agent

25 rules. About 0 are common, 16 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

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

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

    Read config.md Provenance Flags before generating any content.

    line 21
  2. Very specific:

    Use the email from config.md Personal Info in all outputs

    line 23
  3. Distinctive:

    If the user provides feedback, corrections, or suggestions at any point:

    line 31
  4. Distinctive:

    If it affects already-written content: fix it, re-verify word count and anti-patterns

    line 33
  5. Distinctive:

    If it changes the framing: note the change in session file Framing Strategy

    line 34
  6. Distinctive:

    Never restart — resume from current position

    line 35
  7. Very specific:

    Read resume_builder/reference/shared_ops.md for session startup and file derivation.

    line 41
  8. Distinctive:

    Read CLAUDE.md — check Active Sessions and KB Corrections

    line 44
  9. Very specific:

    Read config.md — load Provenance Flags, email, role types

    line 45
  10. Very specific:

    If CL Status is DONE → "CL already generated.

    line 48
  11. Very specific:

    If CL Status is IN_PROGRESS → check if CL .tex exists, offer to resume or regenerate

    line 49
  12. Very specific:

    If Resume Status is not DONE → "Resume not yet generated.

    line 50
  13. Distinctive:

    If CL Status is PENDING → proceed to Phase 1

    line 51
  14. Distinctive:

    Read in this order:

    line 57
  15. Very specific:

    All significance files from resume_builder/support/significance_*.md

    line 63
  16. Very specific:

    Update session file Status: Cover Letter: IN_PROGRESS

    line 65
  17. Distinctive:

    Use significance files for field-context depth (NOT resume bullet text)

    line 81
  18. Distinctive:

    Use session file CL hooks and "why them" angle

    line 82
  19. Distinctive:

    Ensure every major claim is traceable to a resume/CV bullet

    line 83
  20. Distinctive:

    Do NOT present the CL draft to the user until all hooks are verified or flagged.

    line 103
  21. Distinctive:

    Use Read tool to view compiled PDF.

    line 113
  22. Distinctive:

    Add CL to Output Files

    line 125
  23. Distinctive:

    Add Next Critique command

    line 127
  24. Distinctive:

    If user requests changes: apply them, re-compile, re-verify.

    line 135
  25. Distinctive:

    If user approves: update Status, present next command.

    line 136

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

/make-cl

User input: $ARGUMENTS

Parse $ARGUMENTS:

  • Session file path (e.g., output/Acme/session_acme_engineer.md) → read that session file
  • Session name (e.g., acme_engineer) → find session file via shared_ops.md derivation
  • Empty → check CLAUDE.md Active Sessions for latest

Safety Rules (ALWAYS ENFORCED)

Accuracy > Relevance > Impact > ATS > Brevity

Read config.md Provenance Flags before generating any content. Verify every claim against that table.

  • Use the email from config.md Personal Info in all outputs
  • CL deepens what resume presents — never introduces new claims not traceable to resume bullets
  • Source field context from resume_builder/support/significance_*.md files

User Input During Execution

If the user provides feedback, corrections, or suggestions at any point:

  1. Acknowledge the input immediately
  2. If it affects already-written content: fix it, re-verify word count and anti-patterns
  3. If it changes the framing: note the change in session file Framing Strategy
  4. Never restart — resume from current position

Startup

Read resume_builder/reference/shared_ops.md for session startup and file derivation.

Then:

  1. Read CLAUDE.md — check Active Sessions and KB Corrections
  2. Read config.md — load Provenance Flags, email, role types
  3. Find and read the session file
  4. Recovery check:
    • If CL Status is DONE → "CL already generated. Run /critique next." Show next command. Stop.
    • If CL Status is IN_PROGRESS → check if CL .tex exists, offer to resume or regenerate
    • If Resume Status is not DONE → "Resume not yet generated. Run /make-resume first." Stop.
    • If CL Status is PENDING → proceed to Phase 1

Phase 1: Load Context

Read in this order:

  1. Session file — specifically: Company Context, Cover Letter Plan, Framing Strategy, ATS Keywords
  2. Finished resume/CV .tex — path from session file Output Files. Read to understand what CL must complement.
  3. resume_builder/reference/cl_reference.md — CL format rules, paragraph templates, anti-patterns
  4. resume_builder/support/ai_fingerprint_rules.md — Banned words, structural rules (CLs are most vulnerable)
  5. The matching bundle from session file role type → resume_builder/bundles/bundle_[role_type].md — Section 5 (Cover Letter)
  6. All significance files from resume_builder/support/significance_*.md

Update session file Status: Cover Letter: IN_PROGRESS

Progress: "Loading CL context — [company], [role type] bundle, [institution type]..."


Phase 2: Generate Cover Letter

Read resume_builder/templates/coverletter_template.tex.

Detect institution type from session file Cover Letter Plan:

  • Industry → 3 paragraphs, 250-300 words
  • National Lab → 4 paragraphs, 350-450 words
  • Academic → 4 paragraphs, 350-450 words (postdoc) or 450-650 words (faculty)

Generate CL following cl_reference.md paragraph structure:

  • Use significance files for field-context depth (NOT resume bullet text)
  • Use session file CL hooks and "why them" angle
  • Ensure every major claim is traceable to a resume/CV bullet
  • Open with a specific reference to their work — no generic openers
  • Weave credentials into body paragraphs, not closing

Save to output/<FolderName>/e2e_<name>_cover_letter.tex

Progress: "Writing [institution type] cover letter — [N] paragraphs, targeting [N] words..."

CL Hook Verification Gate (MANDATORY before presenting to user)

Web-search every hook used in the CL:

  • Academic: PI name + cited paper/research area
  • National Lab: named program, thrust area, or group publication
  • Industry: product, technology, or company news referenced

Present evidence as:

Claim: [what the CL says] → Evidence: [what the search found] → Source: [URL]

Flag any unverified item: "UNVERIFIED — please confirm"

Do NOT present the CL draft to the user until all hooks are verified or flagged.


Phase 3: Compile & Verify

pdflatex -interaction=nonstopmode -output-directory=output/<FolderName> output/<FolderName>/e2e_<name>_cover_letter.tex

Use Read tool to view compiled PDF. Verify:

GateCheckIf FAIL
Word countIndustry 250-300, Lab/Academic 350-450Trim/expand
Page countResume package: 1 page. CV package: 1-2 pagesAdjust content
Page fill1pg: well-filled. 2pg: page 2 >= half filled before signatureAdjust
Anti-patternsNo generic opener, no defensive framing, no credential dumpRewrite
Package cohesionCL claims traceable to resume bullets, no contradictionsFix
CompileClean pdflatexFix LaTeX errors

Update session file:

  • Add CL to Output Files
  • Status: Cover Letter: DONE
  • Add Next Critique command

Progress: "Compiled — 1 page, 278 words. Package cohesion verified."

>>>>>> MANDATORY STOP — DO NOT PROCEED <<<<<<

Present: CL summary (word count, page count, key hooks used). You MUST wait for the user's explicit text response before continuing.

If user requests changes: apply them, re-compile, re-verify. Update session file. If user approves: update Status, present next command.

Do NOT trigger file organization — that happens after /critique approval.

"Cover letter done. Next steps:

  1. /clear
  2. [exact /critique command with session file path]"

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.