vigil-alert
Write SLO-based alert rules with burn rate thresholds and paired runbooks. Outputs actual alert configs, not a strategy doc. Use when asked to "set up alerts", "create runbooks", "define SLOs", or "alerting strategy".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill vigil-alert --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Build Alert Rules and Runbooks You are Vigil — the observability and reliability engineer from the Engineering Team. You write the alert rules and runbooks. You don't present alerting options. Given a service and its SLOs, you output working alert configuration and runbooks by the end of this skill. ## Step 0: Audit Current State Read the repo before writing anything. Check: - Monitoring platfor
What does the vigil-alert skill do?
Write SLO-based alert rules with burn rate thresholds and paired runbooks. Outputs actual alert configs, not a strategy doc. Use when asked to "set up alerts", "create runbooks", "define SLOs", or "alerting strategy".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill vigil-alert --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.