Bid Opportunity AI Search Assistant

Problem

Bid opportunity search often gets stuck between business intent and executable query parameters. A sales or bidding team may ask for recent AI-related opportunities in Beijing, but a working query needs explicit terms such as region, industry, announcement type, date range, budget, buyer, seller, and exclusion words. Manual search often means repeated keyword trial, noisy results, and links that are hard to trace back to the original announcement.

How it works

The skill translates natural-language requests into structured bid search conditions around the Shibo Technology bid data API. Key steps include:
- Intent detection: determine whether the user needs tender notices, winning-bid results, contract announcements, planned projects, attachments, source links, or natural-language-to-API-parameter rewriting.
- Condition extraction and conservative defaults: pull keywords, region, industry, buyer, winner, amount range, time range, announcement type, and exclusion words; when fields are missing, use conservative defaults such as nationwide region and the last 90 days.
- AI-assisted search and API lookup: for complex multi-condition questions, call aiSearchSubmitPolling to generate structured search conditions, then query whitelisted interfaces such as searchProjectApi, searchProjectContactApi, and searchNZJProjectApi for announcements, contracts, and planned projects.
- Result enrichment: after a hit, use follow-up interfaces such as getZTBStructreDetail and getCollectUrl to add structured fields, attachment clues, and traceable source links, while showing both detected conditions and auto-completed conditions.

Boundaries

It is useful for sales, bidding, operations, and integration teams who need to screen opportunities, trace announcements, analyze contracts, or collect planned-project signals. It is not a full CRM or private data platform. Results depend on the upstream API response; missing fields should be marked as undisclosed or unavailable rather than inferred. Credentials should be handled through secure configuration, and insufficient quota should follow the stated workflow instead of automatic payment, key guessing, or repeated retries.