Claude Skill

proposal-writer

Prepare commercial proposals and client responses - structure, pricing presentation, and persuasive framing. Use for quotes, offers, and project proposals.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_proposal-writer-e9c73a3.zip · 1 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/proposal-writer
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Proposal Writer

Overview

A proposal is a decision document: restate their problem better than they did, then make saying yes easy.

Proposal structure

  1. Executive summary - their situation, the outcome you deliver, investment range (1 page)
  2. Understanding of the need - their words, their stakes (proves you listened)
  3. Proposed solution - phases, deliverables, what's in/out of scope
  4. Methodology & timeline - how, when, milestones
  5. Team & references - who does the work, similar projects (case-study-writer output)
  6. Investment - options (good/better/best when possible), payment terms
  7. Next steps - one clear action with a date
  8. Annexes - technical details, CVs, legal

Workflow

  1. Collect: discovery notes (discovery-call-assistant), scope, constraints, budget signals, decision process.
  2. Draft the executive summary first - if it doesn't convince alone, fix it before writing 20 pages.
  3. Price presentation: anchor with value delivered, not cost breakdown; options beat single take-it-or-leave-it.
  4. Address known objections preemptively (objection-handler input).
  5. Produce the document: docx-generator or pdf-generator, branded template via template-manager.
  6. Validity date + follow-up plan (meeting-followup).

Rules

  • Scope boundaries explicit - "not included" prevents disputes.
  • No jargon the client didn't use first; mirror their vocabulary.
  • Human validation before sending anything priced.
Files (navin)
  • SKILL.md 1.7 KB
    ---
    name: proposal-writer
    description: Prepare commercial proposals and client responses - structure, pricing presentation, and persuasive framing. Use for quotes, offers, and project proposals.
    metadata: {"navin":{"emoji":"📄","category":"writing"}}
    ---
    
    # Proposal Writer
    
    ## Overview
    
    A proposal is a decision document: restate their problem better than they did, then make saying yes easy.
    
    ## Proposal structure
    
    1. **Executive summary** - their situation, the outcome you deliver, investment range (1 page)
    2. **Understanding of the need** - their words, their stakes (proves you listened)
    3. **Proposed solution** - phases, deliverables, what's in/out of scope
    4. **Methodology & timeline** - how, when, milestones
    5. **Team & references** - who does the work, similar projects (`case-study-writer` output)
    6. **Investment** - options (good/better/best when possible), payment terms
    7. **Next steps** - one clear action with a date
    8. Annexes - technical details, CVs, legal
    
    ## Workflow
    
    1. Collect: discovery notes (`discovery-call-assistant`), scope, constraints, budget signals, decision process.
    2. Draft the executive summary first - if it doesn't convince alone, fix it before writing 20 pages.
    3. Price presentation: anchor with value delivered, not cost breakdown; options beat single take-it-or-leave-it.
    4. Address known objections preemptively (`objection-handler` input).
    5. Produce the document: `docx-generator` or `pdf-generator`, branded template via `template-manager`.
    6. Validity date + follow-up plan (`meeting-followup`).
    
    ## Rules
    
    - Scope boundaries explicit - "not included" prevents disputes.
    - No jargon the client didn't use first; mirror their vocabulary.
    - Human validation before sending anything priced.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related