smithery/gtmagents

guardrail-scorecard

Framework for defining, monitoring, and enforcing guardrail metrics across experiments.

Installation

$ npx skills add smithery/gtmagents --skill guardrail-scorecard

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,302 B
  • docs SUMMARY.md 114 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.