vigil-check
From the author
Verify observability posture — audit monitoring coverage, find blind spots, prioritize gaps. Use when asked "is monitoring sufficient", "observability review", "are we covered", or "pre-launch monitoring check".
Install
npx skills add tonone-ai/tonone --skill vigil-check -a claude-code
Installs to .claude/skills/vigil-check/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- vigil-recontonone-ai/tononeObservability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".DevOps★ 76
- observability-and-instrumentationaddyosmani/agent-skillsInstruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.DevOps★ 110.1K
- vigiltonone-ai/tononeObservability and reliability engineer — SLOs, alerting, instrumentation, and incident response. Use when asked to "set up alerting", "define SLOs", "write a runbook", or "review incident response".DevOps★ 76
- observabilityDevelopersGlobal/ai-agent-skillsStructured logging, distributed tracing, and alerting for AI systems and traditional services. You can't fix what you can't see.DevOps★ 213
- observability-and-reliabilitycbrock84/headcountMakes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.DevOps★ 2.1K
- observability-instrumentationBlackBeltTechnology/pi-agent-dashboardMake runtime behavior visible and diagnosable. Use on triggers like "add logging/metrics/tracing", "instrument this", "add alerting", "we can't tell what happened in prod", or when a feature needs evidence it works at runtime. Fills an instrumentation gap not covered by the project's existing skills. Not a ship or release workflow.DevOps★ 331
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in