prometheus-configuration — Claude Code skill: setup
Configures Prometheus for metric collection, storage, and monitoring of infrastructure and applications. Use it for scraping, alert rules, and service discovery.
/plugin marketplace add wshobson/agents
/plugin install observability-monitoring@claude-code-workflowsWhat prometheus-configuration does
This skill guides Prometheus setup for infrastructure and application monitoring. It covers scrape configuration, recording rules, alert rules, and service discovery, with practices for metric naming, retention, relabeling, and monitoring Prometheus itself.
Detailed patterns are kept in references/details.md. The guide also covers high availability, federation, and long-term storage with Thanos or Cortex. For troubleshooting, it uses the Prometheus API endpoints http://localhost:9090/api/v1/targets, http://localhost:9090/api/v1/status/config, and a query for up.
You need references/details.md for detailed patterns when the main navigation is not enough.
What it helps with
- configure Prometheus metric scraping
- inspect scrape targets and configuration
- create recording rules for expensive queries
- design alert rules for monitored services
- set up service discovery
Example prompts for the agent
- Configure Prometheus to monitor this infrastructure and its applications.
- Check the Prometheus scrape targets and configuration through the API.
- Create recording rules and alert rules for this project.
How to install prometheus-configuration
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install observability-monitoring@claude-code-workflowsThis installs the whole observability-monitoring plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill prometheus-configuration -a claude-code3Manually: put the files in place
~/.claude/skills/prometheus-configuration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/prometheus-configuration/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill prometheus-configuration -a codex2Manually: put the files in place
.agents/skills/prometheus-configuration/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill prometheus-configuration -a cursor2Manually: put the files in place
.cursor/skills/prometheus-configuration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents prometheus-configuration2Manually: put the files in place
.github/skills/prometheus-configuration/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/observability-monitoring/skills/prometheus-configurationManually: put the files in place
.devin/skills/prometheus-configuration/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 prometheus-configuration
How do I install prometheus-configuration in Claude Code?
Add the marketplace with /plugin marketplace add wshobson/agents, then install the skill with /plugin install observability-monitoring@claude-code-workflows.
What does prometheus-configuration do?
It guides Prometheus setup for metric collection, scrape configuration, recording rules, alert rules, and service discovery. It also covers Prometheus self-monitoring and storage options.
Which platforms support prometheus-configuration?
The skill supports Claude Code, Codex, and Cursor.
Source text
SKILL.md · MIT
--- name: prometheus-configuration description: Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems. --- # Prometheus Configuration Complete guide to Prometheus setup, metric collection, scrape configuration, and recording rules. ## Purpose Configure Prometheus for comprehensive metric collection, alerting, and monitoring of infrastructure and applications. ## When to Use - Set up Prometheus monitoring - Configure metric scraping - Create recording rules - Design alert rules - Implement service discovery ## Detailed patterns and worked examples Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. ## Best Practices 1. **Use consistent naming** for metrics (prefix_name_unit) 2. **Set appropriate scrape intervals** (15-60s typical) 3. **Use recording rules** for expensive queries 4. **Implement high availability** (multiple Prometheus instances) 5. **Configure retention** based on storage capacity 6. **Use relabeling** for metric cleanup 7. **Monitor Prometheus itself** 8. **Implement federation** for large deployments 9. **Use Thanos/Cortex** for long-term storage 10. **Document custom metrics** ## Troubleshooting **Check scrape targets:** ```bash curl http://localhost:9090/api/v1/targets ``` **Check configuration:** ```bash curl http://localhost:9090/api/v1/status/config ``` **Test query:** ```bash curl 'http://localhost:9090/api/v1/query?query=up' ``` ## Related Skills - `grafana-dashboards` - For visualization - `slo-implementation` - For SLO monitoring - `distributed-tracing` - For request tracing
© Seth Hobson · MIT · wshobson/agents