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

/abridge-common-errors

@820dfc8
Run it yourself

Triage Abridge recording, note-review, Epic handoff, and access failures from observed evidence without inventing vendor error codes. Use when an Abridge clinical workflow is degraded. Trigger with "diagnose this Abridge issue".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

Description uses 3.1% 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 ≈252 characters, or 3.1%.

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 Workflow Failure Triage

Overview

Classify the failure by user-visible stage, preserve a minimum-necessary timeline, and route it to the correct health-system, EHR, device, identity, network, or Abridge owner. Prefer observed messages and approved runbooks over generic HTTP guesses.

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

  • The documented workflow spans patient selection, recording, note creation, Web Editor review, and optional Epic handoff.
  • Linked Evidence is a review aid that connects note text to source transcript or audio; it is not an automatic clinical approval.
  • Public support pages provide user workflows, not a canonical public list of partner API status codes.

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. Record the environment, affected cohort, first observed time, last known good time, and exact visible symptom.
  2. Use Read, Glob, and Grep to locate the approved runbook, interface contract, recent configuration change, and feature-flag history.
  3. Separate capture/device failures, upload or connectivity failures, note-generation delays, editor issues, and EHR handoff failures.
  4. Check whether the problem follows one user, device, location, specialty, note type, or EHR workflow without collecting note content.
  5. Use WebFetch only to compare the symptom with current official Abridge support guidance.
  6. Use Write or Edit to produce a redacted escalation receipt and update a runbook only when evidence supports the change.

Approval Boundaries

Do not replay a patient encounter, open a patient note, change an EHR template, or disable a security control solely to diagnose a failure. Escalate clinical-safety concerns immediately.

Output

Return impact, stage, evidence, likely owning boundary, safe checks completed, stop conditions, and the exact redacted artifact needed for escalation. Separate verified facts, tenant-specific evidence, assumptions, and actions still awaiting approval.

Error Handling

Condition Response
Patient content appears in evidence Stop collection and move to the approved protected support channel.
No exact timestamp or user-visible symptom Request bounded evidence before assigning a cause.
Clinical note may be unsafe Pause downstream use and invoke the clinical-safety escalation path.

Example

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

stage=epic-handoff; cohort=one-clinic; capture-and-review=healthy; owner=local-ehr-template; phi-in-receipt=no; status=escalate

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 a diagnostic framework for triaging Abridge clinical recording and workflow issues with a focus on security and data privacy. It includes explicit instructions to avoid capturing Protected Health Information (PHI) and prohibits the use of hardcoded credentials. All external documentation links point to official vendor support pages, and the skill mandates redaction and strict environment authorization.

  • 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
[environment] [symptom] [time-window]
version
1.5.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "abridge",
  "troubleshooting",
  "clinical-workflow",
  "support"
]
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-common-errors