proposal-cover
Skill39 starsChanged 6 months agoMITView on GitHub
Writes the email that delivers the proposal. Invoked by /proposal cover <client>. Output: PROPOSAL-COVER-[Client].md. Plain text, one CTA, no jargon. Also produce one A/B subject-line variant.
In this repository14 other files it gives its agents.
- proposalSkill
- proposal-buildSkill
- proposal-casestudySkill
- proposal-compareSkill
- proposal-followupSkill
- proposal-objectionsSkill
- proposal-pricingSkill
- proposal-quickSkill
- proposal-report-pdfSkill
- proposal-roiSkill
- proposal-scopeSkill
- proposal-sowSkill
- proposal-summarySkill
- proposal-upsellSkill
The file
Files
Proposal Cover — Delivery Email Writer
Writes the email that delivers the proposal. Invoked by /proposal cover <client>. Output: PROPOSAL-COVER-[Client].md.
Output
A short (50-80 word) delivery email:
- Subject: 4-7 words, e.g. "[Client] + [Agency] proposal"
- Opening line referencing your conversation or their audit
- Point them to the 2 sections to read first (usually Executive Summary + Investment)
- Propose a specific walkthrough time
- Set the validity date expectation
- Warm, confident sign-off
Plain text, one CTA, no jargon. Also produce one A/B subject-line variant.
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.