I bill clients as a freelancer, and I noticed I was rewriting the same Claude Code prompts every week: draft an invoice, write a proposal from a job post, turn messy meeting notes into a summary + action items, check a contract for risky clauses before signing.
So I packaged them as reusable Claude Code skills — plain-text files you drop into your skills folder, no API keys, no subscriptions:
-
/invoice— describe the work in plain English, get a polished invoice back (HTML + Markdown) in seconds -
/proposal— paste a job post or call notes, get a tight, client-ready proposal -
/meeting— paste messy notes or a transcript, get a summary + action-item table + a follow-up email draft -
/redline— paste a contract or SOW, get the risky clauses flagged in plain English before you sign -
/outreach— a personalized 3-touch cold email/LinkedIn sequence for a prospect -
/scopecheck— paste a new client ask against your original scope, get a verdict and a ready-to-send response -
/setrate— turn a target income into an hourly rate or project price, with the math shown
Example of what /redline actually outputs on a real (anonymized) contract clause:
Flagged: Unlimited revisions clause (Section 4.2)
"Contractor shall provide unlimited revisions until Client is fully satisfied" has no cap on rounds or timeline — this is the single most common freelance scope-creep trap. Suggested response: "Happy to include up to 2 rounds of revisions per deliverable; additional rounds billed at the hourly rate."
That's the kind of thing that's obvious once you see it, but easy to miss when you're reading a contract for the third time at 11pm.
I made /invoice free to try on its own. The full 7-skill pack is $27 (one-time, not a subscription) — Claude Code Freelancer Pack.
If you're a freelancer/consultant using Claude Code for actual client work: what's the admin task you'd want automated that isn't on this list? Genuinely collecting ideas for what to build next.
Top comments (1)
client review is the admin step i'd add. Claude can draft the proposal or redline, but after i send it out the notes come back as email snippets, screenshots, or just “section 4”. then i have to map each one back before the next run.
do your proposal/redline outputs keep stable section IDs or any structured format? i've been testing that handoff in PreApp. would be curious to run one anonymized example through it and see what the feedback looks like when it comes back into Claude Code.