Agent skill · marketing growth · jeremylongshore
openevidence-prod-checklist
Gate an OpenEvidence clinical workflow for go-live across access, privacy, safety, training, support, and rollback. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence prod checklist", "OpenEvidence go-live", or a matching workflow request.
Why this skill is useful
Adds a comprehensive production checklist for OpenEvidence that ensures HIPAA compliance and security best practices, which the AI cannot generate reliably on its own.
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 Go-Live Checklist Overview Produce a binary, owner-signed readiness decision for one clearly bounded workflow. 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 Go-live approval belongs to the accountable institution, not this skill or the product output. Current first-party terms, privacy, security, feature guidance, and institution agreements all matter. A successful technical test does not waive clinical review or data obligations. 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. Freeze workflow scope, users, surfaces, data classes, dependencies, success measures, and exclusions. 2. Verify account/access lifecycle, agreements, PHI boundary, consent, retention, approved exports, and security review. 3. Complete synthetic acceptance tests and clinician-led evidence/citation review across normal and failure cases. 4. Verify training, support contacts, incident response, downtime alternative, and rollback authority. 5. Record unresolved items as blockers or explicitly accepted risks with named decision owners. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-prod-checklist