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 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 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 mechanical selling upon reaching the price, but rather judging the current odds, degree of expectation realization, and position-handling priority after the target price is triggered.

Execution process

Step 1: Confirm the target price background

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 observation 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 shows strong expansion or exhaustion after a spike
• Whether the sector environment still supports further upward revision of expectations

Step 4: Provide a scaling framework

Provide the direction of handling suggestions based on the 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 in batches and retaining a tracking position
• If the target price is crossed strongly: consider reassessing the target rather than mechanically handling it all at once
• If it pulls back immediately upon touching the price: focus on reminding about expectation realization and pullback 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, for example:

• Fundamentals verify better than expected
• New catalysts are significantly stronger than the original assumption
• Structural breakout with sustained follow-through buying

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

1. Trigger status

• Target price: {price}
• Current relationship: {approaching/reached/crossed/pulled back}
• Nature of the target price: {research target/trading target/technical target/self-set target}

2. Current judgment

• Degree of expectation realization: {high/medium/low}
• Judgment of further upside space: {high/medium/low}
• Judgment of pullback risk: {High/Medium/Low}

III. Handling Suggestions

• Recommended Action: {Observe/Scale out in batches/Keep position/Re-evaluate}
• Reason for Action: {One-sentence explanation}
• If continuing to hold, focus on: {Verification signal}
• If starting to realize gains, priority principle: {Discipline reminder}

IV. Re-evaluation Conditions

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

---

Quality Requirements

1. Handling upon reaching the price must consider both the degree of expectation realization and new catalysts, and must not be handled mechanically.
2. Batch recommendations should reflect discipline and avoid vague expressions.
3. If the target price itself is based on weak grounds, it must be clearly noted that its reference value is limited.
4. Different frameworks should be given for "strongly breaking through the target price" and "pulling back immediately upon touching the price".
5. The output should serve execution and not be written as general valuation commentary.