major_announcement_impact_skill

Major Announcement Impact Skill

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 locally 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 analyze the actual impact of major announcement events on the company, shareholders, and market expectations, focusing on answering "what did this announcement change, which layer will the impact land on first, who benefits and who loses, and what key uncertainties remain afterward." The output focus is not to rewrite a summary of the announcement, but to clearly break down the impact chain.

Execution process

Step 1: Confirm the announcement type and core facts

First confirm which type of major matter the announcement belongs to, for example:

• Mergers and acquisitions, divestitures, spin-offs, restructuring
• Share reductions, share increases, private placements, rights issues, convertible bonds
• Major contracts, orders, cooperation, litigation, regulatory penalties
• Capacity construction, asset disposal, changes in control

At the same time, sort out the key facts: who is involved, how large the amount is, the timing arrangements, condition restrictions, and whether approval is still required.

Step 2: Establish the baseline state before the event

The impact of an event cannot be judged in isolation from the original background. It is necessary to first clarify:

• What operating and valuation state the company was in before the announcement
• What the market was originally most worried about or most looking forward to
• Whether this matter had already been rumored or expected
• Whether the event reinforces the main line or changes the main line

Step 3: Break down direct impact and second-order impact

Around the announcement itself, judge in layers:

• Direct impact on revenue, profit, cash flow, and the balance sheet
• Structural impact on control, governance, financing capacity, and shareholder returns
• Medium-term impact on industry position, competitive landscape, and strategic direction
• Short-term impact on market sentiment and valuation anchors

Do not mix all consequences together; distinguish between what is immediately visible and what is transmitted later.

Step 4: Identify who benefits, who loses, and who is still watching

Major announcements often do not have a one-sided impact, and it is necessary to clarify:

• Whether the company itself directly benefits
• Which original shareholders, new investors, management, creditors, or supply chain parties are affected
• Whether there are spillover effects on peers, upstream and downstream, or thematic sectors
• Which type of stakeholder's attitude is most likely to affect the event's completion

Step 5: Assess uncertainty and completion thresholds

Further explain why this type of event cannot yet be easily concluded, with key points including:

• Risks in approval, delivery, and execution pace
• Whether there is controversy over price, valuation, or consideration structure
• Whether the market may overestimate short-term gains and underestimate long-term costs
• Which conditions, if unmet, would require overturning the original interpretation

Step 6: Integrate into a finished event impact draft

The final output should help users quickly complete "event characterization + impact breakdown + risk warnings," without showing internal retrieval paths.

Output structure

---

{Stock Name} Major Announcement Impact Interpretation ({YYYY-MM-DD})

I. 30-second conclusion

• Nature of the event: {one sentence}
• Core impact: {Slightly positive / Neutral but complex / Slightly negative + brief description}
• First affected level: {Operations / Financials / Shareholder structure / Sentiment}
• Current biggest uncertainty: {one sentence}

II. Overview of announcement facts

Item	Content
Event type	{content}
Key participants	{content}
Amount/scale	{content}
Timeline	{content}
Additional conditions	{content}

III. Breakdown of the impact chain

• Direct impact: {content}
• Second-order impact: {content}
• Impact that may be overlooked: {content}

IV. Beneficiaries and parties hurt

• Beneficiaries: {content}
• Parties hurt: {content}
• Parties still needing observation: {content}

V. Implementation risks and follow-up observation

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

VI. Current action recommendations

• Recommendation: {prioritize tracking / cautiously optimistic / retain judgment / wait for implementation}
• Reason: {explanation}

---

Quality requirements

1. For major announcements, facts must be stated first, then the impact, to avoid preconceptions.
2. Direct impact and second-order impact must be handled in layers and must not be mixed into one general statement.
3. Do not mistakenly write "room to tell a story" as "value already realized."
4. If the event still requires approval or closing, implementation risk should be placed at the core.
5. The output should help users determine whether this is an event that can be traded, tracked, or temporarily avoided.