Technical Bid Proposal Writing for Openclaw

Transforms tender requirements into a scoring-driven technical bid proposal and exports the approved result as a Word document.

elle-yu
v1.0.0
Jul 15, 2026
0
467
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install bid-proposal

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install bid-proposal using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Technical Bid Proposal Writing?

Openclaw Skills' Technical Bid Proposal Writing skill turns tender requirements into a structured, reviewable proposal workflow from analysis to Word export.

It identifies the project scenario, extracts scoring criteria, recommends the right chapter outline, enriches drafts with a material library, and lets users confirm or revise each chapter before the final .docx is generated.

Technical Bid Proposal Writing Use Cases

  • Start a new proposal when the user sends 投标方案##, 写投标方案, or 投标方案 <项目名>.
  • Analyze a tender requirement document in Word or text form and extract project type, scoring items, and technical domains.
  • Continue a paused proposal from a saved checkpoint in bids/.
  • Improve proposal quality by importing company capability notes, past projects, and chapter examples from material-lib/.
  • Produce a final technical bid document for security services, product delivery, equal assurance, or integrated security scenarios.
  • Review, edit, skip, or regenerate individual chapters before exporting the final Word file.

How Technical Bid Proposal Writing Works

  1. Detect the trigger and ingest the tender requirements from chat text or a .docx file.
  2. Analyze the document to classify the project scenario, extract scoring criteria, and identify technical keywords.
  3. Load the scenario mapping and recommend a chapter outline with mandatory and optional sections.
  4. Present the outline to the user for confirmation, edits, deletions, or chapter reordering.
  5. Build a chapter-specific prompt with scripts/prompt_builder.py, using the requirements analysis and any matching material-library references.
  6. Generate each chapter in order, then let the user confirm, revise, skip, or regenerate the content.
  7. Assemble the approved chapters into a Word document with scripts/generate_docx.py, using a user template or the built-in default template.
  8. Save or restore progress through bids/<project>.json so Openclaw Skills can resume after interruption.

Technical Bid Proposal Writing Setup

  1. Install the required Python dependency:
python3 -m pip install python-docx
  1. Ensure the skill package folders are available and writable:
mkdir -p bids material-lib/past-projects material-lib/chapter-examples references
  1. Optionally add your own company assets and template files:
cp company-capabilities.md material-lib/company-capabilities.md
cp your-template.docx references/default-template.docx
  1. Verify the skill can access the bundled scripts and reference files:
python3 scripts/analyze_requirements.py input.docx --format json
python3 scripts/prompt_builder.py chapter_config.json analysis.json
python3 scripts/generate_docx.py references/default-template.docx chapters.json output.docx
  1. If you want Openclaw Skills to use custom proposal material, import it into material-lib/ before starting the drafting session.

Technical Bid Proposal Writing Data Schema & Taxonomy

Core storage

Path Purpose Notes
bids/<project>.json Session checkpoint Stores project metadata, step progress, confirmed content, and timestamps
material-lib/ Knowledge base Holds company capabilities, past projects, and chapter examples
references/scene-mapping.json Scenario taxonomy Maps tender keywords to proposal scenarios and default outlines
references/default-template.docx Fallback Word template Used when the user does not provide a custom template
output/*.docx Final deliverable Generated bid proposal document

Session state fields

Field Type Meaning
project_name string Human-readable proposal name
project_type string Matched scenario such as security services or product delivery
current_step number Active workflow step index
steps object Per-step status container
steps.<n>.status string pending, in_progress, generated, confirmed, or completed
steps.<n>.result object Output captured for the step, such as analysis or outline data
created_at string ISO 8601 creation timestamp
updated_at string ISO 8601 update timestamp

Chapter taxonomy

  • id: Stable chapter identifier.
  • status: Chapter lifecycle state, typically pending, generated, or confirmed.
  • content: Markdown chapter body.
  • current_chapter: Pointer to the active chapter during drafting.
  • result: Structured output for analysis, outline design, or chapter generation.

Material-library taxonomy

  • company-capabilities.md: Core technical capability description.
  • past-projects/: Historical bid sections and reusable proof points.
  • chapter-examples/: Reference text for requirement analysis, service方案, and technical方案 sections.

Output behavior

  • The workflow preserves all confirmed content in JSON before Word export.
  • The final .docx is assembled in chapter order.
  • Default styling follows the bundled brief-proposal conventions unless a user template is supplied.

Technical Bid Proposal Writing Advanced Features

  • Scoring-item-driven chapter planning ensures every evaluation point is covered.
  • Scenario auto-matching supports security services, product delivery, equal assurance, and integrated security bids.
  • Material-library augmentation pulls in company capabilities, historical cases, and chapter examples to improve draft quality.
  • Durable JSON checkpoints let Openclaw Skills pause and resume at any stage without losing progress.
  • Chapter-level human-in-the-loop controls allow confirm, edit, skip, reorder, and regenerate actions.
  • Custom Word template support lets teams switch between user-provided templates and the built-in default template.
  • Script-assisted automation connects requirements analysis, prompt construction, and .docx generation into one repeatable pipeline.
  • Progress-aware interaction surfaces step status such as 3/6 so reviewers always know where the proposal stands.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*