Agent skill · software engineering · jeremylongshore
abridge-sdk-patterns
Implement a narrow customer-owned adapter around an approved Abridge tenant interface without claiming a public SDK. Use when coding against vendor-issued integration specifications. Trigger with \"build the Abridge adapter\".
Why this skill is useful
Adds a type-safe API client singleton and HIPAA-compliant error handling scripts that are specific to Abridge's healthcare integration.
What it needs
Requires axios, typescript installed locally. Requires abridge account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Abridge Private-Contract Adapter Patterns Overview Keep vendor-specific transport behind a typed port whose schema, authentication, errors, timeouts, and retry rules are pinned to the private contract revision. Make unsupported behavior fail closed and keep clinical review outside the adapter. 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 sources describe product workflows, not a general public SDK package or stable REST surface. Partner-issued specifications may be implemented only for the authorized tenant and cannot be generalized without evidence. Clinical content, credentials, and tenant identifiers must not appear in logs or test fixtures. 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. Verify the contract owner, revision, environment, authentication protocol, schemas, delivery semantics, and support path. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-sdk-patterns