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 explain why a stock is suspended, why it resumes trading, what stage the event has progressed to, and what needs the most attention after resumption. The goal is to transform suspension/resumption from an "event name" into a "framework of actual impact on stock price and expectations."
Execution process
Step 1: Confirm suspension/resumption status
First clarify which type the event belongs to:
- Suspension
- Temporary suspension
- Long-term suspension
- Resumption
- Disclosure of latest progress before resumption
At the same time, confirm the time the event occurred, its duration, and whether it is still in a stage of incomplete information.
Step 2: Identify trigger reasons
Focus on sorting out the core reasons that triggered the suspension/resumption:
- Major asset restructuring, mergers and acquisitions, private placements, changes in control
- Major announcements pending disclosure
- Abnormal stock price fluctuations, regulatory investigation
- Financial or governance risks
- Delisting risk, debt risk, major litigation
If the reasons are a combination of multiple factors, identify the main cause rather than expanding on all of them equally.
Step 3: Sort out the event timeline
Reconstruct the event along a timeline and explain:
- When the first suspension or temporary suspension occurred
- What key information was disclosed during the period
- What level of information transparency has currently been reached
- Whether resumption means the core uncertainty has been partially eliminated
Step 4: Assess the impact mechanism of resumption
The core of a suspension/resumption event is not "what happened," but "how the market will price it." Key judgments needed:
- Whether it is realization of positive news, release of risk, or postponement of uncertainty
- Whether after resumption it is more likely to face catch-up gains, catch-up declines, range-bound turnover, or continuous speculation
- Whether there is a liquidity shock, emotional release, or regulatory constraint
Step 5: Distill the post-resumption observation framework
If trading has already resumed or is about to resume, clearly provide:
- The price and volume signals that need the most attention at the open
- Whether the main event theme is strong enough to support continued trading
- Which performances indicate that the market still does not recognize the currently disclosed content
Step 6: Organize into a suspension/resumption tracking summary
The final output should embody the closed loop of "reason - progress - impact - follow-up observation" and should not show the information collection process.
Output structure
{Stock Name} Suspension/Resumption Tracking
1. Event status
- Current status: {Suspension/Temporary suspension/Resumption/Pending resumption}
- Trigger time: {date time}
- Core reason: {one sentence}
2. Event timeline
| Time | Progress | Impact on market understanding |
|---|---|---|
| {time} | {event} | {impact} |
3. Impact judgment
- Nature of the event: {bullish/bearish/neutral/still uncertain}
- Whether uncertainty has decreased: {high/medium/low}
- Main risks after resumption of trading: {risks}
- Main opportunities after resumption of trading: {opportunities}
IV. Observation framework after resumption of trading
- What to look at first: {price/volume/absorption/buyback}
- Signals confirming strength: {signals}
- Signals of weakening or failure: {signals}
Quality requirements
- Do not remain only at the level of the event name; explain its actual impact path on pricing.
- If disclosure is still insufficient, clearly state where the remaining uncertainty lies.
- Judgments about resumption of trading should pay special attention to liquidity and sentiment shocks, and must not look only at the wording of the announcement.
- The interpretive frameworks for long suspensions and short temporary halts should be distinguished.
- The output should help users construct subsequent observations, rather than only completing a news summary.