Agent skill
mimir-prometheus-troubleshoot
Help craft efficient Mimir/Prometheus queries, troubleshoot metric issues, avoid high-cardinality problems, and recommend best practices for aggregation, recording rules, and performance.
Install this agent skill to your Project
npx add-skill https://github.com/timbuchinger/loadout/tree/main/skills/mimir-prometheus-troubleshoot
SKILL.md
Mimir + Prometheus Troubleshooting & Query-Builder Skill
What this Skill does
Use this skill whenever a user needs help with:
- PromQL queries
- Metric debugging
- Missing data / gaps
- Cardinality optimization
- Aggregation strategy
- Recording rules
Best Practices
Low-cardinality label selection
Use labels such as:
job,instance,service,cluster,namespace,env
Avoid:
user_id,session_id,request_id, raw UUIDs
Always narrow time ranges
Prefer "5m", "15m", "1h".
Use correct aggregations
rate()for counterssum by (...)for groupinghistogram_quantile()for latency
Suggest recording rules if query is heavy
Example Queries
| User Request | PromQL |
|---|---|
| "Error rate for payments in prod" | sum by (job) (rate(http_requests_total{job="payments", env="prod", status=~"5.."}[5m])) |
| "Latency p95 for frontend" | histogram_quantile(0.95, sum by (le) (rate(http_request_duration_seconds_bucket{app="frontend"}[5m]))) |
When to Suggest Loki or Tempo
For:
- request IDs
- root-cause event-level debugging
- full request paths
→ Recommend Tempo + Loki correlations.
Limitations
- Skill does not run PromQL
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
timbuchinger/loadout
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
timbuchinger/loadout
add-note
Use this skill whenever important information is learned during a task or when the user explicitly asks to store something. Use when users ask to remember. Triggers on "remember this", "update memory", "share" or any persistent storage request.
timbuchinger/loadout
user-story
Creates well-structured user stories for software development and project management. Use when the user asks to write, create, or format a user story, or needs to document requirements, features, or tasks in user story format.
timbuchinger/loadout
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
timbuchinger/loadout
kubernetes-troubleshoot
Troubleshoot and manage Kubernetes clusters, including resource inspection, debugging, pod logs, events, and cluster operations. Use when the user needs to diagnose issues, inspect workloads, analyze pod failures, or perform Kubernetes cluster operations.
timbuchinger/loadout
writing-plans
Use when design is complete and you need detailed implementation tasks - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming minimal codebase familiarity
Didn't find tool you were looking for?