Update to Maven Bio

{
  "description": "Build a full intelligence package on one company: pipeline, recent events, capital position, and strategic posture. Use when someone names a company and wants depth, for example 'profile Vertex', 'what is going on at X', 'walk me through their pipeline'. Use profile-entity instead when only a single structured fact sheet is wanted.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 802
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 333
    },
    {
      "relative_path": "references/evidence-research.md",
      "size_in_bytes": 4449
    }
  ],
  "name": "company-portfolio",
  "skill_md_contents": "---\nname: company-portfolio\ndescription: \"Build a full intelligence package on one company: pipeline, recent events, capital position, and strategic posture. Use when someone names a company and wants depth, for example 'profile Vertex', 'what is going on at X', 'walk me through their pipeline'. Use profile-entity instead when only a single structured fact sheet is wanted.\"\n---\n\n# Company Portfolio\n\n## Using this skill\n\nUse the connected Maven Bio MCP server at `https://mcp.mavenbio.com/`. Follow the user's explicit scope, depth, and output preferences; the workflow and output structure below are defaults. Report coverage limits instead of silently narrowing an explicitly requested set.\n\nHyphenated primitive names refer to other skills in this Maven Bio bundle. Consult the relevant skill when composing its workflow. Use the available MCP tool schemas for arguments; pass document identifiers to `read_document` through `ids`, and include a claim-specific `query` when using `format=\"citations\"`.\n\nThis workflow produces company-level intelligence without assuming a report or table deliverable.\n\n## Primary Primitives\n\n- `profile-entity`\n- `enumerate-entities`\n- `trace-events`\n- `trace-financings`\n- `synthesize-evidence`\n\n## Optional Primitives\n\n- `identify-analogs`\n- `benchmark-assets`\n- `synthesize-evidence` (when LOE timing, exclusivity calendar, or label-extension opportunities shape the strategic posture and each date needs a source)\n\n## Output Contract\n\nReturn a company intelligence package that can include:\n\n- company overview\n- pipeline snapshot\n- recent events\n- capital posture (recent rounds, total raised in window, lead investors, financing trajectory, runway implication)\n- public-market financial caveats when applicable (market cap, cash position, revenue scale)\n- strategic themes\n- discussion topics or diligence gaps when relevant\n\n## Aggregation Shortcuts\n\nFor the capital-trajectory and pipeline-shape views of one company, prefer `aggregate_records` over manually aggregating `research_entity(..., aspects=[\"financings\"])` rounds:\n\n- Financing trajectory: `aggregate_records(entity_type=\"financing\", query=\"rounds for {company} by year with total value\")`\n- Pipeline shape: `aggregate_records(entity_type=\"drug\", query=\"active programs for {company} by phase and indication\")`\n\n## Workflow Rules\n\n- treat company/entity profiling as the baseline fact pattern, not the final synthesis\n- pair `aspects=[\"financials\"]` with `aspects=[\"financings\"]` on `research_entity` for the public and private capital pictures; for VCs, corporate venture arms, and strategic investors, also pull `aspects=[\"investments\"]`\n- treat the `related_previews.financings` and `related_previews.investments` teaser on the default company response as a routing prompt, not as evidence; opt into the full aspect when the funding picture matters to the analysis\n- on every financing row, separate the confirmed-value slice from the unconfirmed slice; never aggregate `total_value_usd: null` rounds into a \"total raised\" headline without footnoting\n- augment important company, pipeline, event, and round-level claims with `search_documents` and `read_document`; the structured row is metadata, not citable evidence\n- for portfolios with approved assets, surface upcoming patent expiries, biosimilar entry windows, and label-extension opportunities from primary filings via `search_documents(source_types=[\"fda_filings\", \"sec_filings\"])` and `read_document`; where no filing supports a date, record it as a gap rather than estimating it\n- if host web fetch is blocked, prefer Maven-indexed document retrieval over repeated blocked fetch attempts\n- For independent evidence workstreams, follow the [evidence research procedure](references/evidence-research.md) for each scoped pass, then reconcile the claims before synthesis. Run passes sequentially, or in parallel when the host supports it and the task authorizes it.\n\n## BD and Diligence Posture\n\nFor BD, corp dev, and acquisition-target diligence, the company portfolio should surface a runway-implication slice in addition to the pipeline picture:\n\n- the most recent round (date, type, value, lead investor) versus the company's burn signals from `aspects=[\"financials\"]`\n- the financing trajectory (accelerating, flat, or aging since last round)\n- investor concentration and lead-investor signal\n- the comp-set position relative to peers identified through `identify-analogs` or `enumerate-entities`\n\nA capital-thin or aging-Series-B+ recipient with active mid-stage trials is a candidate signal. A well-funded recipient with a recent strategic investor is a different posture. Make the difference visible rather than collapsing both into \"company overview.\"\n\nFor investment-team workflows oriented around capital momentum across a space rather than one company, route to `funding-landscape` instead of building one company portfolio at a time.\n"
}