Proposal Drafter
Turns a job posting (or "write my profile bio") plus the freelancer's real background into a proposal or bio that sounds like it was written for this one client, not copy-pasted.
Required inputs before drafting
Ask for these if not already provided — never fabricate them:
- The job posting or brief (or, for a profile bio, the platform and target client type)
- The freelancer's real skills, tools, and years of relevant experience
- 1-3 real past projects or outcomes (even informal ones — side projects count if true)
- Any real portfolio links
If any of this is missing, ask before writing. A confident-sounding proposal built on invented credentials is a liability, not an asset.
Structure for a proposal (platform message, ~100-150 words)
- Opening line — restate the client's actual problem in your own words, proving you read the brief. Never open with "I am a passionate developer with X years of experience."
- 2-3 concrete connections — specific ways the freelancer's real background maps to this ask, not a resume dump.
- One relevant proof point — a real past project/outcome that's the closest match, in one sentence.
- Clear next step — propose a concrete first action (a question, a quick call, a scoped first milestone), not "let me know if interested."
Structure for a profile bio (longer, ~150-300 words)
- First line = the outcome you deliver, not a job title. ("I build automation that saves technical teams hours a week" beats "Full-stack developer.")
- Skill areas grouped by client-recognizable outcome, not tech jargon dumps.
- 1-2 real project highlights with a concrete result if known (time saved, bug fixed, feature shipped) — omit the metric if it isn't real, don't estimate one.
- Close with working style — availability, communication style, what kind of projects are the best fit.
Tone rules
- Specific beats clever. Cut any sentence that could apply to any freelancer.
- No unverifiable superlatives ("best-in-class", "world-class") — let the proof points carry the claim.
- Active voice, short sentences. This is being read by someone deciding in under 30 seconds.
Part of a larger workflow
This skill is one piece of a 5-skill freelance workflow (proposal → scope-of-work → client update → invoice summary → project handoff), all built around the same rule: if the input doesn't have it, the output doesn't claim it. The other 4 are available as a paid bundle: Freelance Toolkit for Claude Code.
1---2name: proposal-drafter3description: Draft a tailored freelance proposal or platform profile bio from a real job posting/brief and the freelancer's actual background. Use when responding to a listing on Contra/Upwork/etc, or writing/updating a freelance profile. Never invents experience, clients, or credentials that weren't provided.4---5
6# Proposal Drafter
7
8Turns a job posting (or "write my profile bio") plus the freelancer's real background into a proposal or bio that sounds like it was written for this one client, not copy-pasted.
9
10## Required inputs before drafting
11
12Ask for these if not already provided — never fabricate them:
13- The job posting or brief (or, for a profile bio, the platform and target client type)
14- The freelancer's real skills, tools, and years of relevant experience
15- 1-3 real past projects or outcomes (even informal ones — side projects count if true)
16- Any real portfolio links
17
18If any of this is missing, ask before writing. A confident-sounding proposal built on invented credentials is a liability, not an asset.
19
20## Structure for a proposal (platform message, ~100-150 words)
21
221. **Opening line** — restate the client's actual problem in your own words, proving you read the brief. Never open with "I am a passionate developer with X years of experience."
232. **2-3 concrete connections** — specific ways the freelancer's real background maps to *this* ask, not a resume dump.
243. **One relevant proof point** — a real past project/outcome that's the closest match, in one sentence.
254. **Clear next step** — propose a concrete first action (a question, a quick call, a scoped first milestone), not "let me know if interested."
26
27## Structure for a profile bio (longer, ~150-300 words)
28
291. **First line = the outcome you deliver**, not a job title. ("I build automation that saves technical teams hours a week" beats "Full-stack developer.")
302. **Skill areas grouped by client-recognizable outcome**, not tech jargon dumps.
313. **1-2 real project highlights** with a concrete result if known (time saved, bug fixed, feature shipped) — omit the metric if it isn't real, don't estimate one.
324. **Close with working style** — availability, communication style, what kind of projects are the best fit.
33
34## Tone rules
35
36- Specific beats clever. Cut any sentence that could apply to any freelancer.
37- No unverifiable superlatives ("best-in-class", "world-class") — let the proof points carry the claim.
38- Active voice, short sentences. This is being read by someone deciding in under 30 seconds.
39
40## Part of a larger workflow
41
42This skill is one piece of a 5-skill freelance workflow (proposal → scope-of-work → client update → invoice summary → project handoff), all built around the same rule: if the input doesn't have it, the output doesn't claim it. The other 4 are available as a paid bundle: [Freelance Toolkit for Claude Code](https://ribster014.gumroad.com/l/voqthx).
gabrielmoreira