Agent skill · software engineering · jeremylongshore
openevidence-rate-limits
Triage OpenEvidence access, latency, or capacity symptoms without asserting undocumented quotas or retry contracts. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence rate limits", "OpenEvidence capacity", or a matching workflow request.
Why this skill is useful
Adds a complete rate limiter implementation and retry strategy for OpenEvidence's API that isn't available in public documentation.
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 Access and Capacity Triage Overview Distinguish local connectivity, account/feature access, service behavior, and clinical urgency using safe evidence. 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 numeric request limit or API retry contract was found for OpenEvidence. Browser/app symptoms must not be translated into invented HTTP limits. Urgent care needs must use an independent clinical fallback. 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. Record UTC time, surface, feature, user cohort, duration, impact, and whether patient care is time-sensitive. 2. Move urgent work to the approved clinical fallback before diagnosis. 3. Check local network/browser/device conditions and current first-party status/support information. 4. Reproduce once with synthetic content if safe; do not hammer the service or probe private endpoints. 5. Compare affected users/surfaces and capture a redacted support packet. 6. Report observed capacity symptoms, not a guessed quota, with workaround, owner, and escalation state. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-rate-limits