Agent skill · software engineering · jeremylongshore
openevidence-hello-world
Complete a smallest-safe OpenEvidence onboarding proof through the supported product, with no patient data or invented API key. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence hello world", "OpenEvidence onboarding", or a matching workflow request.
Why this skill is useful
Provides specific API usage examples and error handling for OpenEvidence that the AI wouldn't reliably generate on its own.
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 Verified-User Onboarding Overview Verify account access and the Ask evidence-review loop using a synthetic clinical question. 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 Full service access requires account registration and may include professional verification. The supported onboarding surface is the website or mobile application; no public API-key flow is documented. The first proof must avoid patient data and clinical action. 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. Confirm the intended user, approved device, organizational policy, and whether an institutional account path applies. 2. Register or sign in through the official product; never request or fabricate an API key. 3. Submit a synthetic, non-urgent clinical question containing no identifiable patient facts. 4. Confirm the answer displays sources and, when present, EvidenceGrade; open at least one citation. 5. Record surface, timestamp, result, and any access limitation without copying account secrets. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-hello-world