Data dependencies and execution prerequisites
It is recommended to use Wind wind-mcp-skill to obtain underlying data. Before execution, first check whether wind-mcp-skillis 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 镜像（国内）
npx skills add https://gitee.com/wind_info/wind-skills.git --skill wind-mcp-skill -g -y
Skill positioning
This skill is used to build an executable earnings season tracking calendar around a group of stocks or a coverage pool. The output focus is not simply listing release dates, but organizing "which are most important, what should be done in advance, how to follow up after earnings, and which days are prone to conflicts" into an actionable research schedule.
Execution process
Step 1: Confirm the coverage pool, time range, and scheduling purpose
First clarify the targets and time range to be tracked, for example:
- Watchlist
- A certain industry or theme coverage pool
- Current holdings and key watchlist
- The next two weeks, one month, or the entire earnings season
If the user does not specify, by default cover only the stocks mentioned this time, and focus on the most recent earnings cycle.
Step 2: Organize earnings dates and status
Confirm each company's current earnings arrangements one by one, and distinguish:
- Whether the date is confirmed or tentative
- Whether it is released pre-market, after hours, or intraday
- Whether it is accompanied by an earnings call, guidance update, or management communication
- Whether it conflicts with major macroeconomic events, industry conferences, or other key companies
If the date has not yet been officially confirmed, mark it clearly and do not write an estimated date as a confirmed schedule.
Step 3: Prioritize key companies
Not all earnings deserve equal effort. When ranking, focus on considering:
- Whether it is a current holding or a core candidate target
- Whether a significant expectation gap may occur
- Whether it is in a stage of logic verification or inflection
- Whether it will affect judgment on the entire sector or theme
- Whether it has chain effects with multiple related targets
Step 4: Break down task packages before and after earnings
Around each key earnings report, separately arrange:
- Forward-looking questions to prepare before earnings
- Numbers to prioritize checking on the evening of earnings
- Directions to focus on during the earnings call
- Conclusions to update within 24 hours after earnings
- Secondary questions to continue verifying within one week
Only in this way can the calendar be not just a "timetable", but a real workbench.
Step 5: Identify conflicts, gaps, and resource allocation issues
If multiple key earnings reports are concentrated on the same day or in the same time period, clarify:
- Which companies must take priority
- Which can be tracked only lightly
- Which events have sequential dependencies
- Which dates require templates or contingency plans prepared in advance
Step 6: Integrate into a final earnings season schedule
The final output should be a research calendar that is easy to execute directly, without showing the intermediate collection process. The content should combine both a time view and a task view.
Output structure
Earnings calendar plan ({YYYY-MM-DD})
I. The 3 most important earnings reports this cycle
- {Company A}: {Why it matters}
- {Company B}: {Why it matters}
- {Company C}: {Why it matters}
II. Earnings Calendar Summary
| Date | Company | Release Time | Priority | Pre-earnings Focus | Post-earnings Focus |
|---|---|---|---|---|---|
| {Date} | {Company} | {Pre-market/Post-market} | High | {Content} | {Content} |
III. Key Task Arrangements
Pre-earnings
- {Task 1}
- {Task 2}
- {Task 3}
Post-earnings
- {Task 1}
- {Task 2}
- {Task 3}
IV. Conflicts and Reminders
- Schedule conflicts: {Content}
- Dates requiring advance preparation: {Content}
- Items that can be deprioritized: {Content}
Quality Requirements
- An earnings calendar must not provide only dates; it must also include priorities and task arrangements.
- When dates are uncertain, clearly mark them as tentative to avoid creating an incorrect schedule.
- Key companies should be ranked by portfolio importance, expected variance, and sector influence, rather than listed equally.
- The output should facilitate execution and review, and avoid being written as a static list.
- If multiple key earnings dates conflict, provide clear resource allocation recommendations.