agentleFS
donnybacondigital-debugdonnybacondigital-debug/claude-code-business-kit/.claude/skills/proposal-writer/SKILL.md

proposal-writer

Skill0 starsChanged 2 months agoMITView on GitHub

Write a client proposal from rough notes (call notes, emails, a brief) using the company's proposal template, with scope, deliverables, timeline, price and explicit assumptions. Use when the user asks for a proposal, quote, estimate, "propuesta", "presupuesto", or pastes notes from a client conversation and wants something to send.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sop-writer, content-repurposer and 4 more.

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.
  • Dokkabei97Skill

    sop-writer

    Creates Standard Operating Procedures for repetitive tasks. Generates step-by-step documentation with checklists, decision trees, and responsibility assignments to eliminate single points of failure.

    Also in 3 projects that use this

  • akhilkannurSkill

    content-repurposer

    Also in 4 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 3 projects that use this

  • LangChainSkill

    linkedin-post

    Write a LinkedIn post based on research findings or a given topic. Use this skill when asked to create LinkedIn content, professional posts, or thought leadership pieces.

    Also in 3 projects that use this

  • seikaikyoSkill

    interview-me

    需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Define scope as deliverables: Write things the client receives ("A configured booking page with 3 service types"), not activities ("We will …

    line 20
  2. Very specific:

    Price: Use the price list if provided.

    line 22
  3. Distinctive:

    Timeline: Use milestones tied to what the client must provide ("Week 1 starts when we receive access to X").

    line 23
  4. Distinctive:

    Every deliverable can be checked as done or not done.

    line 29
  5. Very specific:

    No price, date or name that is not in the inputs, unless marked [TO CONFIRM].

    line 31

“Common” is measured: kept by at least 6 in 10 of the 21 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Proposal writer

A proposal must let the client say yes without another call. Clarity beats length.

Inputs

  • Notes about the client and what they want: call notes, email thread or brief.
  • template.md in this skill folder. If the company has its own template, it replaces this one.
  • Optional: price list, past proposals, delivery capacity.

Steps

  1. Extract the facts into a short list: client, problem in their words, goal, constraints (budget, deadline, tools), decision maker.
  2. Find the gaps. List what is missing or unclear. Do not invent it. Each gap becomes either an assumption in the proposal or a question for the user if it would change the price by more than 20%.
  3. Define scope as deliverables. Write things the client receives ("A configured booking page with 3 service types"), not activities ("We will work on bookings").
  4. Write out-of-scope items explicitly. Include at least two things a client could reasonably assume are included.
  5. Price. Use the price list if provided. Otherwise leave [PRICE] and explain in one line how you would estimate it. Never invent a price.
  6. Timeline. Use milestones tied to what the client must provide ("Week 1 starts when we receive access to X").
  7. Fill the template in the client's language and the company's tone.
  8. Export. Markdown by default. If a document skill (docx or pdf) is available and the user asks for a file, export with it.

Quality checks before answering

  • Every deliverable can be checked as done or not done.
  • Assumptions and out-of-scope sections are not empty.
  • No price, date or name that is not in the inputs, unless marked [TO CONFIRM].
  • The first paragraph restates the client's problem in their own words.
  • Final message to the user: the proposal, then a short list of open questions.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.