Individual skill
guardrail-scorecard
Framework for defining, monitoring, and enforcing guardrail metrics across experiments.
plugins/growth-experiments/skills/guardrail-scorecard/SKILL.md
Source commit 78e0419f4440bcb43bc80127e174ecf5adef1753
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 438
- Repository last updated
- Apr 3, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,302 bytes
Read excerpt
# 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.
