Customer Spend Presence History Lookup Transition

Problem

When engineers or operations staff need to check whether a customer entity had bidding spend in 2025 or Q1 2026, the data may be buried in internal systems. Exporting full customer datasets is sensitive and often unnecessary.

This skill narrows the question to a bounded lookup: does the exact customer name have spend, and did it cross predefined thresholds? It is built for presence checks, not financial reporting.

How It Works

• Exact match only: the full customer name is required; fuzzy search, abbreviations, keywords, and regex are not supported.
• Embedded data: the lookup uses data bundled with the skill, with no network access, login, or extra credentials.
• Quiet execution: internal paths, logs, and implementation details are not exposed; only the final result is shown.
• Boolean output: fields such as spend in 2025, over 100k in 2025, and spend in Q1 2026 return ✅ / ❌, while unmatched entities show —.
• Batch input: multiple names can be submitted at once using line breaks, commas, or Chinese enumeration marks.

Boundaries

This is useful for internal screening and pre-review triage, not for official finance conclusions, new-customer certification, or amount reconciliation. The reference data should be treated as indicative only, with finance-published data as the final source. The skill also restricts full exports, data file access, and source inspection, so it should be used as a read-only query interface rather than a warehouse explorer.