Agent skill · software engineering · jeremylongshore
abridge-deploy-integration
Plan and control a staged Abridge rollout across clinical cohorts and EHR workflows without pretending to deploy vendor infrastructure. Use when preparing an Abridge pilot or expansion. Trigger with \"plan the Abridge rollout\".
Why this skill is useful
Adds a comprehensive deployment script for HIPAA-compliant cloud infrastructure that includes specific commands and configurations not commonly found in public documentation.
What it needs
Requires docker, gcloud installed locally. Requires aws, azure, gcp account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Abridge Staged Enterprise Rollout Overview Coordinate readiness, training, tenant configuration, EHR change control, support coverage, measurement, and rollback for a bounded cohort. Customer operators configure their environment and workflow; Abridge operates its platform. 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 integrated workflows across outpatient, emergency, and inpatient settings, with features varying by setting and rollout phase. Published rollout examples emphasize pilots, clinician demand, peer support, and phased expansion. Public product material does not authorize customers to self-deploy Abridge backend services or generic containers. 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. Name the executive, clinical, privacy, security, EHR, training, support, and vendor owners. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-deploy-integration