Update to Maven Bio

{
  "description": "Return one structured, evidence-backed fact sheet for a single known drug, company, trial, mechanism, or target. This is a building block the workflow skills compose. Use it directly only when someone wants the raw fact pattern for one entity; for a full asset picture use asset-profile, and for a full company picture use company-portfolio.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 802
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 327
    }
  ],
  "name": "profile-entity",
  "skill_md_contents": "---\nname: profile-entity\ndescription: \"Return one structured, evidence-backed fact sheet for a single known drug, company, trial, mechanism, or target. This is a building block the workflow skills compose. Use it directly only when someone wants the raw fact pattern for one entity; for a full asset picture use asset-profile, and for a full company picture use company-portfolio.\"\n---\n\n# Profile Entity\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 turns one known entity into a structured fact pattern with explicit provenance.\n\n## Use When\n\n- the user wants depth on a specific named entity\n- a workflow needs entity-level facts before synthesis\n- you need mechanism, trial, event, document, or per-indication development detail tied to one entity\n\n## Core Tools\n\n- `research_entity`\n- `search_documents`\n- `read_document`\n- `get_recent_events`\n- `search_documents` with `source_types=[\"fda_filings\"]` (drug entities, when an approval, designation, or label snapshot matters)\n\n## Output Contract\n\nReturn structured findings such as:\n\n- entity summary\n- key facts\n- evidence-backed claims\n- important unknowns\n\nEach claim should include:\n\n- `claim`\n- `evidence_rating`\n- `citations`\n- optional `notes`\n\n## Quality Bar\n\n- use `research_entity` for discovery and structure\n- request `aspects=[\"indication_phases\"]` on `research_entity` when you want the asset's per-indication phase/status footprint\n- for company entities, request `aspects=[\"financings\"]` for rounds the company received and `aspects=[\"investments\"]` for rounds the company invested in (useful for VCs, corporate venture arms, and strategic investors). Both are opt-in\n- the default company response includes a lightweight `related_previews.financings` and `related_previews.investments` teaser (count plus a few sample rounds). Treat these as prompts for whether to opt into the full per-round detail rather than as evidence in their own right\n- on every financing row, `value_status` disambiguates `total_value_usd`. `\"confirmed\"` means Maven has a USD value. `\"unconfirmed\"` means Maven's data does not have the amount, not that the round was undisclosed in the world. Verify externally if the value is critical\n- distinguish `aspects=[\"financials\"]` (public-market financial statements: revenue, EBITDA, market cap, cash) from `aspects=[\"financings\"]` (private/round-level capital activity). Both can apply to the same company; pair them when reasoning about runway or capital posture\n- treat `related_previews.documents` and `related_previews.events` as prompts for what to inspect next when you requested a narrower aspect\n- use `search_documents` and `read_document` when a claim needs evidence\n- for approved drugs, build the approval snapshot from primary filings via `search_documents(source_types=[\"fda_filings\"])` plus `read_document`, and cite the document and its date for any label-sourced claim; report exclusivity or LOE timing as a gap when no filing supports it\n- keep the raw entity name in the main tool field and move sponsor/company text into the optional context hint\n- do not treat entity metadata alone as direct evidence\n- if host web fetch is blocked, use `search_documents` and `read_document` instead of treating the block as the end of the research path\n- keep missing or weakly supported facts visible as gaps\n"
}