Pre-construction Opportunity Mining Assistant for Government Procurement and Engineering Bidding Projects

The Specific Problem Being Solved

In government procurement and engineering bidding, sales teams often face a critical challenge: how to uncover potential opportunities at early project stages—such as planning, filing, environmental assessment, design, or construction preparation. Traditional methods rely on bidding information released later in the lifecycle, leading to delayed sales engagement and missed chances to connect early with decision-makers like construction units or design firms. Enterprises need a proactive approach to extract pre-construction clues from project pipelines, supporting sales strategies for engineering, equipment, materials, or professional services.

How the Skill Works

This skill automates the mining of pre-construction project information via APIs, with core capabilities including:

• Input Collection and Processing: Users provide industry keywords, regions, investment preferences, time ranges, etc. The skill explicitly prompts for necessary information rather than arbitrarily selecting industries, ensuring precise search conditions.
• Search and Detail Retrieval: Constructs search parameters (e.g., using spaces for AND relationships and | for OR relationships in keywords), calls POST /outer-gateway/bbid/searchNZJProjectApi to fetch project lists, then for high-match items, calls POST /outer-gateway/bid/getNZJProjectDetail to extract detailed information like construction units and content.
• Attachment Management: If needed, calls POST /outer-gateway/bid/getNZJProjectFileList to obtain attachment lists, retaining names, formats, sizes, and status.
• Information Analysis and Sorting: Judges project stages based on explicit statements in titles or content (marking as "to be verified" when unclear), and sorts results by product match, region, publication time, attachment completeness, etc., generating follow-up suggestions such as contacting construction or design units.

The skill strictly adheres to API specifications, for example, the search interface pageNumber must not exceed 50; the detail interface uses parameter name publishtime, while the attachment interface uses publishTime, avoiding confusion. Key management relies on environment variables BBIAO_API_KEY and BBIAO_SERVER_URL for secure API calls.

Applicable Boundaries and Notes

• Data Accuracy Limitations: Project stages depend only on explicit statements in titles or content; missing information is marked "to be verified," requiring user verification. Attachments may be outdated or unavailable, so it's advisable to check status before calls.
• Interface Parameter Constraints: Requests must use UTF-8 JSON POST, and parameter names (e.g., publishtime vs. publishTime) must be strictly distinguished, as misuse can cause failures.
• Reliability of Output Suggestions: Suggestions are based on retrieved information, such as contacting construction or design units, but should not fabricate unmentioned entities. Users must make decisions based on actual circumstances.
• Key Security Requirements: API keys must be read from environment variables and never exposed in logs, responses, or URLs; they should be saved securely long-term to avoid repeated prompts.

This skill suits scenarios requiring pre-construction opportunity mining for engineering sales, but it depends on data source updates and accurate user inputs, and cannot guarantee real-time validity of all project information.