DevOps & Infra Skill
Bash Defensive Patterns
Master defensive Bash programming techniques for production-grade scripts.
$15
SLO Implementation
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with…
A practical framework for defining Service Level Indicators and Objectives with error budgets that turn reliability into a measurable, shared decision tool. It gives you ready Prometheus recording and alerting rules, multi-window burn-rate alerts that cut false positives, and an error-budget policy that tells you exactly when to keep shipping and when to freeze. Replace gut-feel reliability debates with the math of error budgets.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category DevOps & Infra
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
99.9% allows 43 minutes of failure a month; each extra nine costs roughly ten times more. The skill picks user-journey SLIs, writes the error budget into shared policy, and alerts only on multi-window burn rates.
- Pick SLIs from the real user journey, not from what is easy to measure: success ratio and requests under the latency threshold, capped at 2 or 3 SLIs per service so they actually get watched.
- Set the SLO target against cost, not pride: 99.9% means 43.2 minutes of allowed failure per month, and each extra nine costs roughly ten times more, so 99.99% is a decision, not a default.
- Write the error budget policy as shared law between product and engineering: 50% budget remaining postpones risky changes, 10% freezes non-critical deploys, 0% means reliability-only mode.
- Implement it as Prometheus recording rules: SLI ratios over the 28-day window, compliance booleans, budget-remaining percentage and burn rates per time window.
- Alert on multi-window burn rates so nobody is paged for noise: fast burn fires only when both the 1-hour and 5-minute windows exceed 14.4x, slow burn when 6-hour and 30-minute windows exceed 6x.
- Review on a fixed cadence: weekly compliance and budget status, monthly cross-check against postmortems, quarterly target adjustment when the SLO no longer matches reality.
One power source. 6 lines out.
slo-implementation · core
core active · 6 lines
- ✓ defining availability and
Defining availability and latency SLIs for a service
- ✓ setting realistic slo ta…
Setting realistic SLO targets and downtime budgets
- ✓ implementing error budgets
Implementing error budgets to govern release velocity
- ✓ building multi-window bu…
Building multi-window burn-rate alerts that reduce noise
- ✓ creating slo compliance
Creating SLO compliance dashboards
- ✓ running weekly, monthly
Running weekly, monthly, and quarterly SLO reviews
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Make ship-or-freeze decisions with error-budget math instead of opinion
license: perpetual -
Cut alert fatigue with multi-window burn-rate alerting
license: perpetual -
Avoid over-engineering by choosing the SLO target your business actually needs
license: perpetual -
Give product and engineering one shared language for reliability
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
SLI definitions for availability, latency, and durability with PromQL
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
SREs, platform engineers, and engineering leads who want to set, measure, and act on reliability targets instead of guessing.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We don't use Prometheus, how much of this still applies?
The framework itself is tool-agnostic: SLI definitions, error-budget math, target selection, and the review cadence. The ready-made artifacts, however, are PromQL recording rules and burn-rate alerts, so on another stack you would translate those queries yourself.
-
How do multi-window burn-rate alerts actually cut false positives?
A single threshold fires on every blip. Pairing a fast-burn and a slow-burn window means an alert needs both a sharp short-term burn and a sustained trend before it pages anyone, so transient noise stays silent while real budget drain gets attention.
-
Will it decide our SLO targets for us?
No. It gives you the availability reference table mapping targets to downtime budgets and the questions to pick what the business actually needs, but the target itself is a product decision. It explicitly warns against chasing more nines than you need.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.