Lays out a clear business proposal with scope, timeline, pricing and next steps, ready for you to fill in.
WHEN TO USE IT
When a client has asked for a proposal and you need a solid structure fast.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: proposal-outline
description: Outline a business or project proposal for a client, with scope, deliverables, timeline and pricing sections. Use when the user asks for a proposal, a quote document or a statement of work outline.
---
Outline a client proposal.
1. If the client, their problem, what you will deliver, or the rough timeline and budget is missing, ask once, in one message, then continue.
2. Use these sections:
1. Summary: the client's goal and your proposed solution in three sentences
2. Understanding of the need
3. Scope: what is included, and what is not
4. Deliverables and milestones (a table with dates)
5. Pricing (a table; use [amount] where not given)
6. Assumptions and what you need from the client
7. Why you: relevant experience the user supplied
8. Next steps and how to accept
3. Under each heading, give two or three bullet points of draft content.
Rules:
- Do not invent prices, dates, past clients or results; use [check].
- Note that payment and legal terms should be reviewed by the user, and a qualified professional if needed, before sending.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/proposal-outline
mv SKILL.md ~/.claude/skills/proposal-outline/
# then, inside Claude Code, either ask naturally:
# help me outline a proposal for a website redesign project
# or run it by name:
# /proposal-outline
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills