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 a local 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 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 a set of actionable research schedules.
Execution process
Step 1: Confirm the coverage pool, time range, and scheduling purpose
First clarify the targets and time range that need to be tracked, for example:
- Watchlist stock list
- 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-market, 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, it should be clearly marked, and estimated dates should not be written as confirmed schedules.
Step 3: Prioritize key companies
Not all earnings reports deserve equal investment. When ranking, focus on considering:
- Whether it is a current holding or a core candidate target
- Whether there may be a significant expectation gap
- Whether it is in a stage of thesis validation or inflection point
- Whether it will affect judgment on the entire sector or theme
- Whether it has chain effects with multiple related targets
Step 4: Break down the task packages before and after earnings
For each key earnings report, separately arrange:
- Preview questions that need to be prepared before earnings
- The numbers that need to be checked first on the night of earnings
- The directions to focus on listening for in the earnings call
- Conclusions to be updated within 24 hours after earnings
- Secondary questions that need continued verification within one week
Only in this way is the calendar not just a "schedule", but truly a 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 be prioritized
- Which can only be lightly tracked
- Which events have sequential dependencies
- Which dates require advance preparation of templates or contingency plans
Step 6: Integrate into the final earnings season schedule
The final output should be a research calendar that is convenient for direct execution, without showing the intermediate collection process. The content should have both a time view and a task view.
Output structure
Earnings calendar plan ({YYYY-MM-DD})
I. The 3 most important earnings reports in this cycle
- {Company A}: {Why it is important}
- {Company B}: {Why it is important}
- {Company C}: {Why it matters}
II. Earnings Calendar Master Table
| Date | Company | Release Time | Priority | Key Points Before Earnings | Key Points After Earnings |
|---|---|---|---|---|---|
| {Date} | {Company} | {Pre-market/Post-market} | High | {Content} | {Content} |
III. Key Task Arrangements
Before Earnings
- {Task 1}
- {Task 2}
- {Task 3}
After Earnings
- {Task 1}
- {Task 2}
- {Task 3}
IV. Conflicts and Reminders
- Schedule Conflicts: {Content}
- Dates Requiring Advance Preparation: {Content}
- Items That Can Be Downgraded: {Content}
Quality Requirements
- The earnings calendar cannot only provide dates; it must also provide priorities and task arrangements.
- When dates are uncertain, they must be clearly marked as tentative to avoid creating incorrect schedules.
- Key companies should be ranked by portfolio importance, expectation gap, and sector influence, rather than listed equally.
- The output should be easy to execute and review, and should avoid being written as a static checklist.
- If multiple key earnings reports conflict, clear resource allocation recommendations should be provided.