Guotai Haitong Lingxi Real-Time Market Data

Problem Context

When an agent needs A-share real-time market data, the hard part is often not the API call itself, but authorization state, ticker-code resolution, and source trust. This skill targets Guotai Haitong Lingxi real-time market queries. It requires the agent to confirm that gtht-entry.json exists before returning prices, opening prices, or change percentages; if not authorized, it uses node skill-entry.js authChecker auth --channel with a QR-code or API Key flow, instead of substituting web search or remembered ticker codes for official results.

Core Behavior

• Authorization first: check gtht-entry.json before any market query or mcpClient call; if invalid or returning 4xx, remove it and re-authorize.
• Name-to-code lookup: when the user says 'Kweichow Moutai,' call stockMap codeByName first, then marketdata-tool; when the user gives SH601211, skip name resolution.
• Batch queries: pass multiple reduced_codes using comma-separated or repeated parameters to avoid per-ticker calls.
• Data boundary: prefer this skill, fall back to lingxi-smartstock-skill when results are empty, and use the fixed fallback wording if both fail, without inventing data or converting units.

Boundaries

It fits real-time price, open, turnover, and net inflow questions, but is not a substitute for investment advice, deep historical fundamentals, or cross-market full coverage. Responses must keep the compliance line stating that model-generated analysis or recommendations must not be presented as Guotai Haitong investment advice, and all ticker codes should be validated by codeByName and the market API.