Update to Maven Bio

{
  "description": "Return the recent event stream (FDA actions, trial readouts, press releases) for a named drug, company, trial, or indication, with structured evidence per event. Use for recency questions, for example 'what happened with X recently', 'any news on this program'. This is a building block the workflow skills compose.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 802
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 328
    }
  ],
  "name": "trace-events",
  "skill_md_contents": "---\nname: trace-events\ndescription: \"Return the recent event stream (FDA actions, trial readouts, press releases) for a named drug, company, trial, or indication, with structured evidence per event. Use for recency questions, for example 'what happened with X recently', 'any news on this program'. This is a building block the workflow skills compose.\"\n---\n\n# Trace Events\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 is for timeline-style intelligence and recent developments.\n\n## Use When\n\n- the user asks what happened recently\n- a workflow needs catalysts, recent news, or regulatory updates\n- you need a recent-event layer around an entity or indication\n\n## Core Tools\n\n- `get_recent_events`\n- `read_document`\n- `search_documents`\n\n## Output Contract\n\nReturn a structured event list with:\n\n- date\n- event type\n- summary\n- evidence rating\n- citations\n- unresolved questions\n\n## Quality Bar\n\n- use event feeds for discovery\n- strengthen material claims with document reads when needed\n- keep chronology explicit\n- preserve ambiguity if event interpretation is uncertain\n"
}