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

proposal-kit提案套件

Agent Skill

proposal-kit 用于整理文档、README、Markdown 和说明材料,适合在 OpenClaw 中需要把零散信息整理成结构清晰的文档时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

7,832

周安装

333

GitHub Stars

公开资料未说明

下载量

2,744
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install proposal-kit

简介

一键生成完整商业提案包,包括 Word 文档与 PI 文件。

  • 适合需要将零散信息整理为标准化对外材料的场景。proposal-kit 属于效率类 Skill,可作为该场景下的辅助能力补充。
  • 支持自定义模板与多格式导出,提升提案制作效率。
  • 输出文件路径由系统指定,用户需预留足够存储空间。
  • 安装前请确认是否允许执行脚本编译与依赖下载安装。

SKILL.md

name
proposal-kit
description
>

Proposal Kit — One-Click Business Proposal Generator

What This Skill Does

Transforms a brief natural language description into a complete, professional proposal package consisting of 4 coordinated deliverables:

  1. Proposal Document (.docx) — Full narrative proposal with executive summary, problem statement, proposed solution, methodology, timeline, team, and terms
  2. Pitch Deck (.pptx) — Visual presentation version for meetings and screen-sharing
  3. Pricing Sheet (.xlsx) — Itemized cost breakdown with phases, line items, totals, and optional discount tiers
  4. Executive One-Pager (.pdf) — Single-page summary for decision-makers who won't read the full proposal

All four documents share consistent messaging, tone, and structure — they look like they came from the same professional team.

Why This Matters

A proposal is the bridge between "interested" and "sold." Most freelancers, agencies, and small businesses lose deals not because their work is bad, but because their proposals look amateur, take too long to produce, or arrive too late. This skill collapses a 4-20 hour process into minutes.

Workflow

Step 1: Gather the Brief

Extract the following from the user's message. If critical information is missing, ask — but infer sensible defaults for anything non-critical. The goal is to minimize friction. Real users are busy and impatient; they want results fast.

Required (ask if missing):

  • What is the project/service? (even a one-sentence description is enough)
  • Who is the client? (name/company, or "unnamed client" as default)

Optional (infer smart defaults):

  • Budget range or pricing approach
  • Timeline / delivery schedule
  • Industry context
  • Specific deliverables or phases
  • Team size and roles
  • Company name of the proposer (default: use the user's name if known)
  • Tone: formal, friendly-professional, or bold (default: friendly-professional)
  • Currency (default: USD, but localize based on context clues — if the user writes in Chinese use CNY, Japanese use JPY, etc.)

Step 2: Build the Content Architecture

Before generating any files, create a unified content plan. This is critical — all 4 documents must tell the same story from different angles.

Content plan structure:

Project Title: [compelling, specific title]
Tagline: [one sentence that captures the value proposition]
Client Pain Points: [2-3 specific problems this solves]
Proposed Solution: [clear description of what will be delivered]
Key Differentiators: [why choose this team/approach]
Phases: [3-5 project phases with deliverables and timelines]
Pricing: [itemized by phase, with subtotals and total]
Timeline: [start to finish with milestones]
Terms: [payment terms, revision policy, IP ownership basics]

Step 3: Generate All Four Documents

Read the relevant skill files before creating each document type:

  • Before creating the .docx: Read /mnt/skills/public/docx/SKILL.md
  • Before creating the .pptx: Read /mnt/skills/public/pptx/SKILL.md
  • Before creating the .xlsx: Read /mnt/skills/public/xlsx/SKILL.md
  • Before creating the .pdf: Read /mnt/skills/public/pdf/SKILL.md

A. Proposal Document (.docx)

Structure: Cover Page, Table of Contents, Executive Summary, Understanding Your Needs, Proposed Solution, Methodology & Process, Timeline & Milestones, Investment, Why Us, Next Steps, Appendix.

Writing principles:

  • Open with the client's world, not yours
  • Use "you/your" more than "we/our" — ratio at least 2:1
  • Be specific: "reduce onboarding time from 3 weeks to 4 days" beats "improve efficiency"
  • Keep it scannable — busy executives read proposals in 3 minutes

Formatting: Professional layout, navy blue #1B365D accent, tables for pricing and timeline, page numbers in footer.

B. Pitch Deck (.pptx)

10 slides: Title, The Challenge, Our Approach, Solution Details (3 slides), Timeline, Investment, Why Us, Next Steps.

Design: One idea per slide, minimal text, consistent color scheme matching the docx.

C. Pricing Sheet (.xlsx)

Sheet 1 — Pricing Summary: Phase | Description | Deliverables | Timeline | Cost, subtotals, grand total, payment schedule. Sheet 2 — Detailed Breakdown (optional): line-item detail, hours x rate. Sheet 3 — Comparison (optional): Basic | Standard | Premium tiers.

Use formulas for all totals. Professional formatting with alternating row colors.

D. Executive One-Pager (.pdf)

Single page: Project Title, Tagline, The Challenge, Our Solution, Key Deliverables, Timeline, Investment, Contact.

Design: High information density, clear visual hierarchy, same color scheme, readable in 30 seconds.

Step 4: Present the Package

Save all files to /mnt/user-data/outputs/ with naming:

  • [Client-Name]-Proposal.docx
  • [Client-Name]-Pitch-Deck.pptx
  • [Client-Name]-Pricing.xlsx
  • [Client-Name]-Summary.pdf

Use present_files to deliver all four. Close with: "Here's your complete proposal package for [Client] — 4 documents, all ready to send. Want me to adjust the pricing, tone, or any specific section?"

Adaptation Guidelines

For different industries:

  • Construction/Engineering: safety, compliance, certifications, material specifications
  • Technology: technical architecture, scalability, security, integration
  • Creative/Marketing: creative vision, brand alignment, portfolio references
  • Consulting: methodology, frameworks, past results, ROI projections
  • Events: logistics, vendor coordination, contingency planning
  • Legal: formal tone, precise scope definitions, liability considerations

For different deal sizes:

  • Under $5K: lean package, shorter proposal
  • $5K-$50K: standard package, all 4 documents
  • $50K+: add risk mitigation section and case study appendix

For different languages:

  • Detect the user's language and generate ALL documents in that language
  • Adapt cultural norms, formality levels, and document conventions
  • Use locally appropriate business formats and currency

Quality Checklist

Before delivering, verify:

  • [ ] All 4 documents tell the same story consistently
  • [ ] Pricing matches across all documents
  • [ ] Timeline is consistent everywhere
  • [ ] Client name is spelled correctly throughout
  • [ ] No placeholder text left behind
  • [ ] Tone matches the industry and relationship
  • [ ] Call to action is clear and specific
  • [ ] Documents are properly formatted and professional

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

77.91%
按下载量换算2,138

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills