Asset Procurement App Query Assistant

Problem

Asset ledgers, procurement contracts, device acceptance records, app listings, and usage logs are scattered across different POST endpoints. Manual queries often require switching between backends and filling fields such as serialno, procurementNo, sn, provinceId, and developerId, while still risking missing pagination or date range filters. This skill packages these common queries into fixed request templates so an agent can map natural language to the right endpoint and parameters.

How It Works and Limits

It covers five query scenarios:
- Asset information: filter by serial number, asset type, state, company, project type, region, administrator, and time range.
- Procurement contracts: filter by procurement number, supplier, province, and status.
- Acceptance records: filter by procurement number, device name, SN, device type, device ownership, and province.
- App management: filter by app name, type, verification state, state, developer ID, and online status.
- App usage logs: filter by startTime and endTime.

The endpoints point to http://111.34.85.148:9019/gateway/appstoreOss/..., which is an internal or restricted gateway. Before use, verify network reachability, set Content-Type: application/json, and ensure enum values match backend definitions. It is suitable for query orchestration, not as a replacement for API authentication, data masking, or business validation.