Agent skill · software engineering · jeremylongshore
abridge-rate-limits
Analyze and control capacity, queueing, and backpressure for a tenant-specific Abridge integration without inventing public limits or headers. Use when handling concurrency or throttling requirements. Trigger with \"plan Abridge capacity\".
Why this skill is useful
Adds executable scripts for managing Abridge API rate limits and session throttling that are not publicly documented.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Abridge Capacity and Backpressure Contract Overview Derive limits from the signed tenant interface and observed approved responses, then protect clinical workflows with bounded queues, idempotency, retry budgets, and downtime procedures. Public product scale claims are not an API rate contract. Prerequisites The authorized Abridge environment, clinical owner, and health-system policy set Current tenant-specific implementation evidence for every private interface in scope Synthetic data or the organization's formally approved test-record procedure Tool Discipline Use Read, Glob, and Grep to inspect repository configuration, adapters, tests, policies, and existing evidence. Use WebFetch only for current official Abridge, HHS, or named EHR documentation. Use Write or Edit only after confirming scope, environment, owners, patient-data boundary, and approval state. These tools do not confer access to Abridge, an EHR, or a clinical record; return exact operator steps or an approval-gated handoff for live actions. Current Contract The cited public Abridge materials do not define universal API quotas, concurrency tiers, reset headers, or retry semantics. Any limit or retry behavior must be tied to a versioned private interface contract or directly observed tenant evidence. Retries must not duplicate chart updates, note handoffs, or other clinical actions. Authentication Use only the health system's provisioned Abridge application access, SSO, administrative role, or tenant-specific partner authentication documented for the approved environment. Do not infer public API credentials, reuse production secrets in tests, or expose tokens and session material. Verify identity owner, least privilege, environment binding, storage, rotation, and revocation before any authenticated action. Instructions 1. Freeze the interface, contract revision, workload units, peak model, delivery semantics, and clinical recovery objective. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-rate-limits