Catalyst Calendar
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is a coherent trading-event calendar, with disclosed local storage and scheduled-scan ideas but no evidence of credentials, hidden code, exfiltration, or direct trading actions.
This appears reasonable for an informational catalyst calendar. Before installing or using it, decide whether you want scheduled scans, keep the calendar file scoped to the documented workspace path, verify event sources, and avoid letting downstream trading tools act on new entries without review.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the user configures these schedules, the skill may periodically gather event information, update the local calendar, and produce alerts without a fresh one-off prompt each time.
The skill documents recurring scheduled activity. This is disclosed and aligned with a calendar-alert purpose, and no code or installer is provided to create the cron job automatically.
- **Weekly scan** (Monday 07:00 UTC): scrape upcoming events, update calendar - **Daily check** (07:00 UTC): flag events where pre-position window opens today
Enable any cron or scheduled automation only intentionally, keep it limited to the documented calendar file, and review automatic updates before acting on them.
Incorrect or manipulated event data could influence future market-calendar reviews or trading-related reasoning.
The skill stores externally gathered event information in a persistent local JSON file for later use. That is central to the purpose, but unverified scraped content could become trusted context in future analysis.
Search for upcoming crypto and macro events this week. Update catalyst-calendar.json with any new high-impact events in the next 30 days.
Prefer trusted primary sources, keep source URLs with each entry, and treat stored event notes as data to verify rather than instructions to follow.
A mistaken catalyst entry could affect alerts, journal context, or backtest assumptions across related skills.
The calendar is intended to provide context to other trading-pipeline skills, so bad calendar entries could propagate into downstream analysis. This is disclosed and purpose-aligned.
- Outputs feed `skill-crypto-threshold-watcher` (set tighter thresholds near high-impact events) - Logged to `skill-trading-journal` as context for trade decisions - Informs `backtest-expert` on regime conditions
Keep a human review step before changing trading thresholds or making trade decisions based on calendar-derived context.