Agent skill · software engineering · jeremylongshore
abridge-ci-integration
Build a synthetic-data CI gate for customer-controlled Abridge integration code without calling undocumented vendor interfaces. Use when adding regression checks to an Abridge deployment repository. Trigger with \"test the Abridge integration\".
Why this skill is useful
Adds a complete CI/CD pipeline configuration with specific checks for FHIR validation and HIPAA compliance that the AI cannot generate on its own.
What it needs
Requires npm installed locally. Requires github 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 CI Gate Overview Turn the approved deployment contract into deterministic checks for configuration, consent-state handling, note-review handoffs, redaction, and rollback. The gate proves customer-owned behavior; it does not certify Abridge or an EHR tenant. 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 documents clinician recording, note review, Linked Evidence, and Epic handoff as user workflows. The cited public materials do not define a general Abridge REST sandbox, webhook schema, or public SDK contract. Use synthetic encounters and identifiers in CI; never upload patient audio, transcripts, notes, or production tokens. 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. Inventory the customer-owned adapters, configuration schema, feature flags, and rollback controls with Read, Glob, and Grep. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-ci-integration