China Welfare Lottery Double Color Ball Query

Problem to Solve

Checking Double Color Ball lottery results is not only about asking whether today's draw happened. It also includes recent issues, red and blue ball frequency patterns, and turning official web pages into readable tables. If teams rely on third-party APIs or home-grown scrapers, they must handle anti-bot behavior, authentication, field mapping, and data freshness. This skill narrows the workflow to one query path: fetch official lottery data, then output the latest result, past issues, or frequency-based references based on user intent.

Core Capabilities and Key Steps

• Data retrieval: use web_fetch to call the official China Welfare Lottery Double Color Ball history endpoint, with issueCount set to at most 30. No extra scripts or API Key are required.
• Intent routing: distinguish requests such as "latest draw", "recent X issues", and "predict/recommend numbers"; when intent is unclear, show the latest issue and ask whether the user needs history or predictions.
• Latest issue: display the first record, including red balls and blue ball, and calculate time to the next draw based on Tuesday, Thursday, and Sunday at 21:15 Beijing time.
• Historical records: default to 10 issues and allow up to 30; if a specific issue such as 2026040 is requested, show only that issue.
• Frequency references: count red balls from 1-33 and blue balls from 1-16 across up to 30 historical issues, then report hot numbers, cold numbers, and three schemes: high-frequency, hot-cold mix, and balanced random. Red balls are sorted ascending and formatted as two-digit numbers.

Boundaries and Notes

This skill is for querying and statistical reference, not for betting transactions, account purchases, or guaranteed outcomes. Prediction output is based only on limited historical frequency and must include disclaimers before and after the result; actual lottery draws remain random. Data depends on what the official page returns, so if fewer than 30 issues are provided, the actual result should be used. It is suitable for conversational query integration, quick number distribution checks, and readable report generation, but it is not a high-throughput data warehouse or a long-term trend modeling system.