The 8 Best Claude Code Skills for Freelancers

By Skill Index Editorial · May 29, 2026

Freelancing economics are unforgiving in a way salaried work hides. Every hour on a misunderstood scope is an hour the client will not pay for. Every proposal that loses on framing is a month of runway gone. Every unsent follow-up is a deal that goes to the freelancer who did send one. The eight skills below address the places solo operators most consistently bleed money — scoping, proposing, prospecting, following up, negotiating, billing, tracking deliverables, and turning client calls into briefs. Each is a real, verified Claude Code skill from a plugin with public commit history and real star counts.

From the myclaude plugin (2,676 stars). An interactive Product Owner skill that walks a vague client brief into a precise PRD — user stories, acceptance criteria, edge cases. The failure mode it removes is the most expensive one in freelance work: starting implementation against a scope the client and the freelancer secretly disagree on. The freelancer thinks "a contact form"; the client thinks "a contact form with HubSpot sync, GDPR consent capture, double opt-in, and a Slack notification." The PRD catches the gap on day one instead of day twenty-one, when the budget is half-gone and someone has to eat the difference.

When to use: on every new project before the contract is signed, and any time a client says "just a quick thing." Run it as a paid discovery call — an hour of structured requirements interrogation is the cheapest insurance against scope creep that exists, and the PRD becomes the scope-of-work attachment to the proposal.

From the claude-skills plugin (13 stars, verified). Writes RFP responses, project proposals, business cases, and partnership agreements with the structure that wins them — problem framing, proposed approach, deliverables, timeline, pricing, terms. The hidden value is not writing speed but consistency. Most solo freelancers write each proposal from a blank page and accidentally leave out a different section every time, which is why their close rate wobbles. The skill enforces the same skeleton every time, so the variable that determines whether you win is the offer, not whether you remembered the assumptions section.

When to use: on every proposal over the "just send a quote" threshold, especially the ones where there is real competition. Run it after product-requirements so the proposal has a real scope-of-work to attach, and after pricing the project from the time estimate in your xlsx tracker.

From the agent-skills plugin (21 stars, verified). Writes cold emails that actually get replies using proven frameworks (AIDA, PAS, BAB) and enforces the boring rules that separate inbox from spam folder — 50 to 125 words, one ask, one CTA, no opening pleasantries. Cold outreach is the highest-leverage pipeline-building activity a freelancer can do, and also the one most freelancers refuse to do because the blank page is so demoralising. The skill removes the blank page and leaves only the part that requires your taste — picking the right prospect and the right hook.

When to use: on the daily or weekly outreach block you have hopefully already scheduled. Batch ten prospects, run the skill on each, send the same day. Pair it with the solo founders skill stack for the broader go-to-market workflow, and queue the follow-up skill behind every send.

Also from the agent-skills plugin. The companion to cold-email: writes follow-up sequences that re-engage without becoming annoying, using the finding that roughly 42% of replies come from a follow-up rather than the original message. The freelancer who writes one cold email and gives up captures the cheapest third of the pipeline; the freelancer with a five-touch sequence (3 days, 7 days, 14 days, 30 days, breakup) captures the rest. The skill nails the cadence, the tone shift on each touch, and the exit line on the breakup so you stop looking desperate and start looking selective.

When to use: the moment a cold email goes unanswered, on every "I'll get back to you next week" that does not, and on every proposal quiet for more than five business days. Run the breakup on every prospect older than thirty days — half reply "wait, do not close the file," and the other half free up the headspace you were spending on hoping.

Also from claude-skills. Writes the harder client emails — the negotiation reply, the scope-creep pushback, the deadline-slipped apology, the revised-timeline note after Wednesday's surprise requirement. These are the emails freelancers spend an hour writing and a worse hour rewriting because the stakes feel high. The skill produces a first draft that is firm without being defensive, clear without being curt, and friendly without being a pushover — not the version you send, but the version that breaks the blank-page loop and gets you to the one you do send in ten minutes instead of ninety.

When to use: on every client email you are dreading writing — the dread is the signal. Especially valuable for scope-creep responses, rate-increase conversations, late-payment reminders, and the polite declines that protect your calendar.

