Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

proposal-writing-2提案撰写 2

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

12,081

周安装

484

GitHub Stars

1

下载量

3,911
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:proposal-writing-2(提案撰写 2)
来源仓库:https://github.com/jk-0001/proposal-writing-2
安装命令:
openclaw skills install proposal-writing-2
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install proposal-writing-2

简介

为个体创业者定制获胜提案与报价方案,提升中标概率。

  • 适用于自由职业者、初创公司或小微企业提供竞标支持。
  • 结合客户画像生成优先排序的销售文档与沟通策略。
  • 强调本地化语言适配与行业术语准确性。proposal-writing-2 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 安装前请检查是否具备访问客户资料库或历史案例的权限。

SKILL.md

name
proposal-writing
description
Write winning proposals and quotes for a solopreneur business. Use when putting together a proposal for a potential client, structuring a sales document, pricing a project scope, or improving proposal win rates. Covers proposal structure, scoping, pricing presentation, objection pre-emption, and the psychology of persuasive proposals. Trigger on "write a proposal", "proposal template", "sales proposal", "quote for client", "how to structure a proposal", "proposal writing", "win more proposals", "client proposal".

Proposal Writing

Overview

A proposal is not a quote. A quote is a price list. A proposal is a persuasion document that makes the client feel confident, understood, and excited about working with you — and then makes paying feel like the obvious next step. This playbook builds proposals that win, structured around how buyers actually make decisions.


Step 1: Before You Write Anything — The Discovery Checklist

A great proposal is 80% listening and 20% writing. Before drafting, confirm you have answers to every one of these from your discovery conversation:

DISCOVERY CHECKLIST
====================
- [ ] What specific problem is the client trying to solve?
- [ ] What outcome do they want? (Be specific — not "better results")
- [ ] What have they already tried? What didn't work and why?
- [ ] What is the cost of NOT solving this? (In time, money, missed opportunity)
- [ ] What is their timeline / deadline? Is there urgency?
- [ ] Who else is involved in the decision? (Decision-maker vs. influencer)
- [ ] Have they worked with anyone like you before? What was that experience?
- [ ] What does "success" look like to them in 3 months / 6 months?
- [ ] What is their budget range? (Even a rough number helps structure pricing)
- [ ] What are their biggest concerns or hesitations about moving forward?

If you can't answer most of these, you don't have enough information to write a strong proposal. Ask for a follow-up call before writing.


Step 2: Proposal Structure (In This Exact Order)

The order matters. Each section builds on the one before it, moving the client from "I feel understood" to "I'm ready to say yes."

Section 1: Cover Page

  • Their company name (not yours — make it about them)
  • Project title (something descriptive and inspiring, not "Proposal for Services")
  • Date
  • Your name and logo (small — this is their document)
  • Optional: a one-line summary of the outcome you'll deliver

Section 2: Executive Summary (The Most-Read Section)

Many clients read ONLY this section. Make it count.

Write 3-4 sentences that:

  1. Restate THEIR problem back to them (shows you listened)
  2. State the outcome you'll deliver (the "after" picture)
  3. Give a one-sentence summary of your approach
  4. State the investment (price) and timeline

If they read nothing else, this section alone should make them want to say yes.

Section 3: Understanding Your Challenge

This is where you prove you actually listened during discovery. Restate their problem, their context, and their goals in YOUR words. Do not copy-paste from their brief — reframe it to show understanding.

Structure:

  • Their current situation — where they are now
  • The pain — what this situation is costing them (quantify if possible)
  • Their goal — where they want to be
  • The gap — the distance between now and the goal that you'll bridge

This section does more to build trust than anything else in the proposal. If the client reads this and thinks "they actually get it," you've already won halfway.

Section 4: Our Approach

Explain HOW you'll solve their problem. This is not a feature list — it's a narrative. Walk them through what will happen, step by step, from their perspective.

Structure:

  • Phase 1: [What happens first, why, and what the client can expect]
  • Phase 2: [Next step]
  • Phase 3: [Final delivery or ongoing work]

For each phase, include: what you do, what they need to do (their involvement), and what the output looks like.

Keep it high-level. Too much technical detail buries the value. Save the deep details for after they sign.

