proposal-compare
Skill39 starsChanged 6 months agoMITView on GitHub
Compares two proposal approaches side-by-side. Invoked by /proposal compare <a> <b>. Output: PROPOSAL-COMPARE.md.
In this repository14 other files it gives its agents.
- proposalSkill
- proposal-buildSkill
- proposal-casestudySkill
- proposal-coverSkill
- 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 Compare — Two-Approach Comparison
Compares two proposal approaches side-by-side. Invoked by /proposal compare <a> <b>. Output: PROPOSAL-COMPARE.md.
Use Cases
- Two pricing models (retainer vs project)
- Two scopes (lean audit vs full management)
- Two positioning angles for the same client
Output
A comparison table across: investment, deliverables, timeline, expected ROI, risk, close probability. Then a clear recommendation on which to lead with and why, plus when to use the other as a fallback.
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.