Guide
A freelancer's AI skill library: one set of methods, every client
A freelancer gets the most from AI with a small skill library, split in two. Method skills hold how you work: how you write a brief, a proposal, a monthly report. Each is written once, says nothing about any client, and works for every client. Client skills, or one project per client, hold that client's voice, products and rules, named with the client's name, and you load only that one for their work. That split keeps one client's details out of another's drafts, and it means a better method helps every client at once. The skills use the open SKILL.md format, so they work in Claude and in the other tools that read it, and you can share one skill with a client without handing over the rest.
Short answer
- Method skills: how you work, no client facts.
- Client skills or projects: one per client.
- Names that sort: method-…, client-….
- Share one skill, never the library.
A worked example: a copywriter's library
Illustration: a made-up business. A freelance copywriter with four retainer clients keeps seven skills:
| Skill | Kind | Holds |
|---|---|---|
| method-brief | Method | The questions she asks before any piece |
| method-proposal | Method | How she scopes and prices a project, from her rate card |
| method-monthly-report | Method | Results against targets, next month's plan |
| client-harbour-voice | Client | Harbour Roasters' voice guide, product facts, banned words |
| client-fernway-voice | Client | Fernway's voice guide and legal lines |
| client-calder-voice, client-tidewell-voice | Client | The same, for the other two |
One method skill, in part:
---
name: method-monthly-report
description: Writes a client's monthly report from the freelancer's notes: results against the agreed targets, work done, what the client must do, next month. Use when asked for a monthly report or client update.
---
1. Results first, against the targets in the client skill or the notes. Only numbers given.
2. Work done: three bullets at most.
3. What the client must do, with a date.
4. Next month: three bullets at most.
Checks: no client name or fact that isn't in this client's skill or notes.
When Harbour asked to use the voice skill in its own Claude Team account, she shared client-harbour-voice and nothing else. She tests each method skill on two clients' real notes before trusting it with a third.
Build yours
- List what you repeat for every client; each becomes a method skill.
- Strip client facts out of the method; they go in that client's skill or project.
- Name them so they sort: method-…, client-….
- Test a method skill on two clients before using it for all.
- Share single skills with clients who ask; keep the library yours.
Next step: selling the skills
Some clients will want to keep using a skill after the work ends. Giving clients an AI assistant that runs on their own ChatGPT or Claude covers how agencies and freelancers do that. For the file itself, see the SKILL.md format explained.
Skills for this
- AI practiceTurn a prompt into a skillTurns a prompt that works into a skill the whole team can reuse, with a valid name, a when-to-use description, steps, an output template, an example, and checks.
- Operations and adminWeekly client status reportWrites a one-screen weekly client report: status with a reason, what you need from the client, done, next, and metrics against target.
- SalesProposal check before you sendChecks a proposal or quote before it reaches the buyer: their problem in their words, scope, price, next step, risk reversal and names.
- MarketingBrand voice guide and rewriteExtracts a voice guide from 3 to 5 sample texts (traits with do and don't pairs, a word list, mechanics) and rewrites a draft in it.
Questions
Should a freelancer build an AI skill library?
Yes, a small one. Write each method you repeat for every client (how you write a brief, a proposal, a monthly report) as one skill, once. Keep each client's facts apart, in a project or a client skill, so one client's details never leak into another's work.
How do I keep client work separate in my AI?
Split method from context. Method skills hold how you work and nothing about any client. Each client's voice, products and rules go in that client's own project or skill, named with the client's name, and you load only that one for their work.
Can I share a skill with a client?
Yes, one skill at a time. Share the client's own skill, or a method skill you're happy for them to keep; don't hand over the whole library. The SKILL.md format works in Claude and other tools, so the client can use it in theirs.
AI skill
Have your AI turn a prompt that works into a skill your team can reuse
Put this skill in AI Skill Pod and everyone on your team gets it in their Claude, Cursor or ChatGPT (Pro, Business, Enterprise): one invite link, free to start. Turn a prompt into a skill turns a prompt you already use into a skill for your library: a valid name, a when-to-use description in your own words, steps with your rules, an output template, one example and checks, tested on real work.
14 days free · No card needed
Sources
- Agent Skills specification — a folder with SKILL.md; name up to 64 characters, matching the folder; description up to 1,024 (read 2026-11-05)
- Claude Help Center: Use skills in Claude — "Skills are available for users on Free, Pro, Max, Ultra, Team, and Enterprise plans"; code execution on (read 2026-11-05)
- Gemini Apps Help: About the transition from Gems to skills — skills made on other platforms can be imported by uploading their SKILL.md files (read 2026-11-05)