wind-alice/conference_call_takeaway_skill

Conference Call Takeaway Skill

Data Dependencies & Prerequisites

It is recommended to use the Wind wind-mcp-skill to obtain underlying data. Before executing, check if wind-mcp-skill is already available locally; if not, prompt the user to install it:

# GitHub
npx skills add Wind-Information-Co-Ltd/wind-skills --skill wind-mcp-skill -g -y

# Gitee Mirror (Domestic)
npx skills add https://gitee.com/wind_info/wind-skills.git --skill wind-mcp-skill -g -y

Skill Positioning

This skill is designed to extract truly valuable new information from earnings calls or similar management communication materials. It focuses on answering: "What new things did management actually say, what tone and wording should be viewed with caution, what did analysts press hardest on, and what content will change the focus of subsequent research?" The output is not a paragraph-by-paragraph recap of the meeting, but rather an aid to help users grasp the most important judgments to update after the call.

Execution Process

Step 1: Confirm the Meeting Scope & Reading Objective

First, confirm which specific earnings call, investor day, or operational update this refers to, and clarify the user's primary use case:

• Quick review of meeting highlights
• Determine if management's statements reinforce existing views
• Distill key takeaways for the team
• Identify risk points needing further verification after the call

If the user does not specify, default to "rapidly update research judgment after the call."

Step 2: Prioritize New Information, Then Repeated Statements

Meeting materials often contain a large amount of repeated statements. First, screen for parts that provide genuinely new value:

• Marginal updates on performance, demand, order backlog, profit margins, etc.
• Supplementary answers to previously unresolved questions
• Direct responses or evasions on market contentious issues
• Latest statements on future pace, priorities, and capital allocation

If a section merely reiterates publicly available information, it should be deprioritized and not occupy the core summary.

Step 3: Identify Management Tone & Signal Changes

Beyond literal content, pay attention to changes in expression, including:

• More optimistic, more cautious, or more defensive compared to the last call
• Willingness to elaborate on certain topics versus deliberately shrinking away from them
• Describing risks in more specific terms versus using vague language to obscure uncertainty
• Inconsistencies, obfuscation, or shifts in focus

The goal of this step is to capture the difference between "what was said" and "how it was said."

Step 4: Distill the True Focus of the Q&A Session

Topics that analysts or investors repeatedly press on during Q&A are usually closer to core market divergences. Focus on summarizing:

• Which variable was repeatedly questioned?
• Were management's answers direct, sufficient, and verifiable?
• Which questions were answered strongly, and which remained vague?
• Did any question reveal management's lack of preparation or deepening market concerns?

Step 5: Document Post-Call Updates & Red Flags

After finishing the call, clarify:

• Which pre-existing views were reinforced
• Which new information requires revising the research framework
• Which risks are not yet fully exposed but have shown early signs
• Which operational variables most urgently need further verification

Step 6: Synthesize into a Final Post-Call Summary

The final output should be a refined summary suitable for direct sharing or internal discussion. It should not show the step-by-step reading process or a pile of raw excerpts.

Output Structure

---

{Stock Name} Earnings Call Takeaways ({YYYY-MM-DD})

1. 30-Second Conclusion

• Most Important New Information from This Call: {One sentence}
• Overall Management Tone: {More Positive / Basically Stable / Turning Cautious}
• Most Worthy Signal to Watch: {One sentence}
• Post-Call Judgment: {Logic Reinforced / Pending Verification / Risk Rising}

2. New Information from the Call

• New Information 1: {Content}
• New Information 2: {Content}
• New Information 3: {Content}

3. Management Tone Changes

Observation Point	This Call's Performance	Implication
Demand Statements	{Content}	{Explanation}
Margin/Cost Statements	{Content}	{Explanation}
Future Pace Statements	{Content}	{Explanation}

4. Q&A Focus and Response Quality

• Market's top concern: {Content}
• Most thoroughly answered question: {Content}
• Most vague answer given: {Content}

5. Post-Call Red Flags & Follow-up Verification

• {Red Flag 1}
• {Red Flag 2}
• {Follow-up Verification Point}

6. Research Update Recommendations

• Judgments that should be updated: {Content}
• Parts to defer judgment on: {Content}

---

Quality Requirements

1. New information must be presented with the highest priority; do not treat repeated meeting content as key points.
2. Do not merely excerpt management's exact words; translate them into implications for research.
3. The focus of the Q&A session and the quality of responses must be handled separately, as they are usually closest to market divergences.
4. Tone changes should be assessed in context, avoiding mistaking normal wording differences for trend shifts.
5. The output should serve the purpose of "updating views after the call," not becoming a lengthy meeting minutes document.