Skip to content
Back to skills

Unlock Schedule Capacity

ASecurity

Find the doctor bottleneck and fix the appointment template so a fully-booked practice can grow throughput. Reach for this when revenue is flat despite full demand.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agents

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill unlock-schedule-capacity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Unlock Schedule Capacity?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Unlock Schedule Capacity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-unlock-schedule-capacity/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-unlock-schedule-capacity)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: unlock-schedule-capacity
description: "Find the doctor bottleneck and fix the appointment template so a fully-booked practice can grow throughput. Reach for this when revenue is flat despite full demand."
---

# Skill: Unlock schedule capacity

Capacity gates revenue; this finds the constraint and relieves it.

## Step 1 — Map utilization
Measure schedule utilization and the doctor bottleneck (§3 #3).

## Step 2 — Redesign the template
Adjust appointment lengths/types and the support hand-off to add doctor throughput.

## Step 3 — Set the support ratio
Tune the tech-to-doctor ratio so doctors work at the top of their license (§3 #7).

## Step 4 — Quantify the unlock
State the added capacity and revenue from the change.

## Output
A capacity read, an appointment-template redesign, a support-ratio recommendation, and the revenue unlock.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…