Skip to main content
skill CX Codex

support-ops — Claude Code skill: what it does, how to install

support-ops is a Claude Code skill that computes SLA breaches, interval staffing via Erlang C, and deflection targets using ticket export CSV files.

MIT ★ 30,251 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add alirezarezvani/claude-skills
/plugin install business-growth-skills@claude-code-skills
Open on GitHub

What support-ops does

The skill processes CSV and JSON exports from any helpdesk through three Python standard library scripts without external API credentials. It checks first-response and resolution SLA targets on business or calendar schedules, counting currently open overdue tickets as misses.

For phone and live chat queues, staffing requirements are calculated using Erlang C with shrinkage, concurrency, and occupancy thresholds. Email staffing uses workload formulas with backlog burn-down, highlighting roster shortages per interval instead of smoothing peaks across the day.

Contact reasons are sorted by Pareto distribution into knowledge base articles, automated macros, or bug reports for engineering. Running these evaluations requires Python and exported ticket data.

What it helps with

  • calculate SLA attainment across business hours and holidays
  • detect open tickets approaching resolution breaches
  • determine agent scheduling per interval via Erlang C
  • separate topics for deflection, automation, and bug fixes

Example prompts for the agent

  • Check SLA attainment for tickets.csv using sla_policy.json
  • Calculate interval staffing for volumes.csv with aht 420 and concurrency 2
  • Analyze tickets.csv to find candidates for self-service deflection

How to install support-ops

1Plugin marketplace

/plugin marketplace add alirezarezvani/claude-skills
/plugin install business-growth-skills@claude-code-skills

This installs the whole business-growth-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add alirezarezvani/claude-skills --skill support-ops -a claude-code

3Manually: put the files in place

~/.claude/skills/support-ops/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/support-ops/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about support-ops

How to install support-ops in Claude Code?

Run both commands in sequence: first /plugin marketplace add alirezarezvani/claude-skills, then /plugin install business-growth-skills@claude-code-skills.

What does support-ops do?

The skill evaluates helpdesk ticket exports, calculating business-hours SLA attainment, interval agent scheduling via Erlang C, and contact deflection candidates.

What is required to run support-ops?

It requires Python with standard libraries and a helpdesk ticket export in CSV or JSON format. No helpdesk API keys or credentials are used.

Source text

SKILL.md · MIT
---
name: support-ops
description: "Use for any customer support operations question - SLA attainment and breaches (first response, resolution, business hours, weekends, tickets about to breach), how many agents to schedule per hour for a phone, chat or email queue and where the roster is short (Erlang C, service level, handle time, shrinkage, occupancy, backlog), or which ticket topics to deflect with help-center articles, automate with macros or fix as product bugs. Works from a helpdesk ticket export with stdlib scripts."
argument-hint: "<tickets.csv> [--policy sla.json] | --intervals volumes.csv --aht SECONDS"
license: MIT
metadata:
  version: 1.0.0
  build_pattern: "Three deterministic stdlib scripts over a helpdesk ticket export (business-hours SLA attainment and breach risk, Erlang C and workload staffing with shrinkage and occupancy caps, Pareto deflection finder with root-cause routing); methods cited to Erlang 1917, Gans-Koole-Mandelbaum 2003, Little 1961, the KCS v6 Practices Guide and ITIL 4"
  distinct_from: "customer-success-manager (account health, churn, expansion); chief-customer-officer-advisor (retention strategy and CS org); capacity-planner (headcount and hiring order from daily demand at target utilization; this skill schedules per interval against a roster); incident-commander (production incidents, not the support queue)"
---

# Support Ops

> **Portability:** 3 stdlib Python scripts over CSV/JSON you export from any helpdesk. No helpdesk API, no credentials.

Support teams usually argue from anecdotes: "we're swamped", "the SLA is
fine", "we need an FAQ". The ticket export settles each one. This skill
measures SLA attainment on the clock the contract actually uses, sizes the
team with queueing math instead of tickets-per-agent rules of thumb, and
separates topics an article can deflect from topics only a product fix will.

## Workflow

```bash
# 1 - Are we keeping the promise? What breaches next?
python scripts/sla_check.py --tickets tickets.csv --policy sla_policy.json
# 2 - How many people, when?
python scripts/staffing_plan.py --mode live --intervals volumes.csv --aht 420 --concurrency 2
python scripts/staffing_plan.py --mode async --arrivals 30 --aht 600 --backlog 120
# 3 - Which contact reasons should stop reaching agents?
python scripts/deflection_finder.py --tickets tickets.csv
```

**Step 1** computes first-response and resolution attainment per priority on
business or calendar hours (holidays included), p50/p90, open tickets already
breached or due within `--risk-hours`, backlog age and reopen rate. Open
tickets past target count as misses.

