Prompt
AI Client Proposal — Original SKILL.md
Published by AI Agents Library
The original AI Agents Library SKILL.md, reproduced unchanged.
Prompt details
- Resource Id
- 75de8000-ecef-4142-824c-e53c15bf4902
- Prompt Body
- --- name: client-proposal description: Turn discovery notes into a clear client proposal with the client's problem in their own words, the approach, exact deliverables, what is not included, a timeline, the investment, and one next step. Use this when the user needs to write a proposal, quote, estimate, or scope of work for a prospective client, or says write the proposal, draft a quote, or scope this out. --- # Client Proposal When this skill runs, turn the user's discovery notes into a client proposal that wins the work by being specific, not long. ## Process 1. Identify the client, what they asked for, and the outcome they actually want (which is often not the thing they asked for). 2. Open with THEIR problem, in THEIR words. Quote the language they used in discovery. Do not translate it into consultant-speak. 3. Describe the approach in plain terms: what happens, in what order, and why that order. 4. List exact deliverables. Each one must be a thing the client receives, not an activity performed. 5. State what is NOT included. Be direct about it. 6. Lay out the timeline using ONLY dates or durations the user provided. 7. State the investment exactly as the user gave it. If they gave no pricing, write [YOUR PRICE HERE] and flag it. Never guess a number. 8. End with ONE next step. One. Not three options and not "let me know your thoughts." 9. List every gap you refused to fill. ## Rules - Use ONLY what the user provides. Never invent pricing, rates, timelines, deliverables, team size, credentials, results, or case studies. - You cannot see the user's CRM, past proposals, pricing sheet, or files. Never imply you can. - Do not write contract, legal, or payment-enforcement terms (liability, IP, termination, late fees). If something belongs in a contract, say so and leave it out. - Never inflate. A short specific proposal beats a long vague one; padding is what makes proposals go unread. - Never promise a result you were not told the user can deliver. No "guaranteed", no invented percentages. - The "Not included" section is mandatory. It prevents more scope disputes than anything else in the document. - Do not send anything. Produce a draft for human review. ## Output format ### The Problem Their words. Quoted where possible. ### The Approach Plain language. What happens, in what order. ### Deliverables What they receive. Concrete. ### Not Included Explicit. Mandatory section. ### Timeline Only dates or durations provided. ### Investment Exactly as given, or [YOUR PRICE HERE] if not provided. ### Next Step One action. ### What I Would Not Assume Every gap you refused to fill, and what to add. If the user has not provided discovery notes, ask for them before writing anything.
- Variables
- Supported Models
- Prompt Type
- skill_file
- License Note
- Original AI Agents Library content. Redistribution permission confirmed by the AiFolder owner on 2026-10-10; no public open-source license asserted.
- Created At
- "2026-10-10T05:47:00.811Z"
- Updated At
- "2026-10-10T07:45:18.641Z"
Prompt
--- name: client-proposal description: Turn discovery notes into a clear client proposal with the client's problem in their own words, the approach, exact deliverables, what is not included, a timeline, the investment, and one next step. Use this when the user needs to write a proposal, quote, estimate, or scope of work for a prospective client, or says write the proposal, draft a quote, or scope this out. --- # Client Proposal When this skill runs, turn the user's discovery notes into a client proposal that wins the work by being specific, not long. ## Process 1. Identify the client, what they asked for, and the outcome they actually want (which is often not the thing they asked for). 2. Open with THEIR problem, in THEIR words. Quote the language they used in discovery. Do not translate it into consultant-speak. 3. Describe the approach in plain terms: what happens, in what order, and why that order. 4. List exact deliverables. Each one must be a thing the client receives, not an activity performed. 5. State what is NOT included. Be direct about it. 6. Lay out the timeline using ONLY dates or durations the user provided. 7. State the investment exactly as the user gave it. If they gave no pricing, write [YOUR PRICE HERE] and flag it. Never guess a number. 8. End with ONE next step. One. Not three options and not "let me know your thoughts." 9. List every gap you refused to fill. ## Rules - Use ONLY what the user provides. Never invent pricing, rates, timelines, deliverables, team size, credentials, results, or case studies. - You cannot see the user's CRM, past proposals, pricing sheet, or files. Never imply you can. - Do not write contract, legal, or payment-enforcement terms (liability, IP, termination, late fees). If something belongs in a contract, say so and leave it out. - Never inflate. A short specific proposal beats a long vague one; padding is what makes proposals go unread. - Never promise a result you were not told the user can deliver. No "guaranteed", no invented percentages. - The "Not included" section is mandatory. It prevents more scope disputes than anything else in the document. - Do not send anything. Produce a draft for human review. ## Output format ### The Problem Their words. Quoted where possible. ### The Approach Plain language. What happens, in what order. ### Deliverables What they receive. Concrete. ### Not Included Explicit. Mandatory section. ### Timeline Only dates or durations provided. ### Investment Exactly as given, or [YOUR PRICE HERE] if not provided. ### Next Step One action. ### What I Would Not Assume Every gap you refused to fill, and what to add. If the user has not provided discovery notes, ask for them before writing anything.