proposal-writing
Skill1 starsChanged 6 months agoMITView on GitHub
Use only when drafting or improving business proposals, project proposals, service proposals, client proposals, scopes of work, solution outlines, deliverables, timelines, assumptions, and commercial proposal narratives.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- meaningfy-ws/skillerytheir own version, first seen Oct 27, 2026
- MarcoZorn/agencykittheir own version, first seen Jul 7, 2026
- walternate/skillstheir own version, first seen Feb 5, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- MarcoZorn/agencykit★ 6same name
- meaningfy-ws/skillery★ 2same name
- walternate/skills★ 0same name
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.
In this repository72 other files it gives its agents.
- agent-tool-callingSkill
- ai-llm-integrationSkill
- api-documentationSkill
- architecture-docsSkill
- auth-access-controlSkill
- automation-scriptingSkill
- backend-apiSkill
- backend-performanceSkill
- browser-extensionSkill
- business-report-writingSkill
- code-refactorSkill
- code-review-refactorSkill
- code-reviewSkill
- competitor-analysisSkill
- csv-data-cleaningSkill
- database-migrationsSkill
- database-modelingSkill
- database-performanceSkill
- data-engineeringSkill
- debugging-troubleshootingSkill
- devops-deploymentSkill
- document-summarizationSkill
- email-communicationSkill
- email-draftingSkill
- excel-formulasSkill
- frontend-designSkill
- frontend-implementationSkill
- frontend-performanceSkill
- fullstack-integrationSkill
- git-branch-commitSkill
- git-github-workflowSkill
- github-pr-issuesSkill
- graphql-apiSkill
- literature-reviewSkill
- llm-evaluationSkill
- loggingSkill
- mcp-plugin-developmentSkill
- meeting-notesSkill
- metrics-alertingSkill
- mobile-app-developmentSkill
- monorepo-maintenanceSkill
- nextjs-frontendSkill
- observability-monitoringSkill
- office-documentsSkill
- pdf-document-workflowSkill
- performance-optimizationSkill
- pitch-deck-builderSkill
- policy-writingSkill
- presentation-builderSkill
- product-requirementsSkill
- project-planningSkill
- prompt-engineeringSkill
- rag-pipelineSkill
- react-frontendSkill
- readme-writingSkill
- release-notesSkill
- research-synthesisSkill
- rest-apiSkill
- runbook-writingSkill
- security-hardeningSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Keep commitments realistic and review-sensitive terms visible.
- Distinctive: line 19
Avoid vague promises and unsupported ROI claims.
- Distinctive: line 20
Use tables for timeline, pricing, assumptions, and responsibilities.
- Distinctive: line 24
Check names, dates, scope, dependencies, and commercial terms.
“Common” is measured: kept by at least 6 in 10 of the 3 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 Writing
Workflow
- Identify client, problem, desired outcome, evaluation criteria, and deadline.
- Structure the proposal around need, approach, deliverables, timeline, responsibilities, assumptions, and risks.
- Make scope and exclusions explicit.
- Tie benefits to the client's stated goals.
- Keep commitments realistic and review-sensitive terms visible.
Style
- Be specific about deliverables and acceptance.
- Avoid vague promises and unsupported ROI claims.
- Use tables for timeline, pricing, assumptions, and responsibilities.
Verification
- Check names, dates, scope, dependencies, and commercial terms.
- Flag legal, procurement, or finance review needs.
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.

