Agent skill · software engineering · jeremylongshore
abridge-core-workflow-a
Design and verify the clinician workflow from consent through recording, draft review, Linked Evidence, and final note disposition. Use when implementing or auditing an Abridge clinical documentation pathway. Trigger with \"map the Abridge note workflow\".
Why this skill is useful
Adds a complete encounter-to-note pipeline with executable code for audio capture and EHR integration that isn't available in public documentation.
What it needs
Requires axios, ws 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 Encounter-to-Reviewed-Note Workflow Overview Define a clinician-in-the-loop path that keeps consent, patient selection, capture quality, draft verification, edits, and finalization explicit. Treat generated content as a draft until the authorized clinician completes the health system's review process. 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 Abridge's recording guidance tells clinicians to follow organizational consent policy before recording. The Web Editor supports reviewing and editing generated notes, and Linked Evidence supports source verification. A generated note remains subject to clinician review and the health system's documentation policy. 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. Identify care setting, authorized user, patient-selection source, consent rule, note type, and final record destination. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-core-workflow-a