From the skills plugin (142,071 stars). Reads, edits, and creates .xlsx and .csv files — formulas, formatting, charts. For a freelancer, this is the spreadsheet that runs the business: the time tracker, the project P&L (hours x rate minus expenses), the invoicing workbook (line items, totals, VAT, payment terms), and the pipeline tracker. The skill turns the "I should really build a proper spreadsheet for this" thought into an actual spreadsheet built in the time it would have taken to add the same thought to your todo list.

When to use: at the end of every project (build the P&L so you know whether the next project at that price is worth taking), at the start of every month (build the invoicing workbook so the numbers go out on the first), and any time you find yourself doing freelance accounting in your head. Pair it with the data analysts skill stack if your project work has analytical deliverables.

Also from claude-skills. Tracks action items with owners, deadlines, status updates, and escalation workflows. For a freelancer this is the scope-creep guard — every "can you also just" and every "while you are in there" lands in the tracker with the client's name on it and an explicit decision: in-scope, out-of-scope billable (raise a change order), or out-of-scope unbillable. The unspoken "just one more thing" that adds up to thirty hours becomes a visible line item that costs $4,500, which the client can either approve or withdraw.

When to use: on every project from day one — set up the tracker before the first deliverable, share it with the client, refer to it in every status update. The tracker is also where you log the deliverable-QA checklist before sending work back: spec satisfied, edge cases tested, copy proofed, deployment verified. Pair it with the product managers skill stack if you run multi-resource projects with subcontractors.

Also from claude-skills. Summarises meetings from transcripts — key decisions, action items, owners, deadlines, and the follow-up emails ready to send. For a freelancer, every client call is half-work, half-evidence: the work is agreeing what to do, the evidence is the written record of who agreed to what when the inevitable scope dispute happens three weeks later. The skill produces both in one pass, so the recap email lands in the client's inbox by end of day with decisions captured exactly as you understood them — and any misunderstanding gets caught while it is still cheap to fix.

When to use: on every client call longer than fifteen minutes — record (with permission), transcribe, feed the transcript to the skill, send the recap within four hours. The four-hour window matters because that is when the client's memory of the call still matches yours; after twenty-four, every detail is contested. Pair it with action-tracker above so the recap items flow directly into the scope-and-deliverables queue.

How to install

The skills live in four plugins (myclaude, claude-skills, agent-skills, skills), so install is a four-marketplace operation — Skill Index has the exact install command on each skill detail page with a copy button. The highest-ROI sequence for a freelancer's first structured quarter: start with product-requirements so every project begins with a real scope, then proposal-writer so the price you quote is defended by the same document. Add xlsx so hours and P&L get tracked from day one. Layer in cold-email and follow-up so the pipeline becomes a daily habit instead of a quarterly panic. Use email-composer when the next hard client email lands, action-tracker on the next project that smells like it might creep, and meeting-summarizer on the next client whose calls keep ending with both sides confused. Pair the workflow with deep-work blocks via focus.thicket.sh and quick-share QR codes for client portfolios via qr.thicket.sh, and the months stop being a treadmill of underquoted projects and start being a business with margin.

Frequently Asked Questions

Which Claude Code skill should a freelancer install first?

Start with product-requirements from the myclaude plugin (2,676 stars). It is an interactive Product Owner skill that walks a vague client brief into a precise PRD with user stories, acceptance criteria, and edge cases. The failure mode it removes is the single most expensive one in freelance work — starting implementation against a scope the client and the freelancer secretly disagree on. The freelancer thinks 'a contact form' while the client thinks 'a contact form with HubSpot sync, GDPR consent capture, double opt-in, and a Slack notification.' The PRD catches the gap on day one instead of day twenty-one when the budget is already half-gone. Use it on every new project before the contract is signed, ideally as a paid discovery call where the PRD itself is the deliverable.

What is the best Claude Code skill for writing client proposals?

Use proposal-writer from the claude-skills plugin. It writes RFP responses, project proposals, business cases, and partnership agreements with the structure that wins them — problem framing, proposed approach, deliverables, timeline, pricing, and terms. The hidden value is not the writing speed but the consistency. Most solo freelancers write each proposal from a blank page and accidentally leave out a different section every time, which is why their close rate wobbles unpredictably. The skill enforces the same skeleton every time, which means the variable that determines whether you win is the offer, not whether you remembered the assumptions section. Use it on every proposal over the 'just send a quote' threshold, especially ones where there is real competition.

