Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/abridge-deploy-integration

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/abridge-deploy-integration

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈64 tokens for metadata: the name and description. ≈1k when used: this file. ≈421 more on demand in 1 file.

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈255 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Freeze cohort eligibility, care setting, licensed capabilities, consent policy, training, success measures, and stop criteria.
  3. Use Read, Glob, and Grep to inspect the local rollout plan and configuration artifacts without patient data.
  4. Rehearse patient selection, recording, note review, EHR handoff, downtime, support, and opt-out paths with approved test records.
  5. Use WebFetch only for current official Abridge workflow and rollout context; tenant build documents remain authoritative.
  6. Use Write or Edit to publish the staged checklist, responsibility matrix, decision log, and rollback trigger.

Approval Boundaries

Do not expand the cohort, care setting, note type, or EHR workflow without the corresponding clinical and change-control approval.

Output

Return cohort, capabilities, owners, rehearsal evidence, training state, support coverage, metrics, stop criteria, and go/no-go authority. Separate verified facts, tenant-specific evidence, assumptions, and actions still awaiting approval.

Error Handling

Condition Response
Licensed capability is uncertain Hold it out of scope until the vendor owner confirms it.
Rollback owner is absent Do not launch.
Pilot metrics omit safety Add clinical-quality and incident measures before approval.

Example

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

setting=outpatient; cohort=25-volunteers; training=complete; test-records=pass; support=covered; rollback=owned; decision=go

Resources

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides safe and well-structured templates for deploying healthcare AI integrations to HIPAA-compliant cloud environments like GCP and AWS. It correctly utilizes secure secret management practices and implements non-root container security. A minor observation is made regarding the interpolation of user-provided environment variables into scripts, which is standard for deployment tools but represents a potential surface for indirect prompt injection.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[care-setting] [cohort]
version
1.5.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "abridge",
  "deployment",
  "change-management",
  "pilot"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live work requires an authorized Abridge tenant, approved test data, and health-system change authority

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/abridge-deploy-integration