proposal-writing
Skill6 starsChanged 4 months agoMITView on GitHub
Generate a client proposal from scope, budget and past project references. Draws from scope/outcome example pairs when provided.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- meaningfy-ws/skillerytheir own version, first seen Nov 13, 2026
- yiweiwan/skillstheir own version, first seen May 12, 2026
- walternate/skillstheir own version, first seen Feb 5, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- meaningfy-ws/skillery★ 3same name
- yiweiwan/skills★ 1same name
- walternate/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- agency-statusSkill
- client-approvalSkill
- client-reportSkill
- post-mortemSkill
- project-briefSkill
- quote-builderSkill
- shooting-daySkill
- social-calendarSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Do you have past proposals or scope/outcome examples to reference?
- Very specific: line 47
If a BRAND.md file exists in .claude/skills/proposal-writing/ or .claude/brand/, read it before generating and apply its tone, terminology, …
- Distinctive: line 50
If the user provides past proposals or scope/outcome example pairs, extract:
- Distinctive: line 57
If budget is unknown: produce the proposal with a [TBD] placeholder and a note to fill before sending
- Distinctive: line 58
If scope is vague: ask one clarifying question before proceeding
- Distinctive: line 59
If past examples conflict: use the most recent one as primary reference
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
proposal-writing
When to use this skill
EN triggers: "proposal", "write a proposal", "client proposal", "new pitch", "scope document" IT triggers: "proposta", "scrivi una proposta", "pitch", "documento di scopo"
Inputs required
Before generating, ask:
- Client name and industry
- Service scope (what will be delivered)
- Budget range (or "unknown")
- Deadline for the proposal
- Do you have past proposals or scope/outcome examples to reference? (optional but recommended)
Output format
Produces two blocks:
CLIENT-FACING PROPOSAL
- Executive summary (2-3 sentences, outcome-focused)
- Scope of work (phased, specific)
- Deliverables list
- Timeline
- Investment (pricing table)
- Payment terms (default: 50% upfront, 50% on delivery)
- Revision policy (2 included, extras billed separately)
- Next steps / CTA
INTERNAL NOTE (do not send)
- Margin estimate if budget provided
- Assumptions made
- Risks flagged
Human gate
This output is a draft. Review all pricing, scope, and commitment language before sending to the client. Do not send automatically.
Brand voice
If a BRAND.md file exists in .claude/skills/proposal-writing/ or .claude/brand/, read it before generating and apply its tone, terminology, and examples throughout the proposal.
Past proposal reference
If the user provides past proposals or scope/outcome example pairs, extract:
- Tone and structure patterns
- Pricing conventions
- How scope was framed Apply these patterns to the new proposal without copying verbatim.
Edge cases
- If budget is unknown: produce the proposal with a [TBD] placeholder and a note to fill before sending
- If scope is vague: ask one clarifying question before proceeding
- If past examples conflict: use the most recent one as primary reference
🇮🇹 Versione italiana
Quando usare questa skill
Frasi trigger: "proposta", "scrivi una proposta", "pitch cliente", "documento di scopo"
Input necessari
Prima di generare, chiedi:
- Nome e settore del cliente
- Scope del servizio
- Budget indicativo (o "non definito")
- Deadline per la proposta
- Hai proposte precedenti o esempi scope/outcome da usare come riferimento? (opzionale ma consigliato)
Output
PROPOSTA PER IL CLIENTE — sommario esecutivo, scope, deliverable, timeline, investimento, termini di pagamento, politica revisioni, prossimi passi. NOTA INTERNA — stima margine, assunzioni, rischi.
Nota importante
L'output è una bozza. Verifica sempre prezzi, scope e linguaggio contrattuale prima di inviare.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

