Skip to content
Automation
Skill

/guardrail-scorecard

Framework for defining, monitoring, and enforcing guardrail metrics across

From plugin
gtm-agents
368200 skills200 agents199 commands
Install
$ npx -y skills add gtmagents/gtm-agents --skill guardrail-scorecard --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/guardrail-scorecard

Context preview

The summary Claude sees to decide when to auto-load this skill.

Framework for defining, monitoring, and enforcing guardrail metrics across

SKILL.md

guardrail-scorecard.SKILL.md
name: guardrail-scorecard
description: Framework for defining, monitoring, and enforcing guardrail metrics across
  experiments.

Guardrail Scorecard Skill

When to Use

  • Setting non-negotiable metrics (stability, churn, latency, compliance) before launching tests.
  • Monitoring live experiments to ensure guardrails stay within thresholds.
  • Reporting guardrail status in launch packets and post-test readouts.

Framework

1. **Metric Inventory** – list guardrail metrics, owners, data sources, refresh cadence. 2. **Threshold Matrix** – define warning vs critical bands per metric / persona / region. 3. **Alerting & Escalation** – map notification channels, DRI, and decision timelines. 4. **Exception Handling** – document when guardrail overrides are acceptable and required approvals. 5. **Retrospective Loop** – log breaches, mitigations, and rule updates for future tests.

Templates

  • Guardrail register (metric, threshold, owner, alert channel).
  • Live monitoring dashboard layout.
  • Exception memo structure for approvals.

Tips

  • Tie guardrails to downstream systems (billing, support) to catch second-order impacts.
  • Keep thresholds dynamic for seasonality but document logic.
  • Pair with `launch-experiment` to ensure readiness before flipping flags.

---

Ships withgtm-agents

Free AI automation for sales, marketing, and growth teams. No coding required.

Get the whole plugin