support_break_warning_skill

Support Break Warning Skill

Data dependencies and execution prerequisites

It is recommended to use Wind wind-mcp-skill to obtain the underlying data. Before execution, first check whether it already exists locally wind-mcp-skill; 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 to focus on 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 flow

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 consolidation, lower edge of consolidation
• Near medium- and long-term moving averages
• Trendline, gap, dense trading area
• User-preset stop-loss level, take-profit level, or watch level

If the user has not given a price, first identify the most meaningful level based on recent structure, then proceed to subsequent judgments.

Step 2: Explain the importance of the level

Explain why this level is important, answering at least the following questions:

• Is it a confirmation level for trend continuation, or a warning level for trend damage
• Whether stop-loss orders, chase buyers, or traders looking to break even may cluster nearby
• How market psychological expectations change after this level is broken through or broken below

Step 3: Judge the current state of proximity

Identify which state the stock is currently in:

• Not yet touched, but approaching
• Just touched, confirmation not yet completed
• Already validly broken through
• Already validly broken below
• Crossed intraday but not confirmed at close

Intraday touch and close confirmation have different meanings and must be explained separately.

Step 4: Set confirmation rules

Set simple and clear confirmation logic for this key level, prioritizing:

• Whether it holds or breaks below on a closing basis
• Whether volume expands and matches the direction
• Whether it continues the next day, rather than pulling back after a spike or rebounding after a breakdown
• Whether the sector and market environment support the direction

Step 5: Generate response prompts

Provide disciplined prompts for different states:

• What to observe before confirmation
• How to handle it after a valid breakout
• What risk should be prioritized for control after a valid breakdown
• What are the common identification signals of a false breakout or false breakdown

Step 6: Integrate into a key level alert card

The final output is a concise alert card that directly serves execution and observation, without expanding on the technical analysis process.

Output structure

---

{Stock name} key level alert

I. Key level

• Level type: {support/resistance/prior high/prior low/consolidation boundary/moving average}
• Key price level: {price}
• Reason it is important: {why this level is important}

II. Current state

• Current positional relationship: {approaching/touching/breakout/breakdown/unconfirmed}
• Volume-price characteristics: {expanded volume/shrunken volume/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 the level}
• False signal: {what situations indicate a false breakout or false breakdown}

IV. Action guidance

• Top current observation priority: {one sentence}
• If upward confirmation holds: {action guidance}
• If downward confirmation holds: {action guidance}
• Misjudgments to avoid: {common traps}

---

Quality requirements

1. Key levels must be related to recent structure; do not arbitrarily give price levels lacking basis.
2. The focus of alerts is on “confirmation conditions”; an intraday touch must not be written directly as a confirmed breakout.
3. Action guidance should reflect discipline and not output vague statements.
4. If the structure itself is unclear, it should explicitly state that “this level has limited reference significance.”
5. The language should be easy to read quickly before execution, and avoid becoming a lengthy technical analysis.