Agent skill · software engineering · jeremylongshore
abridge-local-dev-loop
Build a local synthetic rehearsal for customer-owned Abridge workflow adapters and failure states. Use when developing integration code without access to patient data or a documented public Abridge sandbox. Trigger with \"create an Abridge dev loop\".
Why this skill is useful
Adds executable scripts for setting up a local FHIR server and synthetic data generation that are not commonly found in public documentation.
What it needs
Requires docker, 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 Synthetic Workflow Rehearsal Overview Model the approved interface control document locally with synthetic fixtures, deterministic state transitions, and zero vendor calls. Keep the harness useful even when tenant-specific schemas change by pinning each fixture to its authority revision. 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 public support materials describe the human workflow but do not promise a universal public developer sandbox. A local EHR simulator or mock adapter tests customer code only; it does not reproduce Abridge, Epic, or clinical behavior. Synthetic dialogue must avoid copied patient phrases and realistic identifiers. 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 customer-owned boundary, private contract revision, permitted fields, and expected state transitions. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-local-dev-loop