Section 5: What You'll Get (Deliverables)

A clear, bulleted list of exactly what they receive. This is the "contract" section that clients refer back to. Be specific:

  • NOT: "Website redesign"
  • YES: "5-page responsive website (homepage, about, services, blog, contact) with mobile optimization, SEO-optimized page structure, and 2 rounds of revisions"

Section 6: Investment (Pricing)

Put this AFTER the value sections — never lead with price. By the time they get here, they should already understand what they're getting and why it matters.

Pricing presentation rules:

  • Present ONE recommended option first (your preferred scope and price). Then offer 1-2 alternatives (a stripped-down version or an expanded version).
  • Anchor high → recommend middle → offer low. The middle option should be where you want them to land.
  • Frame price in terms of ROI where possible: "At $X/month, this pays for itself in the first week based on the 5 hours/week you told us you're currently spending on [problem]."
  • Include what's NOT included (scope boundaries). This prevents scope creep and surprises later.

Pricing option template:

OPTION A — [Name that implies scope, e.g., "Essential"]
  Includes: [deliverables]
  Investment: $[amount]
  Timeline: [weeks]

OPTION B — [Recommended ★] — [Name, e.g., "Complete"]
  Includes: [deliverables — superset of Option A]
  Investment: $[amount]
  Timeline: [weeks]

OPTION C — [Name, e.g., "Enterprise / Full-Service"]
  Includes: [deliverables — everything + extras]
  Investment: $[amount]
  Timeline: [weeks]

Section 7: Why Us (Social Proof)

Brief. 2-3 bullet points max. This is NOT the place for a long bio.

  • A relevant case study or result ("Helped [similar company] achieve [specific result] in [timeframe]")
  • A relevant credential or experience
  • A testimonial quote (if you have one from a similar client)

Put this AFTER pricing, not before. It functions as final confidence-building right before the decision, not as a sales pitch.

Section 8: Next Steps

Make it crystal clear what happens if they say yes. Remove ALL friction from the decision.

If you'd like to move forward:
  1. Reply to this email with "Let's do it" (or sign the attached contract)
  2. We'll schedule a kickoff call within [X days]
  3. [First deliverable or milestone] will be ready by [date]

Include a deadline or a gentle urgency signal: "This proposal is valid for 14 days. After that, availability and pricing may change." This is honest (your availability IS limited as a solopreneur) and creates gentle urgency.


Step 3: Proposal Design and Delivery

Format: PDF. Always. Not a Google Doc link, not a Word doc. A polished PDF signals professionalism.

Design rules:

  • Clean, minimal design. White space is your friend.
  • Use your brand colors and fonts (from brand-identity).
  • No walls of text. Use short paragraphs, bullet points for deliverables, and clear section headers.
  • Include a cover image or illustration that's relevant to their industry.

Delivery:

  • Send via email with a short, warm cover message (2-3 sentences max).
  • Walk them through the proposal on a call if possible (talking through it live dramatically increases win rates).
  • Follow up within 24-48 hours if they haven't responded.

Step 4: Handle Common Objections In Advance

A great proposal pre-empts objections so they never need to be raised. Weave these into the relevant sections:

ObjectionPre-emption
"This is too expensive"Anchor with ROI. Show the cost of NOT acting. Offer a lower-scope option.
"We need time to think about it"Add a validity deadline. Offer a call to answer questions.
"Can you do it cheaper?"Build in a stripped-down option that's already cheaper. Show what gets cut and why.
"We don't know if we need this yet"Section 3 (Understanding Your Challenge) should make the need undeniable.
"We've had bad experiences with freelancers before"Section 7 (Why Us) with specific proof of delivery. Offer a milestone-based payment structure.

Proposal Mistakes to Avoid

  • Writing a generic proposal and swapping in the client's name. Clients can tell. Every proposal should feel custom-written for them specifically.
  • Leading with your story or credentials. Lead with THEIR problem. Earn the right to talk about yourself later.
  • Burying the price. Put it in a clear, dedicated section. Hiding it erodes trust.
  • Giving only one price. Options create anchoring and give the client a sense of control.
  • Not following up. The proposal is not the end of the conversation — it's the beginning of the closing conversation.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

97.46%
按下载量换算3,812

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills