price_target_reach_alert_skill

Price Target Reach Alert 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 wind-mcp-skillis already available 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 questions such as "whether to sell, how much to sell, and whether to revisit the target" into a disciplined handling framework when the stock price approaches, reaches, or exceeds the target price. The focus is not mechanically selling as soon as the price target is hit, but rather judging the current odds, degree of expectation realization, and priority of position handling after the target price is triggered.

Execution Process

Step 1: Confirm the background of the target price

First clarify where the target price comes from and what it represents:

• Research target price
• Take-profit level in the trading plan
• Technical target level
• User-defined watch level

If the source of the target price is unclear, first explain that its reference significance is limited, then proceed to handling suggestions.

Step 2: Determine the current trigger status

Identify the relationship between the stock price and the target price:

• Not yet reached, but already close
• Just reached
• Briefly crossed
• Clearly exceeded
• Pulled back after reaching

Different trigger statuses correspond to different handling priorities.

Step 3: Assess whether the target has already been realized

Judge around "whether the market has already finished trading this expectation":

• Whether the core logic that originally drove the stock price up has been fully reflected
• Whether the current price still has support from new catalysts
• Whether the volume-price performance when reaching the target price is strong expansion or exhaustion after a spike
• Whether the sector environment still supports further upward revision of expectations

Step 4: Provide a scaling-out handling framework

Provide the direction of handling suggestions based on trigger quality:

• If it is only approaching the target price: focus on observation and verification
• If the target price is reached steadily: consider scaling out and retaining a tracking position
• If it strongly crosses the target price: consider reassessing the target rather than mechanically handling it all at once
• If it pulls back immediately upon reaching the price: focus on reminding about expectation realization and drawdown risk

Step 5: Add reassessment conditions

If it is judged that the target price needs to be reassessed, explain which conditions must be met for a reasonable upward revision, such as:

• Fundamentals verification exceeds expectations
• New catalysts are significantly stronger than the original assumptions
• Structural breakout and sustained absorption

Step 6: Output the target price trigger card

The final output should clearly state "current status, handling suggestions, retention conditions, invalidation conditions" and should not show the internal reasoning process.

Output Structure

---

{Stock Name} Target Price Trigger Alert

I. Trigger Status

• Target Price: {Price}
• Current Relationship: {approaching/reached/crossed/pulled back}
• Nature of Target Price: {research target/trading target/technical target/self-defined target}

II. Current Judgment

• Degree of Expectation Realization: {high/medium/low}
• Judgment of Further Upside Space: {high/medium/low}
• Drawdown Risk Judgment：{High/Medium/Low}

III. Handling Recommendations

• Recommended Action：{Observe/Realize in Batches/Keep Position/Re-evaluate}
• Reason for Action：{One-sentence explanation}
• If holding continues, focus on：{Verification signal}
• If starting to realize, priority principle：{Discipline reminder}

IV. Re-evaluation Conditions

• {Under what conditions expectations can be raised again}
• {Under what conditions it should be confirmed that the target price has basically been reached}

---

Quality Requirements

1. Handling at target price must simultaneously consider the degree of expectation fulfillment and new catalysts, and must not be handled mechanically.
2. Batching recommendations should reflect discipline and avoid vague expressions.
3. If the basis for the target price itself is weak, clearly indicate that its reference value is limited.
4. Different frameworks should be given for "strongly breaking through the target price" and "touching the price and then pulling back."
5. The output should serve execution, not be written as general valuation commentary.