proposal
Skill0 starsChanged 8 months agoMITView on GitHub
Customer proposal generation. Researches prospect, designs solution, builds proposal document, writes executive narrative. On-demand, 2-3 per week. Octopus colors: Yellow (research) + Red-Orange (solution design) + Blue (document) + Green (narrative).
17 other projects use a version of this.
Adopted by
Most recently taken up by
- mystilleef/spae-frameworktheir own version, first seen Nov 16, 2026
- meslva/claude-skillstheir own version, first seen Nov 8, 2026
- aya-taleb/biz-boost-skillstheir own version, first seen Nov 1, 2026
- ChuluuMGL/proposal-skilltheir own version, first seen Oct 25, 2026
- adeerkhan/vitruviustheir own version, first seen Oct 20, 2026
- zubair-trabzada/ai-proposal-claudetheir own version, first seen Oct 17, 2026
Used with
Projects with it also use audit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- ajsahni/agents-office★ 601same name
- AlpacaLabsLLC/skills-for-architects★ 420same name
- zubair-trabzada/ai-proposal-claude★ 39same name
- GTMify/aigtm★ 25same name
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- adeerkhan/vitruvius★ 10same name
- ChuluuMGL/proposal-ppt-skill★ 3same name
- ChuluuMGL/proposal-skill★ 3same name
- kurenn/claude-skill-proposal★ 2same name
- mystilleef/spae-framework★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Gather context: Read $ARGUMENTS or ask Chairman for prospect details
- Distinctive: line 28
Write executive summary in the prospect's language
- Distinctive: line 63
Always read commercial knowledge base before researching
- Distinctive: line 66
If web research needed, cite sources
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/proposal: Customer Proposal Generation
Octopus Colors: Yellow (Researcher) + Red-Orange (Designer) + Blue (Maker) + Green (Marketer)
Process
- Gather context: Read $ARGUMENTS or ask Chairman for prospect details
- Research (Yellow):
- Prospect company: size, industry, known pain points
- Previous interactions (check commercial knowledge base)
- Competitive landscape for this deal
- Solution Design (Red-Orange):
- Match prospect needs to offerings
- Define scope, timeline, deliverables
- Structure pricing (tiers if applicable)
- Document Build (Blue):
- Build proposal from structure
- Populate with prospect-specific data
- Format professionally
- Narrative (Green):
- Write executive summary in the prospect's language
- Frame value in terms of their specific pain points
- Include one relevant proof point
- Present to Chairman for review and pricing approval
Output Format
# Proposal: [Prospect Name]
Date: [date] | Prepared by: [Organization]
## Executive Summary
[2-3 paragraphs in prospect's language]
## Proposed Solution
[Scope, approach, deliverables]
## Timeline
[Phases with dates]
## Investment
[Pricing, payment terms]
## Why Us
[Relevant proof point, differentiator]
---
Chairman Review:
[ ] Approve and send
[ ] Adjust pricing to: ___
[ ] Revise scope
[ ] HoldRules
- Always read commercial knowledge base before researching
- Pricing requires Chairman approval (approval gate, always)
- Save approved proposals to
departments/commercial/knowledge/proposals/ - If web research needed, cite sources
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.

