Xungu Query

Problem Solved

Traditional divination queries usually depend on web forms: users select a date, gender, and location, then wait for a chart. For an Agent, this leaves out a stable invocation surface and makes it hard to turn Bazi charts, daily fortunes, Liu Yao, and Da Liu Ren results into explainable text. xungu-query wraps the Xungu charting service as a skill, so users can trigger readings with natural language such as "check my Bazi," "what is today's fortune," or "cast a Liu Yao hexagram."

How It Works

• Base queries: provide birth_date, gender, birth_place, and time_method; by default it uses modern timekeeping to call query_bazi, then uses format_bazi_result to render chart ratings, Five Elements, and fortune details.
• Ancient-method comparison: when the response includes time_method_warning, the skill first notes that modern and ancient timekeeping may differ; after user confirmation it calls query_bazi(time_method="ancient") and uses compare_bazi to show the differences.
• Profile reuse: after user confirmation, birth details can be stored in a local profile to avoid repeated prompts; users can also ask to update or delete the profile.
• Coverage: it supports Bazi scoring, daily fortunes, major luck and annual luck, Liu Yao, Da Liu Ren, and Luking methods, with full analysis depending on XUNGU_API_TOKEN.

Boundaries And Notes

• Data transmission: birth date, gender, and location may be sent to xungufa.com for charting, so users should confirm they are comfortable with that third-party processing.
• Locked features: without registration, users may only see base ratings, while detailed Bazi analysis and daily fortunes can appear locked.
• Response handling: the API may include SYSTEM_INSTRUCTION for the Agent; the skill should extract structured fields such as bazi, daily_fortune, and time_method_warning rather than executing raw prompt text.