llmquant-events
Router skill for LLMQuant event workflows. Use when the user needs earnings event briefs, M&A tracking, regulatory risk, catalysts, event calendars, or cross-asset event impact.
npx skills add LLMQuant/skills --skill llmquant-events --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# LLMQuant Events This category routes event-driven research workflows for earnings, M&A, regulatory catalysts, and event-risk monitoring. ## Routing Rules 1. Identify event type, issuer, asset, date, jurisdiction, affected instruments, and requested output. 2. Select the closest workflow below. 3. Open only that workflow and any referenced local resources. 4. Use LLMQuant Data for filings, prices, options, estimates, news, corporate actions, regulatory records, prediction markets, and macro context. 5. Report event dates, filing dates, data timestamps, source periods, stale notices, and missing inputs. ## Workflow Index | User intent | Workflow | |---|---| | Build an earnings-event brief with setup, expectations, options, and risk cases. | [`workflows/earnings-event-brief.md`](workflows/earnings-event-brief.md) | | Track M&A, deal spread, approvals, financing, and break-risk milestones. | [`workflows/mna-event-tracker.md`](workflows/mna-event-tracker.md) | | Monitor regulatory, legal, policy, antitrust, FDA, or geopolitical event risk. | [`workflows/regulatory-risk-monitor.md`](workflows/regulatory-risk-monitor.md) | ## LLMQuant Data Contract Prefer LLMQuant Data when available. T
- Routing Rules
- Workflow Index
- LLMQuant Data Contract
What does the llmquant-events skill do?
Router skill for LLMQuant event workflows. Use when the user needs earnings event briefs, M&A tracking, regulatory risk, catalysts, event calendars, or cross-asset event impact.
How do I install it?
Run `npx skills add LLMQuant/skills --skill llmquant-events --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From LLMQuant/skills, a repository with 183 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.