agentsclimarketplace

Client proposal generator

Skill bg-szy/TOP-SKILLS/skills/claude-skills/client-proposal-generator

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install
npx -y skills add bg-szy/TOP-SKILLS --skill client-proposal-generator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generates full consulting proposals from a brief. Input client name, problem description, and rough scope. Outputs proposal.md with executive summary, problem statement, proposed approach, timeline, team, pricing tiers, and terms. Researches client company for personalization. Multiple pricing models. Professional formatting matching consulting standards.

SKILL.md

3.4 KB, as published. Nobody here has run it

Client Proposal Generator

Transform a brief description into a complete, professionally formatted consulting proposal (proposal.md), researching the client company for personalization and structuring the document with proven consulting frameworks.

Contents

  • references/inputs.md -- Required and optional inputs, defaults, one-liner extraction
  • references/research.md -- Client web research checklist and research brief template
  • references/problem-and-solution.md -- Problem decomposition, methodology selection, phase and deliverable templates
  • references/timeline.md -- Duration estimation and timeline format
  • references/team.md -- Role framework and team section format
  • references/pricing.md -- Pricing models, 3-tier framework, rate benchmarks, calibration, payment terms
  • references/terms.md -- Standard terms and conditions block
  • references/output-template.md -- Full proposal document structure and delivery summary
  • references/tone-and-quality.md -- Tone variants, pre-delivery quality checklist, error handling

Workflow

  1. Gather input. Collect required fields (client name, contact, problem, firm name) and optional fields; infer the rest from context. See references/inputs.md.
  2. Research the client. Pull company overview, recent news, tech signals, industry context, and competitors; organize into a research brief. See references/research.md.
  3. Frame the problem and design the solution. Decompose into root problem, symptoms, business impact, stakeholders, and urgency; select a methodology and define phases and deliverables. See references/problem-and-solution.md.
  4. Construct the timeline. Estimate duration, lay out phases with milestones, and state dependencies and assumptions. See references/timeline.md.
  5. Compose the team. Map roles and allocations; use placeholder names if none provided and never fabricate credentials. See references/team.md.
  6. Build pricing. Select a model (default: 3-tier fixed), set tier prices from rate benchmarks or a supplied budget, and add payment terms. See references/pricing.md.
  7. Add terms and conditions. Insert the standard block, adjusting scope, IP, and assumptions to the engagement. See references/terms.md.
  8. Assemble and write the proposal. Combine all sections into the output structure and write the file. See references/output-template.md.
  9. Run the quality check. Verify accuracy, consistency, no placeholders, and no fabricated facts; match the selected tone. See references/tone-and-quality.md.
  10. Deliver and summarize. Write to the output path and present the delivery summary with personalization applied and review recommendations. See references/output-template.md.

Guardrails

  • Never fabricate case studies, team bios, credentials, or client facts. Omit rather than invent.
  • If web research yields nothing, proceed without personalization and flag it.
  • Leave no placeholder markers in the delivered document.

Gives 0 of the 12 instructions most plan spec skills give

Counted across 1,100 of the 1,860 authors here whose files we hold, read 2026-08-06

  • ask one question at a timein 46 of 1100, across 38 files
  • Break plans into vertical slicesin 28 of 1100, across 10 files
  • Publish issues in dependency orderin 27 of 1100, across 9 files
  • Iterate until user approves the breakdownin 24 of 1100, across 6 files
  • Explore the repository to understand the codebase statein 24 of 1100, across 7 files
  • Use domain glossary vocabularyin 23 of 1100, across 5 files
  • Apply correct triage labels to published issuesin 23 of 1100, across 5 files
  • Write failing tests before implementation codein 23 of 1100, across 18 files
  • Prefer AFK slices over HITLin 22 of 1100, across 7 files
  • ask clarifying questions until requirements are concretein 21 of 1100, across 13 files
  • Respect existing architecture decision recordsin 20 of 1100, across 5 files
  • write a specification before writing any codein 20 of 1100, across 12 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.