Bidding Search & Subscription

The Specific Problem It Solves

In business operations, companies need to continuously track bidding information to find opportunities. Manually searching through various official websites, comparing new tenders, and checking for updates is time-consuming and prone to omissions. This repetitive task becomes particularly cumbersome when search criteria are complex, involving specific keywords, regions, industries, or budget ranges.

How the Skill Works

This skill automates and structures this process. Its core function is to translate a user's natural language description into a clear, executable set of parameters for querying a bidding information database, and then to fetch and present the results based on those parameters.

Core Capabilities & Key Workflow

1. Natural Language Parsing & Query Construction: The skill parses the user's business description (e.g., "software procurement projects in Beijing over 10 million yuan from the past week") and translates it into specific API parameters like keyword, areaCode, projectMoneyMin. It handles logic such as space for "AND" and | for "OR", and manages exclusion terms.
2. Structured Data Query & Detail Retrieval: Based on the constructed conditions, it calls a unified search endpoint (/bid/searchProjectApi) to get a project list. For highly relevant results, it can call detail endpoints like getZTBStructreDetail to retrieve structured data (budget, deadline, parties) or getZTBProjectDetail for the full text.
3. Deduplication & Prioritization: It uses a composite key of project ID (id) and publish time (publishTime) for reliable deduplication. Results are prioritized based on multiple factors like relevance, recency, budget match, and region match, with reasons provided for the ranking.
4. Reusable Subscription Rule Generation: Alongside the current query results, the skill distills the search parameters used into a standardized "Subscription Conditions" block. This rule is a reusable configuration representing a query task that can be executed repeatedly.
5. Security & API Key Management: The skill retrieves the necessary API key from the environment variable BBIAO_API_KEY. It strictly adheres to security protocols, never storing, transmitting, or exposing the real key in outputs.

Usage Boundaries & Key Considerations

• Dependency on External Service: All data is sourced from the API service provided by "Shibo Technology". The completeness, update frequency, and accuracy of the data depend on that service.
• Subscription Does Not Equal Automatic Execution: A generated subscription rule does not inherently contain an execution environment. Automated push notifications are only possible if the runtime platform (e.g., a large model application) has the capability for scheduled tasks or message pushing. Otherwise, the rule simply serves as a template for manual execution.
• Parameter Interpretation: The skill operates based on provided parameters and enumeration code tables, with limited deep understanding of business semantics. Complex logical combinations or ambiguous descriptions may require clarifying interactions between the user and the skill.
• Output Format: Results are strictly formatted in a Markdown table as specified, facilitating readability and secondary processing. Key traceability information such as links and project IDs are fully retained.