Update to Maven Bio

{
  "description": "Find historical or competitive precedents that inform an asset, company, or market question, and explain why each is a fair comparison. Use for precedent reasoning, for example 'what is the closest analog to this launch', 'what should we price off'. Use benchmark-assets for a direct side-by-side comparison of named assets instead.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 802
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 332
    }
  ],
  "name": "identify-analogs",
  "skill_md_contents": "---\nname: identify-analogs\ndescription: \"Find historical or competitive precedents that inform an asset, company, or market question, and explain why each is a fair comparison. Use for precedent reasoning, for example 'what is the closest analog to this launch', 'what should we price off'. Use benchmark-assets for a direct side-by-side comparison of named assets instead.\"\n---\n\n# Identify Analogs\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 primitive finds reference cases that help frame expectations without forcing a final output format.\n\n## Use When\n\n- a workflow needs comparable launches or programs\n- the user asks for historical analogs\n- you need precedent cases to anchor sizing, positioning, or forecast logic\n\n## Core Tools\n\n- `match_entity`\n- `search_entities`\n- `research_entity`\n- `fetch_related`\n- `search_documents`\n- `read_document`\n- `get_recent_events` (when the analogy turns on how a comparable asset's milestones actually unfolded)\n\nUse `match_entity` when you already know the specific entity you want to anchor analog selection around. Keep the raw entity name in `name` and put sponsor/company/disambiguating text in `context`. Use `search_entities` when you are discovering analog candidates by criteria.\n\n## Output Contract\n\nReturn a structured analog set with:\n\n- analog entity\n- why it is comparable\n- evidence-backed dimensions of similarity\n- differences or boundary conditions\n- evidence ratings and citations\n\n## Optional Primitives\n\n- `validate-target` (when analog selection depends on shared, genetically-validated targets)\n\n## Quality Bar\n\n- explain why each analog belongs in the set\n- avoid superficial similarity without mechanism or market logic\n- keep disanalogies visible\n- treat analog selection as an analytic judgment supported by evidence, not as a fact\n- timing-based analogies (LOE-driven generic entry, biosimilar windows, post-exclusivity uptake) require comparable regulatory milestones on both the anchor and each analog; source those milestones from FDA or SEC filings via `search_documents` plus `read_document` before drawing a timing inference, and drop the analogy rather than inferring a date neither filing supports\n"
}