Data Dependencies and Pre-Execution Conditions
It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether there is wind-mcp-skilllocally; 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 solve the most common and most disorder-prone type of problem: "how to sell after making a profit." The output focus is not on pursuing the highest selling point, but on helping users find a balance between realizing profits, protecting floating gains, and preserving trend space, and establish a repeatable selling framework.
Function Overview
The core function of this skill is: designing a staged take-profit path and realization rules.
It emphasizes first defining under what circumstances part of the profit should be locked in and under what circumstances profits should continue to run, then writing the selling rhythm into clear actions.
Use Cases
- The position is already profitable, but it is unclear whether to sell all at once, sell in batches, or continue holding.
- A strong stock is surging rapidly, and the user is worried about getting hit on both sides by "selling too early" and "giving back profits."
- A swing trade is approaching the target zone and the exit rhythm needs to be designed in advance.
- The team wants to standardize selling discipline and reduce intraday discretionary take-profit decisions.
Working Principles
- The goal of take-profit is to optimize the return distribution, not to pursue the highest selling point.
- Selling rules should simultaneously consider target levels, trend strength, volume-price structure, and market environment.
- Realizing profits and preserving trend space must coexist and cannot be taken to extremes.
- Batch arrangements should be written down in advance to avoid arbitrarily changing rules after making a profit.
- The main text only gives judgments and plans, and does not discuss the internal implementation process.
Execution Process
Step 1: Confirm the position stage and the nature of the profit
First clarify where the current profit comes from:
- Whether it is a rapid surge after an event-driven move, or steady progress within a trend
- Whether the current profit is in the early stage, middle stage, or later stage
- Whether this trade was originally intended as a quick in-and-out, or whether the user is willing to keep a portion to follow the trend
- Whether the user is more worried about giving back profits or more worried about selling too early
Step 2: Define the basic target levels and key realization zones
Turn "it's about time to sell" into clearer levels:
- What position the first realization zone usually corresponds to
- Whether the second realization zone is related to the previous high, the target zone, or obvious resistance
- If the price far exceeds expectations, whether to keep a trend tail position
- If the target zone has not been reached but the structure has clearly weakened, whether to adjust the plan in advance
Step 3: Design the staged selling ladder
Split the position into a rhythm that is easier to execute:
- The first batch is used to lock in certain profits
- The second batch is used to hedge drawdown risk
- The final batch is used to preserve flexibility for trend continuation
At the same time, clarify:
- What the trigger condition is for each batch
- Whether to sell by price level or by trend change
- Whether partial intraday realization is allowed, with the remaining position confirmed again at the close
Step 4: Set rules for moving the break-even level upward and protecting floating profits
Profit management is not only about selling, but also includes dynamic protection:
- After the first realization, should the stop-loss be moved above the cost line
- If the trend continues to strengthen, should the protection level be raised gradually
- If a pullback occurs but the structure is not yet broken, which fluctuations can be tolerated
- Under what circumstances should a "trend position" be switched back to a "realization position"
Step 5: Determine whether to accelerate or slow down realization based on the environment
The selling pace must be subordinate to the environment:
- When market sentiment is high, can selling be appropriately delayed
- When the sector tide recedes, is more active realization needed
- Does the individual stock show signals such as high-volume stagnation, spike-and-fade, or the end of acceleration
- If external risks rise, should protecting existing profits take priority
Step 6: Supplement unexpected scenarios and tracking nodes
Write out common variants in advance:
- How to handle a gap-up that reaches the target zone directly
- How to handle obvious weakening before reaching the target zone
- After a pullback and then a new high, is buying back after selling allowed
- How to define the premise for "continuing to hold the remaining position"
Step 7: Form the final take-profit draft
The final output should help the user clearly know "when to sell first, how much to sell, why to keep some, and what the remaining position relies on to continue holding." The main text should retain the tiered plan, protection rules, and scenario responses.
Output structure
Tiered take-profit plan ({YYYY-MM-DD})
I. 30-second conclusion
- Position object: {stock name}
- Current profit stage: {early / middle / late}
- Take-profit tendency: {actively realize / lock in profits in batches / continue holding the trend tail position}
- First realization trigger point: {content}
- Premise for holding the remaining position: {one sentence}
II. Take-profit gradient
| Batch | Trigger condition | Suggested action | Logic for the remaining position |
|---|---|---|---|
| First batch | {content} | {content} | {content} |
| Second batch | {content} | {content} | {content} |
| Tail position | {content} | {content} | {content} |
III. Rules for protecting floating profits
- Condition for moving up to breakeven: {content}
- Dynamic protection level: {content}
- Premise for trend holding: {content}
IV. Responses to abnormal scenarios
- {scenario 1}
- {scenario 2}
- {scenario 3}
V. Risk warnings
- {risk 1}
- {risk 2}
- {risk 3}
Quality requirements
- The take-profit plan must reflect batch logic, not a single target price.
- Each batch action must have a clear trigger basis.
- It is necessary to explain when to protect floating profits and when to continue letting profits run.
- The impact of environmental changes on the take-profit pace must be stated.
- The output should help manage profitable positions, rather than create an obsession with "selling at the highest point."