How do freelancers do cold outreach without sounding spammy?

Use cold-email from the agent-skills plugin. It writes cold emails using proven frameworks (AIDA, PAS, BAB) and enforces the boring rules that separate inbox from spam folder — 50 to 125 words, one ask, one CTA, no opening pleasantries, no 'I hope this finds you well.' Cold outreach is the highest-leverage pipeline-building activity a freelancer can do and also the one most freelancers refuse to do because the blank page is so demoralising. The skill removes the blank page and leaves only the part of the work that requires your taste — picking the right prospect and the right hook. Batch ten prospects on your daily or weekly outreach block, run the skill on each, send same-day, and queue the follow-up sequence behind each.

How important are follow-up emails for freelance sales?

Very — roughly 42% of replies come from a follow-up rather than the original message, which is why the follow-up skill from agent-skills is the companion to cold-email rather than a separate workflow. The freelancer who writes one cold email and gives up captures the cheapest third of the pipeline. The freelancer with a five-touch sequence (3 days, 7 days, 14 days, 30 days, breakup) captures the rest. The skill writes the sequence with the right cadence, the right tone shift on each touch, and the right exit line on the final one. Use it the moment a cold email goes unanswered, on every 'I will get back to you next week' that does not come back, and on every stalled proposal older than five business days.

How do I handle scope-creep conversations with clients?

Use action-tracker from the claude-skills plugin as the scope-creep guard. Every requested change, every 'can you also just' ask, and every 'while you are in there' addition lands in the tracker with the client's name on it and an explicit decision — in-scope (do it), out-of-scope billable (raise a change order), or out-of-scope unbillable (politely decline). The tracker turns the silent erosion of the project margin into a visible queue the client can see, which is the only way scope-creep conversations actually get had. The unspoken 'just one more thing' that adds up to thirty hours becomes a spreadsheet line that costs $4,500, which the client can either approve or withdraw. Pair it with email-composer for the actual conversation.

What is the best Claude Code skill for invoicing and time tracking?

Use xlsx from the skills plugin (142,071 stars). It reads, edits, and creates .xlsx and .csv files with formulas, formatting, and charts. For a freelancer this is the spreadsheet that runs the business — the time tracker (one row per hour, one column per project), the project P&L (hours x rate minus expenses), the invoicing workbook (line items, totals, VAT, payment terms), and the pipeline tracker (prospects, stage, expected close date, expected value). The skill turns the 'I should really build a proper spreadsheet for this' thought into an actual spreadsheet built in the time it would have taken to write the same thought in your todo list. Build the P&L at the end of every project and the invoicing workbook at the start of every month.

How do I turn client kickoff calls into briefs and recap emails?

Use meeting-summarizer from the claude-skills plugin. It summarises meetings from transcripts into key decisions, action items, owners, deadlines, and the follow-up emails ready to send. The kickoff call and every subsequent client meeting is half-work, half-evidence — the work is agreeing what to do, the evidence is the written record of who agreed to what when the inevitable scope dispute happens three weeks later. The skill produces both in one pass, so the recap email lands in the client's inbox by the end of the day with decisions captured exactly as you understood them, and any misunderstanding gets caught while it is still cheap to fix. Send within four hours — that is the window where the client's memory of the call still matches yours.

How do I write hard client emails without spending an hour on each one?

Use email-composer from the claude-skills plugin. It writes the harder client emails — the negotiation reply, the 'we need to talk about scope' email, the apology when a deadline slipped, the 'here is the revised timeline' note when the client added a requirement on Wednesday for the Friday deadline. These are the emails freelancers spend an hour writing and a worse hour rewriting because the stakes feel high and the wording feels wrong. The skill produces a first draft that is firm without being defensive, clear without being curt, and friendly without being a pushover. The draft will not be what you send, but it breaks the blank-page loop and gets you to the version you do send in ten minutes instead of ninety. Use it on every client email you are dreading — the dread is the signal the email matters.

How to install

Frequently Asked Questions

More from the Skill Index