About sla-tracking
A marketing skill for defining, measuring, and reviewing service-level agreements across marketing, SDR, and sales teams. It provides a structured process and templates for targets, alerts, scorecards, and retrospectives.
Key features
- 01SLA definition and target setting
- 02Pipeline event measurement guidance
- 03Alert and escalation planning
- 04Weekly and monthly review cadence
- 05Scorecard and retrospective templates
Use cases
- 01Setting response and acceptance targets
- 02Building SLA dashboards and alerts
- 03Reviewing breaches and pipeline delays
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/sla-trackingin Claude Code to confirm it loaded.
Details
From the project READMESLA Tracking System Skill
When to Use
- Establishing or revisiting SLA metrics between marketing, SDR, and sales pods.
- Building dashboards/alerts for pipeline speed and follow-up compliance.
- Running retrospectives after SLA breaches or pipeline delays.
Framework
- Definitions – clarify timestamps (MQL, SAL, SQL), owner transitions, and acceptance criteria.
- Targets – set response + acceptance SLAs per segment, region, or channel.
- Measurement – configure data pipelines pulling MAP + CRM events, dedupe logic, and exclusions.
- Alerting – thresholds, notification channels, severity levels, and on-call rotation.
- Review Cadence – weekly dashboards, monthly retros, quarterly recalibration.
Templates
- SLA scorecard (segment → target → actual → variance → owner).
- Alert playbook with trigger conditions and escalation steps.
- Retro template capturing root cause, fixes, and follow-up experiments.
Tips
- Anchor SLAs to revenue impact (pipeline $) to drive accountability.
- Include qualitative context (reason codes) to separate data gaps vs true SLA misses.
- Pair with
routing-logicupdates when volume spikes create bottlenecks.
Comments
Markdown supported