Data dependencies and execution prerequisites
It is recommended to use Wind wind-mcp-skill to obtain the underlying data. Before execution, first check whether wind-mcp-skillalready exists locally; if not, prompt the user to install it:
# 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 organize the judgments and actions that need attention when price approaches, breaks through, or breaks below a key level into a disciplined alert. The focus is not simply reporting a price level, but explaining why this level matters, what the confirmation criteria are, and what will happen after it fails.
Execution process
Step 1: Confirm the definition of the key level
First clarify which category the key level mentioned by the user belongs to:
- Prior high, prior low
- Upper edge of a platform, lower edge of a platform
- Near medium- and long-term moving averages
- Trendlines, gaps, dense trading areas
- User-preset stop-loss levels, take-profit levels, or observation levels
If the user has not given a price, first identify the most meaningful level based on the recent structure, then proceed to subsequent judgments.
Step 2: Explain the importance of the level
Explain why this level is important, and at least answer the following questions:
- Whether it is a confirmation level for trend continuation or a warning level for trend damage
- Whether stop-loss orders, momentum-chasing orders, or unwinding orders may cluster nearby
- How market psychological expectations change after this level is broken through or broken below
Step 3: Judge the current proximity status
Identify which state the stock is currently in:
- Not yet touched, but approaching
- Just touched, confirmation not yet completed
- Effectively broken through
- Effectively broken below
- Crossed during the session but not confirmed at the close
Intraday touching and closing confirmation have different meanings and must be explained separately.
Step 4: Set confirmation rules
Set simple and clear confirmation logic for the key level, prioritizing:
- Whether it holds or breaks below on the close
- Whether volume expands and matches the direction
- Whether it continues the next day, rather than spiking and falling back or pulling back after a breakdown
- Whether the sector and market environment support the direction being established
Step 5: Generate response prompts
Provide disciplined prompts for different states:
- What should be observed before confirmation
- How to handle it appropriately after an effective breakout
- What risks should be controlled first after an effective breakdown
- What are the common identification signals of a false breakout or false breakdown
Step 6: Integrate into a key-level alert card
Finally output a concise alert card that directly serves execution and observation, without expanding on the technical analysis process.
Output structure
{Stock name} key-level alert
1. Key level
- Level type: {support/resistance/prior high/prior low/platform boundary/moving average}
- Key price level: {price}
- Reason it matters: {why this level is important}
2. Current status
- Current position relationship: {approaching/touching/breakout/breakdown/unconfirmed}
- Volume-price characteristics: {volume expansion/volume contraction/flat volume, explaining the structure}
- Environmental alignment: {whether the sector and market support it}
III. Confirmation Criteria
- Upward confirmation: {what conditions must be met to count as holding steady}
- Downward confirmation: {what conditions must be met to count as losing support}
- False signal: {what situations represent a false breakout or false breakdown}
IV. Response Tips
- Current top observation item: {one sentence}
- If upward is confirmed: {action tip}
- If downward is confirmed: {action tip}
- Misjudgments to avoid: {common traps}
Quality Requirements
- Key levels must be related to recent structure; price levels lacking a basis must not be given arbitrarily.
- The focus of the alert is the “confirmation conditions”; an intraday touch must not be written directly as a confirmed breakout.
- Response tips should reflect discipline and must not output vague statements.
- If the structure itself is unclear, it should be clearly stated that “the reference significance of this position is limited.”
- The language should be easy to read quickly before execution, and should avoid becoming a lengthy technical analysis.