Agent skill · software engineering · jeremylongshore
openevidence-install-auth
Establish authorized OpenEvidence account access through official registration and institutional pathways. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence install auth", "OpenEvidence authentication", or a matching workflow request.
Why this skill is useful
Adds specific installation and authentication steps for the OpenEvidence SDK that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python 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 Account Verification and Access Overview Choose the supported user access path and verify it without packages, tokens, shared accounts, or private endpoints. 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 terms require account registration for full service access and make users responsible for account confidentiality. The product is intended for healthcare professionals and may verify registration information. No public OpenEvidence SDK package, API token, OAuth, or service-account contract was found. 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. Identify individual versus institution-managed access, professional role, approved email/device, and accountable access owner. 2. Read current registration, terms, privacy, security, and institution-specific access instructions. 3. Complete only the official sign-up, sign-in, or administrator-issued path; do not install similarly named packages. 4. Enable organization-required device and account protections and keep credentials in approved user-controlled storage. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-install-auth