Monitoring Plan
Design an observability strategy with metrics, alerts, dashboards, SLOs, and on-call response for a service or feature. Triggers: "monitoring plan", "observability", "alerts", "dashboards", "SLO", "on-call".
Install
$ agentstack add skill-omexit-claude-skills-pack-monitoring-plan ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-omexit-claude-skills-pack-monitoring-plan) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Monitoring plan
What I'll do
Design a comprehensive observability strategy that ensures you know when something is wrong, why it's wrong, and how bad it is — before users tell you.
Inputs I'll use (ask only if missing)
- Service/feature being monitored
- SLOs or performance targets (if defined)
- Current monitoring (what exists already?)
- On-call structure (who responds to alerts?)
- Critical user journeys (what must always work?)
How I'll think about this
- The four golden signals: Start with latency, traffic, errors, and saturation. These cover most problems for most services. Add custom metrics only for domain-specific concerns.
- Alert on symptoms, not causes: Alert when users are affected ("error rate > 1%"), not when a specific thing breaks ("disk at 90%"). Cause-based alerts generate noise; symptom-based alerts are actionable.
- SLOs drive alerting: Define what "good enough" looks like (99.9% availability, p95 -monitoring-plan.md"
sections: [golden_signals, slos, alerts, dashboards, logging]
## Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- **Author:** [OmexIT](https://github.com/OmexIT)
- **Source:** [OmexIT/claude-skills-pack](https://github.com/OmexIT/claude-skills-pack)
- **License:** MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.