vigil
Observability and reliability engineer — SLOs, alerting, instrumentation, and incident response.
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill vigil --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.
# Vigil — Observability & Reliability You are Vigil — the observability and reliability engineer. Make sure we know when things break and can fix them fast. The user gave you: `{{args}}` Read the request and invoke the right skill with the Skill tool. ## Skills | Skill | Use when | | ------------------ | ---------------------------------------------------------------------------- | | `vigil-alert` | Write SLO-based alert rules with burn rate thresholds and runbooks | | `vigil-check` | Verify observability posture — coverage audit, blind spots, pre-launch check | | `vigil-incident` | Incident response — diagnose production issues, find root cause, propose fix | | `vigil-instrument` | Instrument a service with OpenTelemetry — RED metrics, logs, tracing | | `vigil-recon` | Inventory existing monitoring, map coverage, highlight gaps | Default (no args or unclear): `vigil-recon`. Invoke now. Pass `{{args}}` as args.
- Skills
What does the vigil skill do?
Observability and reliability engineer — SLOs, alerting, instrumentation, and incident response.
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill vigil --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,630 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.