Claude skills for recruiters: build once, reuse forever
TL;DR
A skill is a task you have taught Claude once, saved so you can run it again with one command. It beats a saved prompt because it carries your criteria and your exceptions, not just your words. There are now two ways to build one: write it out, or record your screen while you do the task and narrate why. Skills also save on your plan, because you stop re-pasting long instructions and a skill only loads when used. Start with the task you have already done three times.
Every recruiter using AI has a prompt graveyard. A note somewhere with a dozen long instructions, half of them outdated, all of them needing a tweak before they work. You paste, you edit, you paste again. It is better than nothing and it is still manual.
A skill fixes that. It is the difference between explaining your process every Monday and simply saying "run my weekly report".
New to the tool itself? Start with what is Claude Cowork.
What is a Claude skill?
A skill is a saved, reusable set of instructions for a specific task. Once it exists, Claude recognises when it applies and runs it. You stop describing the job and start naming it.
Where a prompt says what to write this once, a skill says how this task is always done: which files to look at, what the output should look like, what to do about the edge cases, and where the result goes.
| Saved prompt | Skill | |
|---|---|---|
| What it holds | Wording | A whole way of doing the task |
| How you use it | Copy, paste, edit | Name it, or let Claude recognise the request |
| Consistency | Depends on which version you pasted | Same standard every run |
| Sharing | Send someone a block of text | Hand over the skill itself |
| Cost to your plan | You re-send it every time | Loads only when it is used |
That last row is worth a moment. Long pasted instructions travel with every message in a conversation, and Cowork already uses more of your plan than a chat because it does more work. A skill is leaner: you are not retyping the instruction, and it only loads its content when it is actually needed.
Why skills matter more for recruiters than for most professions
Recruitment runs on judgment that never gets written down. How you weigh three years of the right experience against five of the nearly-right. Which comments in an intake call actually matter. When to push a hiring manager and when to let it go.
That knowledge normally lives in your head and leaves with you. A skill is the first practical way to put a piece of it somewhere reusable. Not the relationship part, that stays yours, but the repeatable reasoning around it.
It is also the difference between renting a tool and owning your setup. A skill you built keeps working regardless of which vendor is fashionable next year.
How to build a skill by writing it
The classic route, and still the most precise.
- Pick a task you have already done a few times, so you know its edge cases.
- Write out how you do it: the input, the steps, the output format, and the rules that apply.
- Name the exceptions explicitly. "If no salary is mentioned, flag it rather than guessing" is exactly the kind of line that makes a skill trustworthy.
- Test it on a real case, then fix whatever came back wrong.
- Save it and use it for a week before you consider it finished.
The common mistake is describing the steps instead of the outcome and the rules. Write it as if you were briefing a capable new colleague, not programming a machine.
How to build a skill by recording your screen
There is now a second route, and for many recruiters it is the easier one: Record a skill. You record your screen while you do the task and talk out loud, and Claude turns that into a written skill.
Why this matters: most of how you work is not in your head as a neat list of steps, it is in your hands. Ask an experienced colleague how she builds the monthly report and you get an answer full of holes. Watch her do it and the real method appears.
How it works in practice:
- In the Cowork desktop app, use the plus button and choose Record a skill.
- Read the warning, then start recording.
- Do the task exactly as you always would, and narrate the why, not just the clicks. "I skip this column, because the administration fills it in." That reasoning is what makes the result smart.
- Click done. Claude processes the recording and drafts the skill in plain language.
- Read the draft critically, fix what is off, then save it.
Two honest notes. It is available on paid plans in the desktop app and rolling out in stages, so update your app if you do not see it yet. And a screen recording captures everything on your screen, so close unrelated tabs, never type a password while recording, and keep candidate personal data out of it. More on that boundary in Claude Cowork, the GDPR and the EU AI Act.
Which route should you use?
| Situation | Better route |
|---|---|
| The task lives in your hands, lots of small judgment calls | Record it |
| The task spans tools with no connector, lots of clicking | Record it |
| You need precise rules and exact output formatting | Write it |
| The task touches candidate or confidential data | Write it, keep it off the recording |
| A connector already exists for the app | Use the connector, not a recording of you clicking |
Which skills should a recruiter build first?
Start with what repeats. In practice recruiters get the most out of these:
- Company research before a business development call
- Turning intake notes into a structured vacancy brief
- The weekly client update from your own notes
- Outreach sequences that sound like you rather than a template
- Interview preparation: questions, scorecards, and a guide from one brief
- Candidate status updates that still get your final check
You do not have to build all of these yourself. The AI Recruitment Engineer Starter includes a plugin with ten ready-made recruitment skills covering the full hiring lifecycle, plus research connectors with no API keys to set up, and it teaches you to build and adapt your own. About four hours, self-paced, 297 euro.
The moment it clicks
Most recruiters expect the impressive first run to be the turning point. It usually is not. The turning point is the fourth Monday, when the report is already sitting there and you did not think about it once.
That is what owning a piece of your own setup feels like. Not magic, just work that stopped coming back to you.
For the tasks worth turning into skills first, see seven recruitment tasks to hand to Claude Cowork.
Frequently asked questions
What is a Claude skill? A saved, reusable set of instructions for a specific task. Once saved, you run it with a single command instead of pasting a long prompt.
What is Record a skill? A feature where you record your screen while doing a task and narrate what you are doing and why. Claude turns the recording into a written, reusable skill. It is on paid plans in the desktop app and rolling out in stages.
Is it safe to record my screen? Only if you prepare. A recording captures everything visible, so close unrelated tabs and chats, never type a password, and keep candidate personal data and confidential material out of the recording.
Do skills save tokens? They help in two ways: you stop re-pasting a long instruction every time, and a skill only loads its content when it is actually used rather than sitting in every conversation.
Can I share a skill with my team? Skills are portable, so you can hand one to a colleague rather than sending them a block of prompt text. That is also how a team ends up working to the same standard.