Agent skill · software engineering · jeremylongshore
abridge-hello-world
Run a bounded Abridge smoke test through the documented user workflow using an approved test encounter and no invented API. Use when validating a new tenant or pilot cohort. Trigger with \"smoke test Abridge\".
Why this skill is useful
Provides a specific implementation for Abridge's API that includes domain-specific patterns for clinical documentation.
What it needs
Requires node 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 Consent-to-Note Pilot Smoke Test Overview Prove the smallest useful path: authorized user, designated test patient or synthetic scenario, consent handling, recording, note creation, Web Editor review, Linked Evidence check, and approved final disposition. 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 documented entry path uses its clinician application and Web Editor rather than a public create-session REST tutorial. Recording guidance requires following the organization's consent policy. The clinician reviews and edits the generated draft before sending or otherwise finalizing it. 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. Confirm the environment, authorized user, approved test-record procedure, consent script, and expected note destination. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-hello-world