SuperAPI AI Directory

dip_buy_decision_skill

General & other

View repository

Updated 10-16 01:30

About this skill

Dip Buy Decision Skill

Data dependencies and execution prerequisites

It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether the local environment already has wind-mcp-skill; 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 determine whether "this decline is an opportunity, or the beginning of trouble." The output focus is not to encourage blind bottom-fishing, but to help users distinguish normal pullbacks within a trend, event-driven mispricing, structural weakening, and pure downside continuation, and to write the absorption action as a boundary-defined trial-and-error plan.

Function overview

The core function of this skill is: determine whether a pullback can be absorbed and how to absorb it.

It emphasizes first judging the nature of the pullback, then deciding whether to try, how to phase in, and when to abandon, helping users avoid misjudging every decline as an opportunity.

Use cases

  • After a strong stock pulls back, the user wants to determine whether a dip-buying window has arrived.
  • After earnings, announcements, or market volatility, the stock price falls rapidly, and it is necessary to distinguish mispricing from a breakdown.
  • The user wants to position during a pullback, but does not want dip buying to become catching a falling knife.
  • The team needs to manage "worth absorbing" and "only observable" separately.

Working principles

  1. Before dip buying, one must first judge the nature of the pullback, rather than first deciding whether to buy.
  2. Only when the trend is not broken, the logic is not broken, and the environment is not broken does absorption discussion have value.
  3. Dip buying is more suitable for phased trial and error, not for a one-time heavy-position judgment.
  4. Abandonment criteria must be written clearly in advance to avoid adding more as it keeps falling.
  5. The main text only presents judgment basis and plans, and does not discuss the internal implementation process.

Execution process

Step 1: Confirm the pullback background and decline type

First determine which category this decline belongs to:

  • Technical pullback after a strong rise
  • Sentiment-driven decline after news or earnings
  • Passive drag caused by systemic market volatility
  • Trend destruction after the logic begins to weaken

Only after first identifying the decline type does subsequent absorption become meaningful.

Step 2: Check whether the original upward logic still holds

The premise for dip buying to hold is "valuable because of the pullback, not valuable because it has deteriorated":

  • Whether the core driver is still present
  • Whether the sector or theme still has activity
  • Whether the market's disagreement over the original logic is only a short-term amplification
  • Whether new negative variables have appeared that change the original judgment

Step 3: Identify the absorption zone and observation zone

Write clearly "where it can be watched after falling":

  • Which positions may form meaningful support
  • Which areas are only continuation pauses and cannot be absorbed hastily
  • How far the current price is from a reasonable observation zone
  • If the price directly breaks below the observation zone, how should it be reevaluated

Step 4: Judge pullback quality and evidence of stabilization

Not every deep decline is worth buying; more important is the way it falls:

  • Whether volume is being released or is out of control during the pullback
  • Whether the decline is an orderly pullback or one-sided stampede
  • Whether positive clues such as stabilization, shrinking volume, and absorption rebound appear
  • If there is no evidence of stabilization, whether to wait for confirmation or directly abandon

Step 5: Design the trial-and-error approach and batching rhythm

For buying on dips, position rhythm deserves even more attention:

  • What level of trial-and-error task should the first tranche alone undertake
  • Under which confirmations is a second tranche allowed later
  • If the pullback continues to deepen, should you pause rather than average down
  • Whether the total planned position should be significantly lower than for breakout-chasing trades

Step 6: Set abandonment criteria and failure boundaries

The most important thing in a buy-on-dip decision is not the entry point, but the stop point:

  • After which position or which type of information appears should you abandon taking the bid
  • Whether consecutive weak rebounds indicate that the bid-taking logic is invalid
  • If the environment deteriorates in sync, whether it is necessary to terminate early
  • When to determine that this is not a pullback but trend damage

Step 7: Form the final buy-on-dip decision draft

The final output should help users know "whether they can take it, where to take it, how much to take first, and under what circumstances they should no longer take it." The main text should retain the judgment of the pullback nature, the bid-taking zone, the rhythm, and the abandonment criteria.

Output structure


Buy-on-Dip Decision Plan ({YYYY-MM-DD})

I. 30-second conclusion

  • Trading target: {stock name}
  • Pullback nature: {healthy pullback / emotional mispricing / trend damage risk}
  • Operational bias: {can try / wait for stabilization / do not take the bid}
  • Observation range: {content}
  • Abandonment criteria: {one sentence}

II. Pullback judgment

Dimension Judgment Impact on conclusion
Original logic integrity {content} {content}
Sector environment {content} {content}
Pullback quality {content} {content}
Stabilization evidence {content} {content}

III. Execution rhythm

  • First tranche trial conditions: {content}
  • Second tranche bid-taking conditions: {content}
  • Conditions for no further additions: {content}

IV. Failure boundaries

  • {boundary 1}
  • {boundary 2}
  • {boundary 3}

V. Risk warnings

  • {risk 1}
  • {risk 2}
  • {risk 3}

Quality requirements

  1. The nature of the pullback must be judged first, and then bid-taking suggestions should be given.
  2. Buy-on-dip suggestions must be paired with batching rhythm and abandonment criteria.
  3. It is necessary to distinguish between "the pullback has reached its target" and "the trend has deteriorated."
  4. If stabilization evidence is insufficient, it should be clearly recommended to continue waiting.
  5. The output should reduce the probability of catching a falling knife, rather than beautifying left-side trading.