Individual skill
channel-pacing-guardrails
Guardrail framework for monitoring spend, efficiency, and CAC thresholds by channel.
plugins/marketing-analytics/skills/channel-pacing-guardrails/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,327 bytes
Read excerpt
# Channel Pacing Guardrails Skill
## When to Use
- Reviewing weekly/monthly pacing to stay within spend and efficiency targets.
- Triggering alerts when CPL/CAC/ROAS drift beyond tolerance.
- Aligning finance + marketing on reallocation decisions.
## Framework
1. **Budget Bands** – define min/max pacing per channel, region, and campaign tier.
2. **Efficiency Guardrails** – set CAC, CPL, ROAS, payback thresholds with warning/critical bands.
3. **Alert Workflow** – specify channels, owners, escalation paths, and notification cadence.
4. **Exception Policy** – document when overrides are allowed and approval requirements.
5. **Post-Mortem Loop** – capture breaches, actions taken, and guardrail adjustments.
