Agent skill · software engineering · jeremylongshore
openevidence-multi-env-setup
Verify a governed OpenEvidence workflow across supported web and mobile surfaces without fictitious dev or staging hosts. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence multi env setup", "OpenEvidence web", or a matching workflow request.
Why this skill is useful
Adds executable scripts and environment validation logic for HIPAA-compliant setup of OpenEvidence across multiple environments.
What it needs
Requires jq 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 Web and Mobile Workflow Parity Overview Define which surface supports each step and test handoff, device, consent, and export behavior. 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 official guide documents web and mobile experiences for Ask and Visits workflows. No public dev or staging domains are documented; environment separation belongs to the institution’s test-data and rollout process. Browser-specific capabilities, such as some recording inputs, must be checked against current guidance. 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. Map the workflow steps, user role, device, browser/app, data class, and expected handoffs. 2. Read the current feature page for web/mobile differences and supported-browser notes. 3. Test with synthetic data on each authorized surface; record unavailable or divergent behavior. 4. Verify that copied notes, citations, recordings, and notifications stay within approved systems. 5. Define the supported surface, fallback, training note, and re-test trigger for each step. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-multi-env-setup--480989