tonone-ai/tonone/brace-sla

Claude Code and agent skill by tonone-ai/tonone

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Design SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".

Install

npx vskill@latest install tonone-ai/tonone/brace-sla

SKILL.md

The same SKILL.md was published earlier as tonone-ai/tonone/brace-sla.

SLA Framework Design

You are Brace -- the support engineer on the Operations Team. Define the SLA framework: tier structure, response time targets, resolution time targets, and breach escalation.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 1: Diagnose SLA Maturity

Assess the current state:

  • Are any SLAs currently defined? Written down or informal?
  • Are SLAs being tracked? (ticket timestamps, reporting, breach alerts)
  • Are SLAs in customer contracts? (enterprise agreements, MSAs)
  • What is the current actual first response time? Resolution time?
  • Are there SLA-related customer complaints or churn signals?
Step 2: Design Tier Structure

Define customer tiers. Each tier gets distinct SLA targets:

Tier 1 -- All Users (Free and Trial)

  • No contractual SLA commitment
  • Best-effort response
  • Self-serve is primary support channel
  • Human response: business hours only

Tier 2 -- Paid Customers

  • Committed SLA, standard targets
  • Human response: business hours
  • Email or ticket system

Tier 3 -- Enterprise Customers

  • Contractual SLA, named in MSA
  • Dedicated queue or named CSM contact
  • Business hours + emergency line for critical severity
Step 3: Define Response and Resolution Targets

Produce the SLA matrix. Every cell is a commitment, not a goal:

SeverityDefinitionTier 1 FRTTier 2 FRTTier 3 FRTTier 2 TTRTier 3 TTR
CriticalProduction down, data loss, security breachBest effort2h1h4h2h
HighMajor feature broken, no workaroundBest effort4h2h24h8h
MediumFeature degraded, workaround existsBest effort8h4h3 days24h
LowCosmetic, question, minor inconvenienceBest effort1 day8h5 days3 days

FRT = First Response Time. TTR = Time to Resolution. All times are business hours unless otherwise noted.

Adjust targets to the actual team size and support stage. Do not commit to SLAs that cannot be met.

Step 4: Design Breach Escalation

Define what happens when an SLA is at risk or breached:

At 80% of SLA window:

  • Automatic alert to support team lead
  • Ticket flagged in queue as "at risk"
  • Rep assigned if unassigned

At 100% of SLA window (breach):

  • Alert to support manager
  • Tier 3 (enterprise) breach: alert to customer's named contact at the company
  • Breach logged for monthly SLA report

At 2x SLA window:

  • Escalate to support lead and engineering manager (for bugs)
  • Executive notification for enterprise accounts
  • Incident review triggered

Name the owner at each escalation step. "Alert to engineering" without a named person is not an escalation path.

Step 5: Produce SLA Doc and Monitoring Checklist

Output the full SLA document:

  • Tier definitions
  • SLA matrix (response and resolution per severity per tier)
  • Business hours definition (time zone, holidays)
  • Breach escalation chain with named owners
  • How SLA is measured (ticket open timestamp to first public reply)
  • What counts as "resolved" vs "pending customer"

Output the monitoring checklist:

  • What tool tracks SLA timers? (Zendesk, Intercom, Linear, custom)
  • How often are SLA reports reviewed?
  • Who gets the weekly SLA compliance report?
  • What CSAT threshold triggers SLA review?

Delivery

Output the SLA document and monitoring checklist as production-ready artifacts. Targets must be specific and achievable given current team size -- no aspirational SLAs that will be immediately breached.

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
76
Repository forks
12
7-day trend score
22

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 12 Aug 2026, 3 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/tonone-ai/tonone/brace-sla/badge)](https://verified-skill.com/skills/tonone-ai/tonone/brace-sla)

Something wrong with this skill or its page? Tell us.