Agent skill · writing content · jeremylongshore
openevidence-core-workflow-b
Audit an OpenEvidence answer’s EvidenceGrade, citations, and applicability before it informs clinical work. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence core workflow b", "OpenEvidence citations", or a matching workflow request.
Why this skill is useful
Adds executable scripts for searching evidence, building citation collections, grading evidence, and generating reports that extend the AI's capabilities in healthcare research synthesis.
What it needs
Requires npm installed locally. 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 EvidenceGrade and Citation Review Overview Treat the displayed grade as a navigation aid, then perform a source-level review of every material claim. 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 official user guide documents lettered EvidenceGrade output and links to its methodology. A grade summarizes evidence strength; it is not a patient-specific recommendation or correctness guarantee. Citation review must consider source type, date, population, outcome, and fit to the decision. 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. List each material claim that could change diagnosis, treatment, safety, documentation, or patient communication. 2. Capture the displayed EvidenceGrade and any caveats without treating the grade as the conclusion. 3. Open the supporting citations and map each claim to the exact source or mark it unsupported. 4. Check guideline authority, publication date, study population, intervention, comparator, outcomes, and limitations. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-core-workflow-b