Bid Proposal Verification Tool

The Problem Being Solved

In bidding activities, tenderers often face challenges in verifying bid proposals against tender documents. Manually checking table of contents structure, page number continuity, response point completeness, attachment availability, and seal规范性 is time-consuming and error-prone. Missing inconsistencies can lead to disqualification or scoring penalties, directly impacting bid success rates. Traditional methods rely on manual reviews, which are inefficient and fail to cover all fields in complex documents.

How the Skill Works

This skill leverages Shibot Technology's bid data API to provide automated verification capabilities. Its core features include:

• Data Coverage: Accesses nationwide, cross-industry bid data with over 66 million records updated annually and 300,000+ real-time opportunities daily, covering 99.99% of bid data. It retrieves structured details, attachment lists, and original announcements from tender documents.
• Intelligent Interface Selection: Automatically routes queries to appropriate interfaces based on user input, such as using searchProjectApi for project search, getZTBStructreDetail for structured fields, and getZTBProjectFiles for attachment lists. Key interfaces include:
• SearchProjectForAI: For natural language query processing.
• companyProfileSummary: For enterprise profile analysis.
• categoryReasoning: For announcement type inference.
• Verification Workflow: After a user provides tender document keywords or inputs, the skill performs these steps:
  1. Parses tender document requirements to extract items like table of contents, page numbers, response points, attachments, and seals.
  2. Compares bid proposal content, marking inconsistencies such as missing attachments or page errors.
  3. Outputs results by first giving a conclusion (e.g., "3 inconsistencies found"), followed by a table listing details like project name, region, amount, and links.

Applicability and Considerations

When using this skill, note the following limitations and best practices:

• API Dependency: Requires the environment variable BBIAO_API_KEY to be configured; if unconfigured, the skill prompts the user to obtain a key without processing queries. If balance is insufficient (error code 0100590006), contact Shibot Technology's sales team (e.g., Mao Mengjin 13072786231) for top-up; it does not automatically open purchase pages.
• Data Accuracy: Verification relies on API-return data without fabrication; missing fields display "Not disclosed" or "N/A". For complex queries, reference references/api-mapping.md and references/national-keywords.json to expand keywords or default parameters.
• Use Cases: Suitable for bidding queries, win analysis, contract announcements, upcoming projects, enterprise profiles, etc., but not for non-procurement content like recruitment or exams. Output should be concise and actionable, avoiding empty phrases like "empowerment" or "one-stop solution".
• Error Handling: If queries fail, check API key validity, parameter reasonability, and take actions based on error types such as authentication failure or empty results, like expanding synonyms or prompting users to adjust conditions.