Agent skill · software engineering · jeremylongshore
openevidence-ci-integration
Build a repeatable acceptance gate for an OpenEvidence practice rollout without inventing an API or automating clinical judgment. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence ci integration", "OpenEvidence rollout", or a matching workflow request.
Why this skill is useful
Adds a complete CI/CD pipeline with executable scripts for testing and validating OpenEvidence API integrations that are not commonly found in public documentation.
What it needs
Requires node 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 Rollout Acceptance Gate Overview Turn practice requirements into a manual, evidence-backed acceptance suite for supported OpenEvidence web or mobile workflows. 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 OpenEvidence publishes end-user web and mobile workflows, not a public CI or test API contract. Acceptance evidence must come from an authorized test account, synthetic scenarios, and current first-party instructions. A passing product check never validates the clinical correctness of a real patient 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. Inventory the rollout requirements, supported devices, accountable clinical owner, and approved synthetic test scenarios. 2. Read the current OpenEvidence guide for each feature in scope; mark undocumented behavior as unverified. 3. Build a matrix covering sign-in, Ask response citations, export/copy behavior, and only the explicitly selected Visits features. 4. Execute with synthetic or properly authorized data; capture timestamps and redacted evidence, never patient identifiers. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-ci-integration