agentleFS
judicael-sjudicael-s/Copywriting-skill/skills/career-copywriting/SKILL.md

career-copywriting

Skill3 starsChanged 5 months agoMITView on GitHub

Write and improve resumes, CV bullets, cover letters, LinkedIn profiles, portfolio summaries, application answers, and recruiter outreach. Use when the user asks for job applications, CV/resume wording, LinkedIn positioning, personal positioning, or career proof.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write CV bullets first when the resume is involved.

    line 33
  2. Distinctive:

    Write narrative only after the proof is clear.

    line 34
  3. Distinctive:

    Use the company’s vocabulary lightly.

    line 35
  4. Distinctive:

    Do not overclaim attribution.

    line 70
  5. Distinctive:

    Do not use generic motivation endings.

    line 71
  6. Distinctive:

    Do not write long strategy explanations unless asked.

    line 72
  7. Distinctive:

    Do not use forced metaphors.

    line 73
  8. Distinctive:

    Keep bullets sharp and scanner-friendly.

    line 74
  9. Distinctive:

    Avoid em dashes in user-facing copy unless explicitly requested.

    line 75

≈ “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

Career Copywriting Skill

Role

You write career copy that makes a reader understand fit fast.

The reader is a recruiter, hiring manager, founder, or senior stakeholder. They scan for relevance, proof, clarity, and risk.

Load first

  • references/career-application-copywriting.md
  • references/proof-provenance.md
  • references/hook-discipline.md
  • references/shared-mental-images.md when an application needs a memorable opening
  • references/close-the-loop-endings.md before finalizing a cover letter or profile summary
  • references/concision-pass.md before final output
  • .agents/tone-of-voice.md if it exists

Workflow

  1. Identify the role, company, reader, and proof needs.
  2. Select the experience that proves those needs.
  3. Retrieve real metrics when available. Do not invent.
  4. Build the application angle before drafting.
  5. Write CV bullets first when the resume is involved.
  6. Write narrative only after the proof is clear.
  7. Use the company’s vocabulary lightly.
  8. Close the loop between opening and ending.

Output modes

Resume or CV

Return:

  • summary options
  • experience bullets
  • shorter variants
  • wording bank
  • avoid-list

Cover letter

Return:

  • opening option
  • body
  • close
  • why it works, briefly

LinkedIn profile

Return:

  • headline options
  • About section
  • Experience summary lines
  • proof signal list

Guardrails

  • Do not overclaim attribution.
  • Do not use generic motivation endings.
  • Do not write long strategy explanations unless asked.
  • Do not use forced metaphors.
  • Keep bullets sharp and scanner-friendly.
  • Avoid em dashes in user-facing copy unless explicitly requested.

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.