Agent skill · software engineering · jeremylongshore
abridge-install-auth
Establish Abridge tenant access, identity ownership, and approved EHR integration prerequisites without fabricating public credentials or endpoints. Use when onboarding an Abridge implementation. Trigger with \"configure Abridge access\".
Why this skill is useful
Adds executable scripts for Abridge integration and authentication that are specific to healthcare EHR systems, which the AI wouldn't generate on its own.
What it needs
Requires npm, pip 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 Access and Integration Readiness Overview Build an authority map for contracted capabilities, user provisioning, SSO, administrative roles, EHR integration, support, and secrets. Treat vendor-issued implementation documents as tenant-scoped evidence, not reusable public API facts. 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 publicly describes enterprise SSO, governance, analytics, secure cloud handling, and EHR-integrated workflows. The cited public documentation does not publish a self-service API-key flow, universal partner hostname, or generic SMART-on-FHIR setup for Abridge customers. Identity, integration, and support details must come from the signed agreement and approved implementation workbook. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-install-auth