Development
Skill
/prometheus-configuration
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.
Claude Code
$ npx -y skills add wshobson/agents --skill prometheus-configuration --agent claude-code
Codex
$ npx skills add wshobson/agents --skill prometheus-configuration -a codex -y
Cursor
$ npx skills add wshobson/agents --skill prometheus-configuration -a cursor -y
Gemini CLI
$ npx skills add wshobson/agents --skill prometheus-configuration -a gemini-cli -y
GitHub Copilot
$ npx skills add wshobson/agents --skill prometheus-configuration -a github-copilot -y
OpenCode
$ npx skills add wshobson/agents --skill prometheus-configuration -a opencode -y
Windsurf
$ npx skills add wshobson/agents --skill prometheus-configuration -a windsurf -y
SKILL.md
prometheus-configuration.SKILL.mdname: 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:**
curl http://localhost:9090/api/v1/targets
**Check configuration:**
curl http://localhost:9090/api/v1/status/config
**Test query:**
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
Read more
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:**
curl http://localhost:9090/api/v1/targets
**Check configuration:**
curl http://localhost:9090/api/v1/status/config
**Test query:**
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
Stats
42,403
Stars
4,481
Forks
Active
Maintenance
Python
Language
MIT
License
Last commit
Created
Ships withagents
Use one collection of plugins, agents, skills, and commands across Claude Code, OpenAI Codex CLI, Cursor, OpenCode, Antigravity CLI, GitHub Copilot, and Pi. A harness is the coding tool that loads and runs the components.
42k185 skills137 agents
Stars on GitHub
Momentum
- stars in total
- 42.4k
Other skills on agents.
More skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about prometheus-configuration.
- Which coding agents can use prometheus-configuration?
- prometheus-configuration installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.