earnings-calendar
Skill1 starsChanged 3 months agoMITView on GitHub
Builds a single-file HTML earnings calendar from viaNexus CORE/EARNINGS_CALENDAR, laid out as a real month grid and colour-coded by market session (pre-market vs post-market). Produces either a static snapshot page or a live page that fetches with the user's own token. Use whenever someone wants to see upcoming earnings — an earnings calendar, reporting schedule, "who reports this week", "when does NVDA report", an earnings season view, or a pre/post-market release breakdown.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- staskh/trading_skillstheir own version, first seen Nov 3, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- staskh/trading_skills★ 405same name
- IngAs8/ClaudeSkill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- election-market-dashboardSkill
- financial-researchSkill
- live-market-dashboardSkill
- mt-newswires-analystSkill
- portfolio-monitorSkill
- rsi-screenerSkill
- transcript-analysisSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Read references/dataset.md before writing any code that touches this dataset.
- Distinctive: line 57
No LLM sits in the fetch loop.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Earnings Calendar
Generate a single HTML file the user opens in any browser. No backend, no build step at view time, no external requests.
Read references/dataset.md before writing any code that
touches this dataset. It documents three things that will otherwise produce a
wrong page: every record is predicted, roughly half carry no session, and the
serving semantics are not what a normal table lookup would suggest.
Two shapes, one template
assets/template.html renders a build-time snapshot if it has one, and shows a
token bar if it doesn't. Same file either way.
export VIANEXUS_TOKEN=sk_...
python3 scripts/build.py # snapshot -> calendar.html
python3 scripts/build.py --no-data # live page, nothing embedded| Shape | When to use |
| Snapshot | Handing a finished page to someone. Renders instantly and offline; no token needed to view it. Contains real data, so treat it as you would any data export. |
Live (--no-data) | Publishing anywhere others can reach. Ships no data at all — the viewer pastes their own token and the page fetches for them. |
assets/example-calendar.html is a prebuilt live page. Open it, paste a token,
press Load.
The token is used only at build time and never written into either output.
build.py refuses to write a file containing anything shaped like a key or a
proxystream ticket.
How the live page fetches
api.blueskyapi.com sends Access-Control-Allow-Origin: *, so browser fetch
works from anywhere including file://. The page runs a pool of 10 concurrent
requests, one per symbol, and reports progress as it goes. About 500 symbols
takes roughly a minute.
No LLM sits in the fetch loop. Every date on screen is API output verbatim.
Changing what it looks like
Styles live in assets/_shared.css and are inlined at build time. The colour
system is deliberate and worth preserving:
- Chrome stays neutral so the only colour on the page is the data.
- Pre-market is teal, post-market is amber — first light and the close. Semantic, not decorative. Don't repurpose these two hues for anything else.
- No session is grey, and it is the largest group. Design for that, don't treat it as an edge case.
Weekends are omitted from the grid entirely. Earnings are not released on a Saturday, and rendering two permanently empty columns misstates how dense a week is. Leading and trailing empty weeks are trimmed for the same reason.
Adjusting the symbol list
assets/symbols.txt, one per line. It ships as an S&P 500 list. There is no API
route that returns universe membership for an unscoped token, so it is a file
rather than a lookup — which also means it needs occasional review. See
references/dataset.md for the drift currently in it.
To build for a different set, pass --symbols my-list.txt, or paste symbols
directly into the live page's textarea.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.