quote-drafter
Skill1 starsChanged 5 months agoMITView on GitHub
Turn a few bullet points into a clean, client-ready quote or proposal with scope, itemized pricing, timeline, and next steps. Use when the user says "write a quote", "draft a proposal", "client quote", "pricing proposal", or "send a quote".
In this repository4 other files it gives its agents.
- cash-flow-snapshotSkill
- expense-categorizerSkill
- invoice-chaserSkill
- payment-plan-drafterSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Run this prompt with the user's notes:
- Distinctive: line 52
Tip: Add one line on why the client reached out (a referral, a deadline) — it makes the summary feel written for them.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quote & Proposal Drafter
Turn rough notes into a professional, client-ready quote.
When to use
A prospect needs pricing and you want a clean quote without writing it from scratch.
What you'll need
A few bullets on the client, the work involved, your pricing, and the timeline.
Instructions
Run this prompt with the user's notes:
You are my proposals writer. Turn the notes below into a clean, client-ready quote.
Notes:
- Client / company: [client name]
- What they need: [the work or problem in a few bullets]
- Scope / deliverables: [what I'll actually do]
- Pricing: [fixed price, hourly rate, or per-item — include the numbers]
- Timeline: [how long, or start/end dates]
- Anything to exclude: [out-of-scope items, if any]
Produce a quote with these sections:
1. A one-paragraph summary that shows I understood their problem.
2. Scope of work — deliverables as a clear bullet list.
3. Pricing — an itemized table (line item, quantity, price, total) with a clear grand total.
4. Timeline — when work starts and key dates.
5. What's not included — so there are no surprises later.
6. Next step — exactly what they do to accept.
Tone: confident and professional, not salesy. Use my real numbers — never invent prices or dates I didn't give you. If anything important is missing, list your questions at the top before the draft.Tip: Add one line on why the client reached out (a referral, a deadline) — it makes the summary feel written for them.
Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →
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.

