intraday_abnormal_move_alert_skill

Intraday Abnormal Move Alert Skill

Data dependencies and execution prerequisites

It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether it already exists 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 provide a quick-judgment result of "explain first, then classify, then prompt actions" when rapid rises, rapid declines, volume shocks, or abnormal turnover occur during intraday trading. The core goal is to help users determine whether this unusual move is noise, event-driven, or a meaningful change worth continuing to track.

Execution process

Step 1: Define the abnormal-move target and abnormal-move pattern

First clarify which stock, which time period, and which type of abnormal move. The abnormal-move pattern should at least clearly describe the following information:

• Price direction: rapid spike, rapid drop, rally then pullback, dip then rebound, amplified volatility
• Magnitude and speed: whether short-term fluctuations significantly deviate from the norm
• Trading change: whether there is simultaneous volume expansion, volume contraction, or rising turnover
• Position: whether it occurs at a prior high, prior low, dense moving-average zone, or trend continuation zone

Step 2: Investigate explicit drivers

Prioritize checking whether there is newly added information that can directly explain the abnormal move, focusing on:

• Company announcements, industry news, policy news, regulatory developments
• Financial reports, earnings forecasts, product launches, major contracts, suspension and resumption information
• Collective abnormal moves in the sector, index or futures linkage, overseas mapping

If no obvious catalyst can be found, also clearly state that "no newly added explicit driver has been found so far"; do not assume there must be news.

Step 3: Determine whether the abnormal move has sector or sentiment resonance

Analyze whether the stock's abnormal move is an isolated event or group behavior, focusing on answering:

• Whether the same sector is moving abnormally in sync
• Whether theme heat is spreading
• Whether it is consistent with the market's main line direction
• Whether it is merely capital huddling in a local area or rotating at high levels

The meaning of an isolated abnormal move and sector resonance is completely different, and they must be distinguished.

Step 4: Assess sustainability and credibility

Assess the quality of the abnormal move from four perspectives: "event strength, volume-price structure, position relationship, degree of follow-through":

• Whether the event is new enough, strong enough, and specific enough
• Whether volume expansion matches the price breakout, rather than a late-session or instantaneous pulse
• Whether the current price position is likely to encounter trapped positions or profit-taking positions
• Whether the market provides sustained follow-up orders, rather than a single order lifting the price

Step 5: Provide response prompts

The focus of the output is not to directly conclude buy or sell, but to tell the user what should be prioritized for observation at this time:

• If the abnormal move is credible, which confirmation signals should continue to be watched
• If the quality of the abnormal move is average, which pullback or rebound traps should be guarded against
• If the abnormal move is highly questionable, how to lower the priority of attention

Step 6: Integrate into an intraday quick-judgment card

Finally output a concise conclusion card, without expanding the internal investigation process. The language should be short, clear, and easy to read quickly during intraday trading.

Output structure

---

{Stock Name} Intraday Abnormal Move Quick Judgment ({HH:mm})

1. Abnormal move overview

• Abnormal move type:{sharp pull-up/sharp drop/spike and fade/dip and recover}
• Abnormal Move Description:{what kind of price and volume changes occurred within how long}
• Position:{key level, middle of range, near prior high, near prior low, etc.}

II. Possible Drivers

• Explicit Driver:{if any, state the core event; if none, write 'no newly discovered explicit driver'}
• Sector Resonance:{whether there is any, and how it is performing}
• Sentiment Factors:{whether it belongs to theme fermentation, capital scrambling for shares, panic selling, etc.}

III. Abnormal Move Quality Assessment

Dimension	Assessment	Explanation
Event Strength	High/Medium/Low	{reason}
Volume-Price Match	High/Medium/Low	{reason}
Continuation Probability	High/Medium/Low	{reason}
Pullback Risk	High/Medium/Low	{reason}

IV. Key Intraday Response Points

• Priority Confirmation Signal:{what needs to be seen for continued strengthening}
• Invalidation Signal:{if what appears, it indicates the abnormal move is likely distorted}
• Current Conclusion:{one-sentence summary of whether it is worth continued tracking}

---

Quality Requirements

1. Quick judgment must prioritize answering 'why it moved' and 'whether this wave can be trusted', rather than repeating intraday performance.
2. When no cause can be found, state it truthfully; do not package speculation as fact.
3. Judgments about continuity must be supported by evidence, and cannot merely say 'it looks very strong'.
4. The main text should be suitable for intraday reading and avoid lengthy background introductions.
5. If the abnormal move is triggered by resonance across the entire sector, highlight whether 'the stock is merely a mapping' or 'the stock has independent catalysts'.