Agent skill · software engineering · jeremylongshore
openevidence-webhooks-events
Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence webhooks events", "OpenEvidence handoffs", or a matching workflow request.
Why this skill is useful
Provides specific webhook integration patterns and event handling for OpenEvidence that the AI wouldn't 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 Workflow Handoffs and No-Webhook Guard Overview Translate event-driven integration requests into supported manual or contract-confirmed handoffs. 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 No public OpenEvidence webhook endpoint, signing method, event catalog, or retry policy was found. Private network behavior is not a supported integration contract. Documented product features and institution agreements define allowable handoffs. 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. Define the business event, source feature, destination, latency need, data class, failure impact, and accountable owner. 2. Search current first-party and institution-specific documentation for an explicit webhook or integration contract. 3. If none exists, block endpoint creation, secret generation, signature code, and guessed event names. 4. Design the minimum approved manual handoff, product-native workflow, or vendor-confirmation request. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-webhooks-events