Update to Maven Bio

{
  "name": "asset-profile",
  "description": "Build a full intelligence packet on one named drug or asset: development status, trial evidence, competitive position, catalysts, and risks. Use when someone names a single asset and wants depth, for example 'tell me everything about X', 'profile this drug', 'is X differentiated'. 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": 332
    },
    {
      "relative_path": "references/evidence-research.md",
      "size_in_bytes": 4449
    }
  ],
  "skill_md_contents": "---\nname: asset-profile\ndescription: \"Build a full intelligence packet on one named drug or asset: development status, trial evidence, competitive position, catalysts, and risks. Use when someone names a single asset and wants depth, for example 'tell me everything about X', 'profile this drug', 'is X differentiated'. Use profile-entity instead when only a single structured fact sheet is wanted.\"\n---\n\n# Asset Profile\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 a structured profile for one asset without assuming a final memo or deck format.\n\n## Primary Primitives\n\n- `profile-entity`\n- `benchmark-assets`\n- `trace-events`\n- `synthesize-evidence`\n\n## Optional Primitives\n\n- `identify-analogs`\n- `size-market`\n- `synthesize-evidence` (when the asset is approved or near-approval and designation, label, or exclusivity claims need to be tied back to specific filings)\n- `validate-target` (when the asset's thesis depends on its target's genetic validation)\n\n## Output Contract\n\nReturn a structured asset intelligence package that can include:\n\n- asset overview\n- development status\n- supporting trial or document evidence\n- competitive framing\n- recent catalysts\n- key risks and unresolved questions\n\n## Workflow Rules\n\n- treat entity profiling as the baseline fact pattern, not the final synthesis\n- when calling `research_entity`, keep the raw asset name in `name` and put sponsor/company/disambiguating text in `context`\n- use document augmentation to strengthen trial, catalyst, forecast, and competitive claims\n- if host web fetch is blocked, prefer `search_documents` and `read_document` over repeated blocked fetch attempts\n- if a composite asset name fails to resolve, retry with the raw asset name and move sponsor/company details into the optional context hint\n- if the asset is approved in any region, include a regulatory timeline (designations, approval dates, label revisions) built from `search_documents` with `source_types=[\"fda_filings\"]` and `read_document`; cite the filing and its date for each milestone, and state exclusivity or LOE timing as a gap when no filing supports it\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"
}