Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/observability-sre
Observability and SRE expert.
Passed 21 of 22 test cases with the skill, and 18 of 22 without it.
and 1 more in the full report
3 fixed18 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to set up Prometheus alerting rules for our payment service in production. Could you draft the YAML configuration for our alert rules file? Please include alerts for high response times and elevated error counts so our on-call team gets notified when things degrade.
| Checked | Without skill | With skill |
|---|---|---|
| The YAML configuration defines SLO recording rules instead of raw infrastructure metrics. | Missed | Passed |
| The alerting rules calculate symptom metrics such as latency p95. | Passed | Passed |
The instructions your model reads when the skill loads.
These rules are mandatory. Violating them means the skill is not working correctly.
Alert on user-facing symptoms, not internal infrastructure metrics.
# ❌ FORBIDDEN: Alerting on internal metrics
- alert: CPUHigh
expr: cpu_usage > 70%
# Users don't care about CPU, they care about latency
- alert: MemoryHigh
expr: memory_usage > 80%
# Internal metric, may not affect users
# ✅ REQUIRED: Alert on user experience
- alert: APILatencyHigh
expr: slo:api_latency:p95 > 0.200
annotations:
summary: "Users experiencing slow response times"
- alert: ErrorRateHigh
test cases passed, vs 18 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.