OneWave-AI/open-agent-stack / plugins/market-desk/skills/earnings-watch
earnings-watch
VerifiedEarnings-season prep for your holdings and watchlist -- report dates, what the market is actually watching per name, prior-quarter context, and a post-report debrief template. Preparation, not prediction. Use in the weeks around earnings season.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
SKILL.md
View on GitHub---
name: earnings-watch
description: Earnings-season prep for your holdings and watchlist -- report dates, what the market is actually watching per name, prior-quarter context, and a post-report debrief template. Preparation, not prediction. Use in the weeks around earnings season.
---
# Earnings Watch
Earnings season punishes the unprepared with surprises and rewards the prepared with context. This skill builds the calendar and the per-name prep sheet -- what to watch, not what will happen. No forecasts, no trade suggestions.
## Workflow
1. **Build the calendar.** For each holding/watchlist ticker: confirmed or expected report date and time (web-verified; expected dates marked as unconfirmed), sorted chronologically. Flag clusters -- three holdings reporting the same week deserves knowing in advance.
2. **Per-name prep sheet.** For each upcoming report: what the company guided last quarter (the promise being graded), the 2-3 line items coverage says matter this time (a margin number, a subscriber count, a segment's growth), any pre-announcements or peer results that set expectations, and how the stock has behaved into recent prints (context, not prediction).
3. **The holder's questions.** Per name, what this report could clarify about the owner's original thesis: "You hold this for the cloud segment -- watch whether its growth re-accelerated." Tie the watching back to the reason for owning.
4. **Post-report debrief** (on request, after a print): what was reported vs. guided, what management said about the items flagged, and whether anything changed the facts of the holding thesis -- laid out for the owner to judge, not judged for them.
## Rules
- No predictions -- not of results, not of stock reactions. The prep sheet says what to watch, never what will happen.
- Dates get verified and labeled confirmed/expected; a wrong earnings date is the most embarrassing possible error here.
- Expectations context comes from cited coverage, marked as narrative, not fact.
- The debrief reports; the owner concludes. Anything resembling "this changes the thesis, consider selling" is out of scope and says so.
- Sources and dates on everything; earnings-adjacent web data goes stale in hours.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |