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 a 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 extract truly valuable new information from earnings calls or similar management communication materials, focusing on answering "what exactly did management newly say, which tones and wording are worth being alert to, what analysts are most probing, and what content will change the focus of subsequent research." The output should not be a paragraph-by-paragraph paraphrase of the meeting, but should help users grasp the judgments most worth updating after the meeting.
Execution Process
Step 1: Confirm the meeting scope and reading objectives
First confirm which earnings call, investor communication meeting, or business update meeting it corresponds to, and clarify the user's main purpose of interest:
- Quickly review the key points of the meeting
- Determine whether management's statements reinforce the original view
- Extract meeting notes for team sharing
- Identify risk points that need further verification after the meeting
If the user does not specify, proceed by default with "quickly updating research judgments after the meeting."
Step 2: Capture new information first, then look at repeated statements
Meeting materials usually contain a large amount of repeated statements, so priority should be given to screening out the parts with genuine incremental value:
- Marginal updates on performance, demand, orders, profit margins, etc.
- Supplementary answers to questions that were not clarified previously
- Direct responses to or avoidance of market controversies
- The latest statements on future pace, priorities, and capital allocation
If a section merely repeats the public line, it should be downgraded to avoid occupying the core summary.
Step 3: Identify changes in management tone and signals
In addition to the literal content, also pay attention to changes in the way things are expressed, including:
- More optimistic, more cautious, or more defensive than last time
- More willing to elaborate on certain types of questions, or deliberately contracting
- Describing risks more specifically, or using vague expressions to obscure uncertainty
- Whether there are inconsistencies, vagueness, or diversion of focus
The goal of this step is to capture the difference between "what was said" and "how it was said."
Step 4: Extract the true focus of the Q&A session
The content that analysts or investors repeatedly probe in the Q&A is usually closer to the core market disagreement. Focus on summarizing:
- What variables are repeatedly questioned
- Whether management's answers are direct, sufficient, and verifiable
- Which questions were answered strongly, and which remain vague
- Whether a certain question exposed insufficient preparation by management or deepening market concerns
Step 5: Consolidate post-meeting updates and warning signs
After reading the meeting, it is necessary to clarify:
- Which original views were reinforced
- Which new information requires revising the research framework
- Which risks, although not fully exposed, have already shown signs
- Which operating variables most need continued verification going forward
Step 6: Integrate into a post-meeting summary draft
The final output should be a post-meeting distillation that can be forwarded directly and used directly for internal discussion, without showing the paragraph-by-paragraph reading process or a pile of raw excerpts.
Output Structure
{Stock Name} Earnings Call Summary ({YYYY-MM-DD})
I. 30-Second Conclusion
- Most important new information from this meeting: {one sentence}
- Overall management tone: {more positive / basically stable / turning cautious}
- Most noteworthy warning signal: {one sentence}
- Post-meeting judgment: {thesis strengthened / pending verification / rising risk}
II. New Information from the Meeting
- New information 1: {content}
- New information 2: {content}
- New information 3: {content}
III. Changes in Management Tone
| Observation point | This time's performance | Implication |
|---|---|---|
| Demand statement | {content} | {explanation} |
| Margin/cost statement | {content} | {explanation} |
| Future pace statement | {content} | {explanation} |
IV. Q&A Focus and Answer Quality
- Question the market cares about most: {content}
- Question answered most thoroughly: {content}
- Question answered most vaguely: {content}
V. Post-Meeting Warning Signs and Follow-Up Verification
- {warning sign 1}
- {warning sign 2}
- {follow-up verification point}
VI. Research Update Recommendations
- Judgment that should be updated: {content}
- Parts on which no conclusion should be drawn yet: {content}
Quality Requirements
- New information must be presented first; do not treat repeated meeting content as the focus.
- Do not merely excerpt management's original words; translate them into research implications.
- The focus and answer quality of the Q&A session must be handled separately, because it is usually closest to market disagreements.
- Tone changes should be judged in context, avoiding misjudging normal wording differences as trend changes.
- The output should serve to 'update views after the meeting,' rather than becoming a lengthy meeting minutes.