Data Dependencies and Execution Prerequisites
It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether there is already locally wind-mcp-skill; if not, prompt the user to install:
# GitHub
npx skills add Wind-Information-Co-Ltd/wind-skills --skill wind-mcp-skill -g -y
# Gitee 镜像（国内）
npx skills add https://gitee.com/wind_info/wind-skills.git --skill wind-mcp-skill -g -y
Skill Positioning
This skill is used to explain "why there is a sudden volume surge" and to distinguish the nature behind the volume surge as event-driven, sector spread, main-force gaming, technical-level release, or sentiment trading. The goal is to avoid treating all volume surges as bullish and to avoid missing volume surges that truly contain information value.
Execution Process
Step 1: Confirm the context in which the volume surge occurs
First define the time granularity and market position of the volume surge:
- Intraday instantaneous volume surge, half-hour volume surge, full-day volume surge
- Whether the volume surge occurs during an rise, decline, sideways movement, or near a breakout/breakdown
- Whether the day is also accompanied by high turnover, gap, limit-up sealing, limit-up opening, or late-session anomaly
Step 2: Determine whether the volume surge significantly deviates from normal
Compare current trading performance with the normal level in the recent stage, focusing on:
- Whether turnover amount or volume has significantly increased
- Whether changes in turnover rate are also clearly synchronized
- Whether the volume surge is sustained or pulse-like
- Whether the volume surge is mainly concentrated in a single period
Step 3: Investigate the sources of incremental drivers
Focus on investigating four categories of causes:
- Event-driven: announcements, news, policies, financial reports, products, orders, regulation
- Sector-driven: collective anomalies among peers, theme fermentation, leadership by the bellwether
- Technical-driven: key-level breakout, breakdown, stop-loss stampede, trend acceleration
- Capital-driven: sentiment-driven scrambling for shares, hot-money relay, gaming turnover, late-session capital probing
Step 4: Identify the quality of the volume surge
A volume surge itself does not mean it is effective; it must answer:
- Whether price advances along the direction of the volume surge
- Whether there is "volume surge without price movement" or "volume surge with a spike and pullback"
- Whether the volume surge brings structural revaluation, rather than a one-day pulse
- Whether the current market supports the continuation of this volume surge
Step 5: Output key tracking points
Provide the most important follow-up verification questions, for example:
- Whether there is follow-through the next day
- Whether the key level is held steadily
- Whether it continues to receive support from theme heat
- Whether price strength can still be maintained after turnover falls back to normal
Step 6: Integrate into an attribution result
The final output should mainly consist of "nature of the volume surge + credibility + follow-up observation points," and should not display the internal investigation path.
Output Structure
{Stock Name} Volume Anomaly Attribution
I. Volume Surge Overview
- Volume surge period: {intraday/full-day/late session}
- Price performance: {rise/fall/spike and pullback/range-bound}
- Volume surge characteristics: {description of significance and persistence}
II. Main Attribution
| Attribution direction | Judgment | Explanation |
|---|---|---|
| Event-driven | High/Medium/Low | {Whether there is clear incremental information} |
| Sector-driven | High/Medium/Low | {Whether there is collective resonance} |
| Technical-driven | High/Medium/Low | {Whether it is related to key levels} |
| Capital game/flow | High/Medium/Low | {Whether it looks more like sentiment or capital behavior} |
III. Judgment of Volume Quality
- Credibility: {High/Medium/Low}
- Evidence that most supports the current judgment: {1-2 items}
- Risk that most needs caution: {1-2 items}
IV. Follow-up Tracking
- Next key things to watch: {signal}
- If it continues to strengthen: {what it means}
- If it rapidly fades: {what it means}
Quality requirements
- Attribution must cover multiple possibilities; it is not allowed to equate increased volume with bullishness right from the start.
- If evidence is insufficient, it is allowed to give a judgment of "attribution not yet sufficient."
- The explanation should focus on "why the volume increase occurred" and "whether it is worth continuing to track."
- When multiple causes exist at the same time, the primary cause and secondary causes must be clearly identified, not simply piled up in parallel.
- The output should serve rapid intraday judgment, and the conclusions should be short and stable.