Data dependencies and execution prerequisites
Recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether wind-mcp-skillis already available locally; 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 spike" and to distinguish the nature behind the volume spike as event-driven, sector spillover, main-force game, technical-level release, or sentiment trading. The goal is to avoid treating all volume spikes as bullish, and also to avoid missing volume spikes that truly contain information.
Execution process
Step 1: Confirm the context in which the volume spike occurs
First define the time granularity and market position of the volume spike:
- Instant intraday volume spike, half-hour volume spike, full-day volume spike
- Whether the volume spike occurs during a rise, fall, sideways movement, or near a breakout/breakdown
- Whether the day also has high turnover, gap, limit-up sealing, limit-up opening, or late-session anomaly
Step 2: Determine whether the volume spike significantly deviates from normal
Compare current trading performance with the normal level in the recent period, focusing on:
- Whether turnover or volume has risen significantly
- Whether the change in turnover rate is also obviously synchronized
- Whether the volume spike is sustained or pulse-like
- Whether the volume spike is mainly concentrated in a single time period
Step 3: Investigate the sources of incremental drivers
Focus on investigating four types of causes:
- Event-driven: announcements, news, policy, financial reports, products, orders, regulation
- Sector-driven: collective anomalies among peers, theme fermentation, leadership by the bellwether
- Technical-driven: breakout at key levels, breakdown, stop-loss stampede, trend acceleration
- Capital-driven: sentiment scramble for shares, hot-money relay, game-driven turnover, late-session capital probing
Step 4: Identify the quality of the volume spike
A volume spike itself does not mean it is effective; it must answer:
- Whether price advances in the direction of the volume spike
- Whether there is "volume only without price movement" or "volume spike with rally and pullback"
- Whether the volume spike brings structural revaluation rather than a one-day pulse
- Whether the current market supports the continuation of this volume spike
Step 5: Output tracking priorities
Give the most important verification questions for follow-up, for example:
- Whether there is follow-through the next day
- Whether key positions hold
- Whether it continues to receive theme-heat support
- Whether price strength can still be maintained after volume falls back to normal
Step 6: Integrate into attribution results
The final output focuses on "nature of the volume spike + credibility + follow-up observation points" and does not display the internal investigation path.
Output structure
{Stock name} volume anomaly attribution
I. Volume spike overview
- Volume spike period: {intraday/full-day/late session}
- Price performance: {rise/fall/rally and pullback/consolidation}
- Volume spike 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} |
| Technically driven | High/Medium/Low | {Whether it is related to a key level} |
| Capital game | 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}
- Risks that most need vigilance:{1-2 items}
IV. Follow-up Tracking
- Next key focus:{signal}
- If it continues to strengthen:{what it means}
- If it rapidly fades:{what it means}
Quality requirements
- Attribution must cover multiple possibilities, and it is not allowed to equate increased volume with bullish news right away.
- If the evidence is insufficient, it is permissible to give a judgment that "attribution is temporarily inadequate."
- The focus of the explanation is "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, and they should not be piled up side by side.
- The output should serve rapid intraday judgment, and the conclusion should be short and stable.