observability-monitoring — Claude Code skill: features, install
This skill covers Prometheus and Grafana monitoring, from metric collection and PromQL to alerts and dashboards for distributed services.
npx skills add manutej/luxor-claude-marketplace --skill observability-monitoring -a claude-codeWhat observability-monitoring does
The skill guides monitoring work for applications and distributed systems with Prometheus, Grafana, and related cloud-native components. It covers metric collection, time-series analysis, dashboards, alert rules, and service targets such as SLIs, SLOs, and SLAs.
Its material is organized around Prometheus components: the TSDB, scrape targets, service discovery, PromQL, Alertmanager, and exporters. It also discusses labels, recording rules, logs, traces, and events, with configuration examples for Kubernetes and static scrape targets.
High-cardinality labels increase memory and storage usage, so label dimensions should match the queries you actually need. Installation requires npx or gh, depending on the platform.
What it helps with
- configure metric collection for services
- build dashboards for system health
- define alert rules and routing paths
- analyze time-series data with PromQL
- set service indicators and reliability targets
Example prompts for the agent
- Set up Prometheus and Grafana monitoring for this API, including scrape targets and alert rules.
- Review
prometheus.ymland suggest recording rules for the queries used most often. - Design application metrics, SLIs, and SLOs for these microservices while avoiding excessive label cardinality.
How to install observability-monitoring
1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill observability-monitoring -a claude-code2Manually: put the files in place
~/.claude/skills/observability-monitoring/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/observability-monitoring/
1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill observability-monitoring -a codex2Manually: put the files in place
.agents/skills/observability-monitoring/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill observability-monitoring -a cursor2Manually: put the files in place
.cursor/skills/observability-monitoring/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install manutej/luxor-claude-marketplace observability-monitoring2Manually: put the files in place
.github/skills/observability-monitoring/SKILL.md1Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill observability-monitoring -a gemini-cli2Platform CLI
gemini skills install https://github.com/manutej/luxor-claude-marketplace --path plugins/luxor-devops-suite/skills/observability-monitoringManually: put the files in place
.devin/skills/observability-monitoring/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add manutej/luxor-claude-marketplace --skill observability-monitoring -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about observability-monitoring
How do I install observability-monitoring in Claude Code?
Run npx skills add manutej/luxor-claude-marketplace --skill observability-monitoring -a claude-code, then check ~/.claude/skills/observability-monitoring/SKILL.md.
What does observability-monitoring do?
It helps design Prometheus and Grafana monitoring, including metric collection, PromQL analysis, dashboards, alerting, exporters, and service objectives.
Why does label cardinality matter?
Every distinct label combination creates a separate time series. Large cardinality raises memory and storage consumption.