Update to Bigdata.com

{
  "description": "Map the dated events that could move a public company over the next few quarters, using Bigdata.com data (events calendar, filings, news, tearsheet). Covers scheduled catalysts — earnings, investor days, index reviews, lock-up and patent expiries, regulatory decision dates — and foreseeable unscheduled ones — litigation milestones, product cycles, contract renewals, refinancings. Each catalyst carries a date or window, likely direction, magnitude, confidence, and what to watch, ranked by expected impact rather than by date alone. Triggers: \"catalyst monitor for X\", \"what's coming up for X\", \"upcoming catalysts for X\", \"what could move X\", \"key dates for X\", \"event calendar for X\", \"what should I watch on X\".\n",
  "included_files": [
    {
      "relative_path": "README.md",
      "size_in_bytes": 1483
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 330
    },
    {
      "relative_path": "assets/bigdata-icon-black.svg",
      "size_in_bytes": 3278
    },
    {
      "relative_path": "assets/report-template.md",
      "size_in_bytes": 3621
    },
    {
      "relative_path": "references/epic-framework.md",
      "size_in_bytes": 7472
    }
  ],
  "name": "bigdata-catalyst-monitor",
  "skill_md_contents": "---\nname: bigdata-catalyst-monitor\ndescription: >\n  Map the dated events that could move a public company over the next few quarters, using\n  Bigdata.com data (events calendar, filings, news, tearsheet). Covers scheduled catalysts —\n  earnings, investor days, index reviews, lock-up and patent expiries, regulatory decision\n  dates — and foreseeable unscheduled ones — litigation milestones, product cycles, contract\n  renewals, refinancings. Each catalyst carries a date or window, likely direction, magnitude,\n  confidence, and what to watch, ranked by expected impact rather than by date alone.\n  Triggers: \"catalyst monitor for X\", \"what's coming up for X\", \"upcoming catalysts for X\",\n  \"what could move X\", \"key dates for X\", \"event calendar for X\", \"what should I watch on X\".\n---\n\n# Bigdata Catalyst Monitor\n\nForward calendar of what could move the name, ranked by impact. Use Bigdata.com plugin tools for every fact.\n\n**Use this skill when** the question is \"what's coming\". Not this skill when:\n\n| Request | Use instead |\n|---------|-------------|\n| What already happened over the past month | Company brief |\n| Deep analysis of the next earnings print | Earnings preview |\n| Probability-weighted outcomes and values | Scenario analysis |\n| Risks rated by likelihood and impact | Risk assessment |\n\n**Catalyst vs risk:** a catalyst is a **dated or datable event** that resolves something. A standing risk with no resolution date belongs in a risk assessment.\n\n## Data foundation (plugin tools)\n\n| Tool | Purpose | Prerequisite |\n|------|---------|--------------|\n| `find_securities` | Resolve company name → RavenPack `entity_id` | None |\n| `bigdata_events_calendar` | Scheduled earnings and conferences | `find_securities` |\n| `bigdata_company_tearsheet` | Baseline financials, estimates, what the price embeds | `find_securities` |\n| `bigdata_search` | Regulatory dates, litigation milestones, product cycles, filings | None |\n\n**Required on every call:** pass `plugin_slug: \"bigdata-catalyst-monitor\"` in the request parameters of *every* Bigdata.com plugin tool call made while running this skill. The value is always the skill name, `bigdata-catalyst-monitor`, regardless of the company or query.\n\n**Exceptions:** the `search` and `fetch` tools do not accept `plugin_slug` — omit it there.\n\nIf the company name is ambiguous after `find_securities`, ask:\n\n> \"I found multiple companies named [X]. Did you mean [Company A] in [Industry] or [Company B] in [Industry]?\"\n\n## Workflow\n\n### Step 1 — Identify the company\n\nCall `find_securities` with the company name to get the `entity_id`.\n\n### Step 2 — Scheduled events\n\nCall `bigdata_events_calendar` for earnings dates and conferences over the next 2–4 quarters. Note the fiscal calendar so quarter-ends and guidance updates land correctly.\n\n### Step 3 — Baseline: what is already priced\n\nCall `bigdata_company_tearsheet`. A catalyst only matters relative to expectations — capture consensus estimates, current multiples, and sentiment so each catalyst can be framed against what the market already assumes.\n\n### Step 4 — Search for datable events\n\nRun **6–8 targeted searches**:\n\n- \"[Company] upcoming product launch roadmap timeline\"\n- \"[Company] regulatory decision approval date FDA / FTC / EU\"\n- \"[Company] lawsuit trial date court ruling expected\"\n- \"[Company] investor day capital markets day guidance update\"\n- \"[Company] contract renewal expiry major customer\"\n- \"[Company] debt maturity refinancing schedule\"\n- \"[Company] patent expiry exclusivity loss\"\n- \"[Company] index inclusion review lock-up expiry\"\n\nInclude the industry-specific ones that apply — clinical readouts, license renewals, rate cases, spectrum auctions, model launches.\n\n### Step 5 — Rate each catalyst\n\nFor every catalyst record:\n\n- **Date or window** — exact where known, quarter where not; mark undated but expected items as such\n- **Type** — scheduled or foreseeable\n- **Likely direction** — positive / negative / two-sided\n- **Magnitude** — high / medium / low, tied to a value driver where possible (\"~$Nm revenue\", \"~Xbps margin\", \"removes overhang on segment Y\")\n- **Confidence** — how sure the date and the outcome are; these are different, and both matter\n- **What to watch** — the specific signal that tells you which way it resolved\n\n### Step 6 — Rank and sequence\n\nRank by **expected impact**, not chronology — a large two-sided event in nine months usually matters more than a routine print next week. Then give the chronological calendar separately, so the reader gets both views.\n\nClose with the **2–3 catalysts that dominate** the next few quarters and what each would change.\n\n## Output\n\nFollow [assets/report-template.md](./assets/report-template.md) exactly — section order, tables, sources, and footer.\n\n- Add inline citations `[1]`, `[2]` immediately after claims, hyperlinked to the document URL.\n- Every deliverable ends with the **Powered by Bigdata.com** line and the **Disclaimer**, verbatim.\n- Default format is Markdown; offer a Word (.docx) or presentation version if useful.\n\n## Quality bar\n\nNon-negotiables:\n\n- Every catalyst carries a **date or window** — undated speculation is not a catalyst\n- Direction, magnitude, and confidence given separately; date confidence distinguished from outcome confidence\n- Magnitude tied to a value driver, not just labelled \"high\"\n- Ranked by impact **and** listed chronologically\n- Standing risks with no resolution date excluded — they belong in a risk assessment\n- Facts separated from analysis and implications\n"
}