Writes a complete client proposal document including problem statement, proposed solution, scope definition, timeline, pricing, and terms. Produces a full proposal ready to send to a prospective client.
SkillScore92Maintained
Automatic
◆Sales & GTM pack
Last verified 10/9/2026
What it changes
Passed 24 of 26 test cases with the skill, and 11 of 26 without it.
Without skill42%
With skill92%
Checks it passed that the model alone missed
The proposal excludes promises of personal effort or work hours.
The proposal describes project value using outcome-focused language.
The call to action section contains exactly three numbered next steps.
and 20 more in the full report
13 fixed11 passed either way2 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+371%
Agent turns
0%
Response time
+26%
Model gemini-3.6-flashMeasured 10/9/2026v124 of 26 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
Write the Next Steps call to action section for a $9,000 brand strategy proposal to Orion Robotics. I want to make sure the client knows what to do next to get started.
What was checked, without and with the skill
Checked
Without skill
With skill
The call to action section contains exactly three numbered next steps.
Missed
Passed
The call to action specifies scheduling a kickoff call as one of the steps.
Passed
Passed
case-16 · gemini-3.6-flash · 10/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md541 linessingle file
Freelance Proposal Writer
When to Use
Use this skill when any of these situations arise:
A user has an active client inquiry, lead, or conversation and needs to send a formal proposal document to move the engagement forward
A user is responding to an inbound request for proposal (RFP) from a business or organization seeking freelance or consulting services
A user completed a discovery call or intake meeting with a prospective client and needs to convert that conversation into a written proposal
A user is pitching a project proactively -- approaching a potential client with a defined scope, timeline, and price before the client has officially requested a proposal
A user needs a scope of work (SOW) document to define project boundaries, deliverables, and responsibilities before starting work on a handshake or verbal agreement
A user is re-proposing a project after a scope or pricing negotiation and needs to issue a revised, updated proposal document
A user received vague client interest ("let's work together, send me something") and needs to structure that loose interest into a formal, actionable document
Do NOT use this skill when:
The user needs help calculating what rate to charge before they are ready to write a proposal -- use freelance-rate-calculator first, then return to this skill
The user is writing a business plan or investor pitch (no client relationship, forward-looking business case) -- use a business proposal skill
The user is writing a job application cover letter responding to a posted employment position -- use cover-letter-writer
The user wants a contract or legal services agreement for a project that is already agreed upon -- this skill produces a pre-contract proposal, not a binding services contract; direct to a contract template skill
The user needs a statement of work amendment to modify an existing signed agreement -- that is a change order document, not a new proposal
The user wants general advice on freelancing business practices without a specific project to propose -- use a freelance strategy or business development skill
The user is responding to a grant opportunity or nonprofit funding request -- those require a different structure focused on organizational mission and outcomes
Process
Step 1: Gather Complete Project Context Before Writing Anything
Do not start drafting until you have answers to these specific inputs. If the user has not provided them, ask. Missing context produces generic proposals that lose clients.
Client identity: Client name, company name, industry, company size if known (startup vs. enterprise vs. SMB signals budget norms and decision-making speed)
Lead source: How did this lead arrive? Referral, inbound inquiry, RFP, cold pitch, existing relationship? Lead source affects tone -- a warm referral proposal reads more conversationally than a formal RFP response
The client's stated problem: Capture their words specifically. What did they say they need? What pain point are they describing? Note the difference between what they say they want (a new website) and what they actually need (more online orders) -- the best proposals address both
The user's proposed solution: What will the user actually deliver? Get specifics -- not "design work" but "5 logo concepts, 2 refinement rounds, final logo in SVG/PNG/PDF formats"
Scope boundaries: What is IN scope and what is explicitly OUT? Ask the user if anything is ambiguous -- ambiguity in a proposal becomes a dispute later
Timeline: Desired start date, key constraints (client's internal deadline, product launch, fiscal year end), total project duration the user is planning
Pricing structure: Fixed project fee, hourly with an estimate cap, monthly retainer, value-based pricing, or phased billing? Get the total number and the user's intended payment split
Special terms the user wants: Revision limits, intellectual property ownership timing, kill fee if cancelled, confidentiality requirements, non-compete or exclusivity, tools and software the client must provide