Agent skill · writing content · jeremylongshore
openevidence-core-workflow-a
Structure and review an OpenEvidence clinical consult while preserving clinician accountability and evidence traceability. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence core workflow a", "OpenEvidence clinical-consult", or a matching workflow request.
Why this skill is useful
Adds executable scripts for querying clinical evidence, checking drug interactions, and retrieving guidelines that are specific to the OpenEvidence platform.
What it needs
Requires openevidence account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OpenEvidence Clinical Consult Workflow Overview Convert a clinical uncertainty into a focused Ask workflow, then validate the evidence before using it in care. Keep inputs minimal, separate observed facts from assumptions, and leave consequential decisions with the named accountable owner. Prerequisites A clearly bounded workflow, accountable clinical owner, and organizational policy Current first-party OpenEvidence documentation and applicable institution agreements Synthetic or properly authorized minimum-necessary data Tool Discipline Use Read, Glob, and Grep to inspect supplied policies, plans, and evidence. Use WebFetch only for current first-party OpenEvidence documentation. Use Write or Edit only when the user requests a named deliverable with an approved destination. Never expose credentials, PHI, recordings, or unrestricted environment output. Current Contract The platform is informational and educational and does not replace diagnosis or professional clinical judgment. The public guide describes Ask for evidence-based clinical questions with cited sources. Only enter patient context permitted by applicable policy, agreement, authorization, and consent. Authentication Use only the official OpenEvidence web/mobile sign-in or an institution-approved access path. Do not invent API keys, OAuth clients, SDK credentials, service accounts, or private endpoints. Never ask a user to reveal a password, session token, cookie, or recovery code. Instructions 1. Define the decision to support and the minimum context needed; remove direct identifiers unless approved and necessary. 2. Frame the question with population, intervention or exposure, comparator, outcomes, and relevant constraints. 3. Choose the documented Ask model or workflow appropriate to complexity; use Snow for a literature investigation when warranted. 4. Review EvidenceGrade when present, then open citations and inspect recency, study design, population, and guideline provenance. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-core-workflow-a--e878e7