agentsclimarketplace

Event calendar

Skill blaze10011/market-flow-desk/.claude/skills/event-calendar

Scheduled-risk radar — upcoming earnings dates + market-wide events (the gap risk a stop can't protect against). Use when the user asks "when does <ticker> report", "any earnings coming up", "what's on the calendar", "events this week", "is it safe to hold <ticker> through earnings", "when's the Fed meeting / CPI", "any catalysts for my positions", or before holding a swing trade across a possible report.From its SKILL.md

Install
npx -y skills add blaze10011/market-flow-desk --skill event-calendar

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 343 tokens by cl100k_base, as published. Nobody here has run it

Event / Earnings Calendar

Make sure the user is never blindsided by a scheduled event that gaps a stock through their stop overnight. Earnings are the main risk; Fed/CPI/jobs move the whole market (and the user's correlated book) at once.

Steps

  1. Run from the project root: python3 scripts/events.py [TICKERS...] [--window 20] It reads the user's open positions (data/trading-log.xlsx, Open Positions sheet) + traded names, pulls each stock's NEXT earnings date (yfinance), flags any inside the hold window, and lists market-wide events from data/macro_events.yaml.

  2. Interpret only what it prints. Lead with the flagged earnings (inside the hold window = overnight gap risk a stop can't catch), then the macro events.

  3. For any flagged name, give the user the choice — don't tell them what to do, frame it:

    • Step aside before the date (bank the gain / small loss, re-enter after).
    • Trim to a smaller position so a gap hurts less.
    • Hold through only as a conscious gamble, sized down. This pairs with the #4 JPMorgan-Earnings analysis: the calendar says WHEN, that skill says WHAT to expect (implied move, beat/miss history).

Notes

  • Macro dates in data/macro_events.yaml are maintained manually — refresh them every few weeks (or offer to update via a quick web check).
  • The point is "never surprised by a date," not "never trade earnings." Decision support, not advice.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.