Career copywriting
Skill judicael-s/Copywriting-skill/skills/career-copywriting
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.From its SKILL.md
npx -y skills add judicael-s/Copywriting-skill --skill career-copywritingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.0 KB, 372 tokens by cl100k_base, as published. Nobody here has run it
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.mdreferences/proof-provenance.mdreferences/hook-discipline.mdreferences/shared-mental-images.mdwhen an application needs a memorable openingreferences/close-the-loop-endings.mdbefore finalizing a cover letter or profile summaryreferences/concision-pass.mdbefore final output.agents/tone-of-voice.mdif it exists
Workflow
- Identify the role, company, reader, and proof needs.
- Select the experience that proves those needs.
- Retrieve real metrics when available. Do not invent.
- Build the application angle before drafting.
- Write CV bullets first when the resume is involved.
- Write narrative only after the proof is clear.
- Use the company’s vocabulary lightly.
- 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most marketing audience skills give in 372 tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- Identify role, company, reader, and proof needs
- Select experience that proves those needs
- Build application angle before drafting
- Write CV bullets first when resume is involved
- Write narrative only after proof is clear
- Use company vocabulary lightly
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.