AI Agent Hub
Back to skills
Tender Document Analysis Assistant icon

Tender Document Analysis Assistant

Business Operations Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Install @user_ba095919/biaoshu-writer-read-pro using https://skillhub.cn/install/skillhub.md.

About this skill

Problem: bid requirements are scattered and hard to audit

Tender documents often mix project background, qualification clauses, scoring rules, pricing terms, and multiple packages. Manual review can miss disqualification red lines, bidding-control signals, and required response items. Tender Document Analysis Assistant targets this workflow: it parses the tender document, generates a bid draft, and reviews compliance risks before submission, so engineers and commercial teams can decide whether to bid, how to structure the bid, and which issues need review.

Core capabilities and workflow

  • Smart interpretation: upload .pdf, .doc, or .docx files up to 50 MB, or provide a local path / cloud URL. The skill returns a structured 8-dimension report covering project information, compliance items, disqualification red lines, scoring criteria, key requirements, commercial terms, pricing requirements, and procurement background, plus bidding-control insights and participation advice. Reports can be exported as HTML or Word.
  • Bid drafting: based on an interpreted tender project and selected package, specify target length up to 500 pages. The process selects packages, extracts requirements, builds an outline and body, fills standard templates, and adds table of contents, sections, and bookmarks for pending fields. It outputs a .docx file. Drafting consumes credits and can take more than 10 minutes.
  • Compliance review: submit the interpreted tender document with one or more bid documents (.doc / .docx, each up to 1024 MB). It produces a graded issue list — high risk, needs review, and notices — with tender basis, bid evidence, and suggested fixes. Multi-file similarity detection, semantic-review status, and exportable compliance reports are included.

Boundaries

  • The tender document must be interpreted first before bid drafting or compliance review.
  • Interpretation, package selection, and compliance review are not directly billed, but API/Skill submissions require a positive balance; bid drafting is the credit-consuming step.
  • Outputs are returned as absolute file paths. Partial review results must not be described as complete. Experience capture and issue reporting require explicit user consent, with a daily cap of 20 entries.

Screenshots

Use Cases

  • Before bidding, parse a new tender document to extract disqualification red lines, scoring criteria, and commercial terms, then export an interpretation report for review.
  • After interpreting a multi-package tender, select a package and generate a .docx draft with target length, table of contents, sections, and pending-field bookmarks.
  • Before the bid deadline, compare one or more bid documents against the tender to check high-risk issues, similarity, and export a compliance report.
  • When only a tender notice fragment or blind-bid format question is available, get general guidance first, then provide the full file for tailored analysis.

Best For

  • Bid preparation owners: need to assess eligibility from qualification clauses, scoring rules, and procurement background, then compile a risk list.
  • Bid writers or technical writers: need to convert tender requirements into bid outlines, body drafts, standard tables, and pending fields.
  • Commercial operations staff: need to track multi-package selection, interpretation reports, bid drafts, and pre-submission compliance checks.
  • Compliance reviewers: need to document tender basis, bid evidence, suggested fixes, and similarity detection in an auditable review record.