**Step 2** uses Erlang C for phone and chat (service level, ASA, occupancy cap,
shrinkage, chat concurrency) and workload plus backlog drain for email. With a
`staffed` column it shows the gap per interval.

**Step 3** ranks the Pareto head of contact reasons and routes each one:
DEFLECT when one answer resolves most tickets and few reopen, AUTOMATE when
agents adapt a common answer, FIX_ROOT_CAUSE when tickets reopen or describe a
defect, REVIEW otherwise.

## Hard rules

- **Ask which clock the SLA runs on** (business or calendar, timezone, holidays) before reporting attainment. Never assume.
- **Open breaches count.** Never report attainment on closed tickets only.
- **Run `sla_check.py`, don't count hours by hand.** Business-hours arithmetic across evenings and weekends is where manual counts go wrong. Name each breached and at-risk ticket with the time left, and say when a clock started later than the ticket (after hours, weekend).
- **Staff to the interval, not the day.** A daily average hides the 11:00 peak.
- **Headcount and hiring order belong to capacity-planner** (business-operations). This skill schedules the agents you have, interval by interval.
- **Never write an article for a defect.** FIX_ROOT_CAUSE goes to engineering with ticket count and hours.
- **Deflection savings are an upper bound** until contact rate for the topic is measured after launch.
- **State every default** (attainment target, service level, shrinkage, occupancy cap, concurrency, Pareto cut).

## Report

Answer in the reply, not only in a file, and never edit the user's input files.
Show the working a reviewer would check: the load in Erlangs (arrivals x AHT /
3600), the agent count one below the answer and the service level it misses
with, scheduled = on line / (1 - shrinkage), and for each breached or at-risk
ticket the time used, the time left and when its clock started (a ticket that
arrives after hours or on a weekend starts at the next opening).

## Scripts

| Script | Role | Exit codes |
|---|---|---|
| `scripts/sla_check.py` | Attainment, p50/p90, breached and at-risk open tickets, backlog age, reopens | 0 ok · 2 at risk / below target · 3 bad input · 4 open breaches |
| `scripts/staffing_plan.py` | Agents on line and scheduled per interval, roster gap | 0 ok · 2 roster short · 3 bad input |
| `scripts/deflection_finder.py` | Pareto of contact reasons with DEFLECT / AUTOMATE / FIX_ROOT_CAUSE / REVIEW | 0 none · 2 candidates · 3 bad input |

All support `--help`, `--sample` and `--output json` (`--format` is an alias).

## References and assets

- [`references/sla_design_and_measurement.md`](references/sla_design_and_measurement.md): metrics, clocks, setting targets (5 sources)
- [`references/staffing_and_erlang_c.md`](references/staffing_and_erlang_c.md): the model, its gaps, defaults (5 sources)
- [`references/deflection_and_kcs.md`](references/deflection_and_kcs.md): deflect vs automate vs fix, KCS, honest savings claims (5 sources)
- [`assets/sla_policy.example.json`](assets/sla_policy.example.json), [`assets/tickets.example.csv`](assets/tickets.example.csv), [`assets/intervals.example.csv`](assets/intervals.example.csv)

© Alireza Rezvani · MIT · alirezarezvani/claude-skills

Similar skills

All skills for Notes, tasks and projects →

From the same set488

The whole set →
coding-agent-rollout coding-agent-rollout audits Claude settings before a team rollout: lints permissions across scopes, inventories MCP servers and plugins, and turns local session data into adoption counts. CX Codex +1 1installs agent-regression-evals agent-regression-evals is a Claude Code skill that statistically tests agent prompt, model, and tool updates against a baseline, distinguishing true pass-rate regressions from noise. CX Codex +1 1installs grade-iterate grade-iterate is a Claude Code skill for phase 3 of building a Claude Managed Agent. It sets a rubric, reads grader verdicts, and iterates until a version passes. CX Codex +1 1installs support-ops support-ops is a Claude Code plugin that checks support SLAs, plans agent coverage, and finds deflection targets. It works from a helpdesk ticket export. ★ 30,251repo stars cs-compliance-officer cs-compliance-officer orchestrates compliance across multiple frameworks, maps overlapping controls, and creates a unified evidence repository to prevent duplicated audit work. CX Codex ★ 30,251repo stars plugin-audit Audits skills, plugins, agents, and commands for structure, quality, security, and ecosystem checks. Use it before publishing or changing a repository. CX Codex +1 ★ 30,251repo stars cs-demand-gen-specialist cs-demand-gen-specialist is a subagent for planning acquisition channels: it allocates budgets, calculates CAC and ROAS, audits ad-account health, and designs email nurture sequences. CX Codex ★ 30,251repo stars seo-auditor seo-auditor audits Markdown documentation and README files for frontmatter tags, broken links, headings, and keyword density, then applies fixes and creates a report. CX Codex +1 ★ 30,251repo stars

Project sponsors

Companies that keep this analytics open