Update to Bigdata.com

{
  "name": "bigdata-company-brief",
  "description": "Generate a company brief — a cited 30-day summary of what happened at a public company and why it matters — using Bigdata.com data (news, filings, transcripts, tearsheet financials). Findings are categorized into financial results, product and tech launches, M&A and partnerships, regulatory and legal, management changes, and other material events, each with date, facts, and a bullish/bearish/neutral investment implication tied to a value driver, plus competitive context and a ranked top 2-3. Triggers: \"company brief for X\", \"what's happening with X\", \"catch me up on X\", \"recent developments at X\", \"what's the news on X\", \"summary of the last month for X\", \"any updates on X\".",
  "included_files": [
    {
      "relative_path": "README.md",
      "size_in_bytes": 2063
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 331
    },
    {
      "relative_path": "assets/bigdata-icon-black.svg",
      "size_in_bytes": 3278
    },
    {
      "relative_path": "assets/report-template.md",
      "size_in_bytes": 2818
    },
    {
      "relative_path": "references/porter-five-forces.md",
      "size_in_bytes": 9337
    }
  ],
  "skill_md_contents": "---\nname: bigdata-company-brief\ndescription: >\n  Generate a company brief — a cited 30-day summary of what happened at a public company and\n  why it matters — using Bigdata.com data (news, filings, transcripts, tearsheet financials).\n  Findings are categorized into financial results, product and tech launches, M&A and\n  partnerships, regulatory and legal, management changes, and other material events, each with\n  date, facts, and a bullish/bearish/neutral investment implication tied to a value driver, plus\n  competitive context and a ranked top 2-3. Triggers: \"company brief for X\", \"what's happening\n  with X\", \"catch me up on X\", \"recent developments at X\", \"what's the news on X\",\n  \"summary of the last month for X\", \"any updates on X\".\n---\n\n# Bigdata Company Brief\n\nRetrospective 30-day summary of material developments at a public company, with a \"so what\" on each. Use Bigdata.com plugin tools for every fact.\n\n**Use this skill when** the user wants to catch up on what has already happened. Not this skill when:\n\n| Request | Use instead |\n|---------|-------------|\n| Analysis ahead of an upcoming earnings call | Earnings preview |\n| Breakdown of results just reported | Earnings digest / earnings reaction |\n| \"What is it worth\" | Valuation snapshot |\n| Structured risk mapping with likelihood/impact | Risk assessment |\n| Full thesis, DCF, or variant perception | Investment memo |\n\n## Data foundation (plugin tools)\n\n| Tool | Purpose | Prerequisite |\n|------|---------|--------------|\n| `find_securities` | Resolve company name → RavenPack `entity_id` | None |\n| `bigdata_company_tearsheet` | Profile, sector/industry, financial position, recent performance | `find_securities` |\n| `bigdata_search` | News, filings, transcripts, legal and regulatory coverage | None |\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 — Business context\n\nCall `bigdata_company_tearsheet` with the `entity_id` for the company profile (sector, industry, description), financial position, and recent performance metrics. This context is what lets you judge whether a news item is material — read it before searching.\n\n### Step 3 — Competitive context (one pass)\n\nRun `bigdata_search` at least once on industry structure and positioning:\n\n- \"[Company] competitive landscape market share\"\n- \"[Company] vs competitors [Industry]\"\n\nA full five-forces write-up is not needed. **2–4 sentences** on concentration, pricing power, and disruption risk materially lift the brief. Mental model: [references/porter-five-forces.md](./references/porter-five-forces.md).\n\n### Step 4 — Search recent news (last 30 days)\n\nUse `bigdata_search` with natural-language queries that include the company name and a temporal reference. Run **5–10 searches** for coverage, then compress.\n\n- \"[Company] news last 30 days\"\n- \"[Company] recent developments\"\n- \"[Company] earnings announcement\"\n- \"[Company] product launches partnerships\"\n- \"[Company] regulatory legal updates\"\n- \"[Company] lawsuit litigation court ruling investigation settlement last 30 days\"\n\nCover all of: financial developments, product/technology announcements, partnerships and M&A, regulatory and legal matters, management changes. The explicit legal/litigation query is there so material non-operational items don't get buried under earnings headlines.\n\nIf the month was quiet, ask:\n\n> \"I haven't found any significant developments for [Company] in the last 30 days. Would you like me to extend the search period or focus on specific topics?\"\n\n### Step 5 — Categorize, and mark what is primary\n\nSort every finding into the six output categories: **Financial Results**, **Product/Tech Launches**, **M&A and Partnerships**, **Regulatory/Legal Updates**, **Management Changes**, **Other Material Events**.\n\nWhile sorting, tag each item **primary** (material to value or the narrative) or **secondary**. Do not equal-weight the categories in the prose — quantity of headlines is not materiality. If a category is empty, write \"No significant developments in this period\" rather than padding it.\n\n### Step 6 — Investment implication (\"so what\")\n\nFor each **material** event, give:\n\n- **Date** — when it happened or was announced\n- **Facts** — objective summary of what happened\n- **Investment implication** — Bullish / Bearish / Neutral, tied to a value driver\n\nAvoid generic labels. Replace \"bullish for the stock\" with the lever: \"could support ~+$Nm revenue run-rate\", \"+Ybps margin\", \"de-risks [issue]\", \"lifts regulatory overhang on segment Z\". If it isn't quantifiable, state the **specific mechanism** instead of a direction.\n\n### Step 7 — Rank and synthesize\n\nRank the top **2–3** developments for the period and lead the executive summary with them. The overall assessment states the **net tilt and why**, not a recap of every bullet.\n\n## Output\n\nFollow [assets/report-template.md](./assets/report-template.md) exactly — section order, sources, and footer.\n\n- Add inline citations as superscript-style numbers `[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 at the end if useful.\n\n## Quality bar\n\nPass the PM test before delivering: **What's different?** **What matters (2–3 items)?** **What should I do about it?** (net assessment, key risk, next catalyst — no position sizing). Would it survive a short, skeptical morning meeting without reading as a news dump?\n\nNon-negotiables in every brief:\n\n- Competitive context present, not skipped\n- Every material event carries date, facts, and a **mechanism-level** implication\n- Top 2–3 developments ranked and surfaced in the executive summary\n- Legal/regulatory search actually run, with material items shown\n- Empty categories marked as such rather than padded\n- Facts separated from analysis and implications\n"
}