---
name: abridge-install-auth
description: "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\"."
argument-hint: "[environment] [identity-owner]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.5.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - abridge
  - access
  - identity
  - onboarding
model: inherit
effort: high
compatibility: Designed for Claude Code; live work requires an authorized Abridge tenant, approved test data, and health-system change authority
title: abridge-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/abridge-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/abridge-install-auth/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/abridge-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/abridge-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/abridge-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/abridge-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/abridge-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/abridge-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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. Identify contract owner, tenant administrator, identity owner, EHR owner, privacy and security contacts, and vendor implementation lead.
2. Inventory licensed products, environments, cohorts, roles, SSO requirements, support routes, and tenant-specific interfaces.
3. Use `Read`, `Glob`, and `Grep` to locate configuration templates and secret references without exposing secret values.
4. Verify least-privilege provisioning, joiner-mover-leaver handling, break-glass ownership, and audit evidence.
5. Use `WebFetch` only for current official Abridge public context; reconcile private setup steps with their document revision.
6. Use `Write` or `Edit` to create the readiness matrix and unresolved-dependency log.

## Approval Boundaries

Do not invent or probe Abridge endpoints, place vendor secrets in repository files, or authorize a user outside the health system's identity process.

## Output

Return environment and capability inventory, authority owners, role model, secret locations by reference, support route, evidence revisions, and readiness gaps. Separate verified facts, tenant-specific evidence, assumptions, and actions still awaiting approval.

## Error Handling

| Condition | Response |
|---|---|
| Credential source is informal | Reject it and request vendor-issued or identity-owner evidence. |
| Role scope is unclear | Provision nothing until least privilege is defined. |
| Environment cannot be distinguished | Hold all live actions. |

## Example

The example is a redacted operational receipt, not patient data or proof of vendor certification.

```text
tenant=contracted; environments=2; sso-owner=iam; ehr-owner=clinical-apps; secrets=references-only; unresolved=vendor-interface-revision
```

## Resources

- [Official documentation map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/abridge-install-auth/references/official-docs.md) — dated public evidence and the limits of what those sources establish.

Read the source map before changing a workflow. Recheck tenant-specific implementation evidence for every interface or capability that public documentation does not define.

## Next Steps

Revalidate the evidence date and tenant-specific authority before repeating this workflow in another environment, cohort, care setting, or integration mode.
