Data dependencies and execution prerequisites
It is recommended to use Wind wind-mcp-skill to obtain the 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 and resumption from an "event name" into a "framework for the 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 the 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 the trigger reason
Focus on sorting out the core reasons that triggered the suspension or 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 reason is a combination of multiple factors, identify the main cause and do not expand on 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 post-resumption impact mechanism
The core of a suspension/resumption event is not "what happened," but "how the market will price it." Key judgments are needed on:
- Whether it is positive news realized, risk released, or uncertainty delayed
- Whether after resumption it is more likely to face a catch-up rally, catch-up decline, volatile turnover, or continued speculation
- Whether there is a liquidity shock, emotional venting, or regulatory constraint
Step 5: Distill the post-resumption observation framework
If trading has resumed or is about to resume, clearly provide:
- The price and trading signals that need the most attention at the open
- Whether the main event line 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 reflect the closed loop of "cause - progress - impact - follow-up observation" and should not display the information collection process.
Output structure
{Stock Name} Suspension/Resumption Tracking
I. Event Status
- Current Status: {Suspension/Temporary Suspension/Resumption/Pending Resumption}
- Trigger Time: {Date and Time}
- Core Reason: {One sentence}
II. Event Timeline
| Time | Progress | Impact on Market Understanding |
|---|---|---|
| {Time} | {Event} | {Impact} |
III. Impact Judgment
- Event Nature：{leans bullish/leans bearish/neutral/still uncertain}
- Whether uncertainty has decreased：{high/medium/low}
- Main risks after trading resumes：{risk}
- Main opportunities after trading resumes：{opportunity}
IV. Post-Resumption Observation Framework
- What to look at first：{price/volume/takeover of orders/short covering}
- Signals confirming strength：{signal}
- Signals of weakening or failure：{signal}
Quality requirements
- Do not remain only at the level of event names; explain the actual path of impact on pricing.
- If disclosure remains insufficient, clearly state where the remaining uncertainty lies.
- Post-resumption judgments should pay special attention to liquidity and sentiment shocks, and must not rely only on the wording of announcements.
- The interpretive frameworks for long suspensions and brief temporary halts should be distinguished.
- The output should help users build follow-up observation, not just complete a news summary.