Skill: Setup monitoring
SkillMonitoring & opsGuide for setting up or extending monitoring (metrics, logs, alerts) for a service. Use when the user asks to set up monitoring or add alerts.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Skill: Setup monitoring skill
What this skill tells your AI
The instructions your AI receives, as published by girijashankarj/cursor-handbook in .cursor/skills/devops/setup-monitoring/SKILL.md and read by ahel’s review.
Trigger
When the user asks to set up monitoring, add alerts, or configure dashboards.
Steps
- Scope — Identify what to monitor (API latency, errors, DB, queue depth) and where (cloud provider, vendor).
- Metrics — Define 3–5 key metrics (e.g. request rate, error rate, p99 latency); use structured logging with correlationId.
- Alerts — Propose thresholds (e.g. error rate > 1%, p99 > 2s) and severity; document in runbook.
- Dashboard — List panels to add (time series, status); use placeholders for dashboard URLs.
- Logs — Remind: no PII or secrets; JSON format; include correlationId per project rules.
Rules
- Follow
.cursor/rules/devops/monitoring.mdc. Use placeholder resource names.
Signals
- GitHub stars
- 30
- Forks
- 3
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
setup-monitoring- Source
- github.com/girijashankarj/cursor-handbook