Update to Supplement Intelligence

{
  "description": "Research reviewed supplement ingredient evidence or current tracked product formulations using Supplement Intelligence.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 537
    }
  ],
  "name": "supplement-evidence-research",
  "skill_md_contents": "---\nname: supplement-evidence-research\ndescription: Research reviewed supplement ingredient evidence or current tracked product formulations using Supplement Intelligence.\n---\n\nUse this skill when the user asks about a supplement ingredient covered by Supplement Intelligence, asks what a tracked product currently contains, asks about the evidence or safety context for a reviewed ingredient, or wants to browse the reviewed ingredient library.\n\n## Tool selection\n\n1. If the user names a reviewed ingredient or asks what evidence supports an ingredient, call `get_ingredient_evidence`.\n2. If the user names a tracked product or asks what a product contains, call `get_product_formulation`.\n3. If the user uses an ambiguous name, partial name, or you are not sure whether the request refers to an ingredient or product, call `search_supplement_intelligence` first.\n4. If the user asks what topics are available or wants to browse the evidence library, call `list_reviewed_ingredients`.\n\n## Evidence interpretation\n\nAlways distinguish these three layers:\n\n- **Formulation fact:** what the current tracked manufacturer source lists.\n- **Ingredient-level evidence:** what research on an ingredient or preparation supports.\n- **Finished-product efficacy:** whether the exact product formulation and dose have direct supporting evidence.\n\nDo not infer finished-product efficacy merely because a product contains an ingredient with supportive evidence.\n\nWhen the tool reports a formulation, dose, preparation, population, duration, or outcome mismatch, preserve that limitation in the answer.\n\nWhen evidence is mixed, preliminary, heterogeneous, or inconclusive, say so plainly rather than converting it into a positive or negative recommendation.\n\n## Review-level evidence\n\nWhen `review_evidence` is returned:\n- Use it to explain what higher-level human evidence actually studied.\n- Preserve the population/scope, finding, and limitations together.\n- Do not convert a statistically significant pooled result into a blanket recommendation.\n- Do not infer an exact dose or preparation from a review summary unless that detail is explicitly present.\n- Prefer the ingredient's overall evidence posture when individual reviews disagree.\n- Keep review-level ingredient evidence separate from finished-product efficacy.\n\n## Safety and medical boundaries\n\n- Do not pass sensitive personal health details, diagnoses, medication lists, medical-record text, contact information, or other personal data into search queries. Extract only the ingredient or product term needed for the tool call.\n- Present safety information and source context when relevant.\n- Do not diagnose a user.\n- Do not prescribe treatment.\n- Do not provide a personalized supplement dosage based only on these tools.\n- Do not tell a user that a supplement is appropriate for their personal medical condition.\n- For individualized medical decisions, direct the user to a qualified healthcare professional.\n\n## Freshness and versioning\n\nWhen a tool returns `last_reviewed_at`, `catalog_checked_at`, `formulation_checked_at`, `data_version`, or `source_count`, use those fields directly when freshness matters. Do not infer a newer review date from the current conversation date.\n\n## Sources\n\nWhen the ingredient tool returns source URLs or PMIDs, preserve the connection between the factual claim and the source.\nDo not invent citations or claim that a source studied a finished product unless the tool explicitly says the evidence is direct.\n\n## Out-of-scope requests\n\nDo not invoke this skill for unrelated health topics, prescription-drug questions with no relevant supplement evidence, general shopping requests, weather, finance, politics, or other topics outside the Supplement Intelligence database.\n"
}