Data dependencies and execution prerequisites
It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether there is already 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 complete the final "trade health check" before the market opens. The output focus is not to redo a broad, comprehensive analysis, but to quickly confirm through a checklist whether candidate trades meet execution conditions, which risks are known, which conditions are unmet, and which orders should be abandoned first, thereby reducing impulsive last-minute actions and operational omissions.
Function overview
The core function of this skill is: check catalysts, liquidity, and risk before placing orders.
It emphasizes doing a final check of plan completeness, the day's environment, event risk, and execution details, helping users turn pre-market preparation into a truly actionable order sheet.
Use cases
- The user needs to quickly check candidate trades prepared for execution that day before the market opens.
- After a team morning meeting, the conclusions need to be compressed into a checklist that can be followed directly.
- There is a lot of pre-market news, and the user is worried about missing major events or liquidity risks.
- The user wants to reduce the probability of "having thought it through clearly, but trading chaotically once the market opens."
Working principles
- The goal of the pre-market check is to clear mines and set priorities, not to rewrite a complete research report.
- Every candidate trade must answer "why do it today, what justifies doing it, and under what circumstances would we not do it."
- Event risk, liquidity, and environment fit are the highest-priority pre-market checks.
- If any key condition is unmet, decisively downgrade it to observation rather than forcing execution.
- The main text outputs only the checklist and execution judgment, and does not discuss the internal implementation process.
Execution process
Step 1: Confirm the day's candidate pool and execution priorities
First organize the trade targets prepared for handling that day:
- Which are high-priority planned orders
- Which are only observation orders
- Which are continuation actions for existing positions
- Whether multiple trades are competing for the same risk budget
Step 2: Check overnight and pre-market new information
Before the market opens, first see whether there are variables that change the original plan:
- Whether there are changes in earnings reports, announcements, regulation, policy, or industry news
- Whether there is obvious disruption in overseas markets, related assets, or sectors
- Whether the company has new rumors, rumor denials, trading suspensions/resumptions, or important meetings
- Whether the original catalyst has strengthened, weakened, or become invalid
Step 3: Check plan completeness
Each candidate order must have the minimum execution elements:
- Whether entry conditions are clear
- Whether position size and batch pacing are clear
- Whether stop-loss and take-profit rules are clear
- Whether a contingency plan is already in place if the trigger fails to meet expectations
If any one of these is missing, it should not be regarded as a complete plan.
Step 4: Assess the day's execution environment
The easiest thing to overlook before the market opens is "whether today is suitable for this type of order":
- Whether the index and sentiment environment support chasing strength or buying dips
- Whether the target sector is still on the main line or an active direction
- Whether there are major macroeconomic time points today that could amplify volatility
- Whether the market faces an obvious risk of style rotation
Step 5: Check liquidity and price deviation risk
Having a plan does not mean it can be executed comfortably:
- Whether the pre-market price has already deviated from the ideal range
- Whether a gap up or gap down would change the original risk-reward
- Whether trading activity is sufficient to support the planned position
- If the market moves rapidly at the open, whether execution needs to be delayed
Step 6: Output execution, watch, and abandon tiers
Tier the candidate orders according to the pre-market check results:
- Executable
- Needs confirmation
- Not today
At the same time, explain the reasons for downgrading to avoid being overturned again by emotions during the session.
Step 7: Form the final pre-market execution sheet
The final output should let the user clearly know in the last few minutes before the open “who to look at first, who can be traded, what to wait for, and which orders are canceled today.” The main text should retain the list, priorities, and abandonment conditions.
Output structure
Pre-market execution checklist ({YYYY-MM-DD})
I. 30-second conclusion
- Today's highest-priority trades: {name list}
- Executable count: {count}
- Count needing confirmation: {count}
- Count to cancel or downgrade: {count}
- Today's main risks: {one sentence}
II. Candidate pool checklist
| Stock | Original planned direction | New pre-market variables | Environment fit | Execution status | Notes |
|---|---|---|---|---|---|
| {target 1} | {content} | {content} | {high/medium/low} | {execute/wait/cancel} | {explanation} |
| {target 2} | {content} | {content} | {level} | {status} | {explanation} |
III. Key execution orders
{stock name}
- Execution rationale: {content}
- Pre-open conditions: {content}
- If it opens high: {content}
- If it opens low: {content}
- Abandonment conditions: {content}
IV. Today's do-not-trade list
- {target 1}: {reason}
- {target 2}: {reason}
V. Observation points for the first 30 minutes after the open
- {observation point 1}
- {observation point 2}
- {observation point 3}
Quality requirements
- The pre-market checklist must highlight the three tiers of “can trade, wait to trade, do not trade.”
- It is necessary to clarify whether new overnight variables change the original plan.
- Each execution order must provide a handling plan for a gap up, a gap down, or no trigger.
- If conditions are incomplete, proactively downgrade rather than reluctantly retain it.
- The output should serve rapid pre-open decision-making, not lengthy repetition of research content.