Agent skill · software engineering · jeremylongshore
openevidence-migration-deep-dive
Migrate saved Deep Consult practices to the current Snow model workflow while revalidating output and governance. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence migration deep dive", "OpenEvidence migration", or a matching workflow request.
Why this skill is useful
Provides specific migration strategies and checklists for OpenEvidence that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OpenEvidence Deep Consult to Snow Migration Overview Translate legacy Deep Consult use cases into Snow, which the official guide identifies as its replacement. 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 current guide says Deep Consult has been replaced by OpenEvidence Snow in the model selector. Legacy Deep Consult examples remain representative, but do not establish current performance, quota, or timing. Migration must revalidate prompts, structure, citations, review, data handling, and user training. 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 legacy Deep Consult prompts, reports, user groups, downstream decisions, and sensitive-data handling. 2. Classify each workflow as retire, move to ordinary Ask, or pilot in Snow based on complexity and value. 3. Read the current Models and Deep Consult guidance; remove obsolete navigation and invented quota assumptions. 4. Run synthetic paired evaluations and compare coverage, citation traceability, uncertainty, format, and reviewer effort. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-migration-deep-dive