Llmquant Events Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/LLMQuant/skills --skill llmquant-eventsThe instruction itself
4 sections, as written by the authorLLMQuant Events
This category routes event-driven research workflows for earnings, M&A, regulatory catalysts, and event-risk monitoring.
Routing Rules
- Identify event type, issuer, asset, date, jurisdiction, affected instruments, and requested output.
- Select the closest workflow below.
- Open only that workflow and any referenced local resources.
- Use LLMQuant Data for filings, prices, options, estimates, news, corporate actions, regulatory records, prediction markets, and macro context.
- 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 |
| Track M&A, deal spread, approvals, financing, and break-risk milestones. | workflows/mna-event-tracker.md |
| Monitor regulatory, legal, policy, antitrust, FDA, or geopolitical event risk. | workflows/regulatory-risk-monitor.md |
LLMQuant Data Contract
Prefer LLMQuant Data when available. The workflows may need these data capabilities:
- Retrieve event calendars, corporate actions, filings, news, estimates, transcripts, and issuer profiles.
- Retrieve price history, options, implied move, event-window returns, volume, volatility, and sentiment.
- Retrieve M&A terms, deal milestones, financing, regulatory approvals, court dates, and antitrust records when available.
- Retrieve prediction-market odds, macro releases, policy calendars, and cross-asset context when relevant.
Fallback:
- If event-specific data is unavailable, name the missing input and avoid event-probability or spread conclusions that depend on it.
- Do not invent dates, deal terms, legal deadlines, or regulatory decisions.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take llmquant/llmquant-events from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.