- Home
- Skills
- Data & Databases
- Log-to-SLO Compiler
Works with the AI Agents you already use
Log-to-SLO Compiler
Turn real logs into SLIs, SLOs, error budgets and burn-rate alerts that fire on user pain.
$15
Log-to-SLO Compiler
Example session with this skill installed
We have 40 alerts and no SLOs. On-call pages for things users never noticed, and misses things they do. Here are 30 days of access logs and our service list.
- Read your context and instructions
- Compiled the log-to-slo compiler
Worked example — illustrative data.
SLOs: checkout service
User journeys
- Complete a purchase (tier 1). 2. View order history (tier 2). 3. Apply a discount code (tier 2).
SLIs
| SLI | Query | Exclusions |
|---|---|---|
| Availability | good: status < 500 on /checkout; valid: all /checkout | health checks, synthetic probes |
| Latency | good: p95 under 500ms; valid: all /checkout | bot traffic |
| Correctness | good: order id returned and amount matches cart | none |
SLOs and budgets
Availability 99.9% over 28 days: budget 0.1% of requests, about 40 minutes of full outage. Below 25% remaining, reliability work takes priority over features. Exhausted: freeze risky changes.
Alerts
| Alert | Burn rate | Window | Route |
|---|---|---|---|
| Fast burn | 14.4x | 1h / 5m | page |
| Medium burn | 6x | 6h / 30m | page |
| Slow burn | 1x | 3d / 6h | ticket |
No-data alerts on every SLI, because a silent service passes every ratio check.
Current performance
Measured 99.62% availability and p95 610ms over the 30 days ending 10 Nov. The target is a stretch, not a description.
Gaps
Correctness needs an order id in the log line; added to the instrumentation backlog.
Connects securely to your tools. The creator never sees your data.
About this skill
SLI and SLO compiler: derive reliability targets and error budgets from the logs you already collect, with alert thresholds that hold.
Use this skill when:
- define SLIs and SLOs
- set error budgets
- turn logs into reliability targets
- fix alert fatigue
Who it's for: SRE and platform teams without formal SLOs.
Example request
We have logs but no SLOs. Give us three we can defend.
What the example returns
- SLIs built from request events
- SLOs with error budgets
- Alerts that page once, not hourly
In the package: five files — SKILL.md with the trigger and workflow, README.md, references/METHOD.md (the full method), references/CHECKLIST.md (the pass/fail gate) and examples/EXAMPLE.md (a worked run you can copy).
Works with Claude Code, Cursor, Codex CLI and any agent that reads SKILL.md. Plain markdown: no API key, no account, no network access.

Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 days ago