Agent skill · software engineering · jeremylongshore
openevidence-upgrade-migration
Adopt a documented OpenEvidence feature or model change through inventory, pilot, review, training, and rollback. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence upgrade migration", "OpenEvidence change-management", or a matching workflow request.
Why this skill is useful
Adds specific migration scripts and domain knowledge for OpenEvidence API versioning and schema changes that the AI wouldn't reliably generate 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 Feature-Change Adoption Overview Prevent silent workflow drift when navigation, models, outputs, or product features change. 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 features and model choices can change; current first-party guidance is the baseline. Deep Consult-to-Snow is one documented replacement, but other changes require their own evidence. Saved prompts and procedures must be revalidated when model or output behavior changes. 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. Capture the change source, evidence date, affected users, workflows, data, templates, records, training, and controls. 2. Separate documented facts from assumptions and determine whether the change is mandatory, optional, or unavailable to the account. 3. Run synthetic before/after scenarios using a stable rubric for citations, applicability, uncertainty, format, and effort. 4. Review privacy, consent, security, clinical, operational, and records impacts. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-upgrade-migration