operating-production-services
Operate Reliable Production Services
Production teams need clear reliability targets and repeatable incident practices. This skill provides SLO guidance, burn-rate alert patterns, and blameless postmortem templates.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "operating-production-services" from https://skillstore.io/skills/asmayaseen-operating-production-services.md and its manifest at https://skillstore.io/api/skills/asmayaseen-operating-production-services/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "operating-production-services". Our API requires 99.9% monthly availability. Create an error-budget policy.
Expected outcome:
- Above 50%: continue normal delivery.
- From 10-50%: delay high-risk changes.
- Below 10%: freeze non-critical changes.
- At 0%: prioritize reliability work.
Using "operating-production-services". A deployment caused 20 minutes of errors and rollback restored service. Draft a postmortem outline.
Expected outcome:
The outline includes an executive summary, UTC timeline, customer impact, 5 Whys analysis, immediate correction, and assigned prevention actions.
Using "operating-production-services". Propose an alert strategy for a 99.9% availability SLO.
Expected outcome:
- Use a fast-burn alert to detect rapid budget consumption.
- Use a slow-burn alert to catch sustained degradation.
- Validate thresholds with historical traffic before paging.
Security Audit
SafeAll 15 static findings are false positives. Ten findings are Markdown fences for formulas, PromQL, and templates; five are standard 5 Whys prompts, not system reconnaissance. No prompt injection, malicious intent, data exfiltration, or unsafe command construction was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/asmayaseen-operating-production-services/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/asmayaseen-operating-production-services?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/asmayaseen-operating-production-services?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/asmayaseen-operating-production-services/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/asmayaseen-operating-production-services.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Asmayaseen. (2026). operating-production-services security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/asmayaseen-operating-production-services/audits/9BibTeX citation
@techreport{asmayaseen-asmayaseen-operating-production-services-2026,
author = {Asmayaseen},
title = {operating-production-services security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/asmayaseen-operating-production-services/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "operating-production-services security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Asmayaseen"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/asmayaseen-operating-production-services/audits/9"
identifiers:
- type: other
value: "skillstore:asmayaseen-operating-production-services:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Set service objectives
Define measurable availability and latency objectives, then connect them to error-budget policies.
Build actionable alerts
Adapt Prometheus recording rules and multi-window burn-rate alerts for an existing service.
Lead incident learning
Turn incident facts into a blameless postmortem, clear timeline, root-cause analysis, and owned actions.
Try These Prompts
For [service], define one availability SLI, a realistic 28-day SLO, and the resulting monthly error budget. Explain each choice.
Create an error-budget policy for [service] with actions above 50%, from 10-50%, below 10%, and at exhaustion.
Using these incident facts: [facts], draft a blameless postmortem with summary, UTC timeline, 5 Whys, impact, and owned action items.
For [service metrics] and [SLO target], propose Prometheus availability and latency SLIs, recording rules, and fast and slow burn-rate alerts. State assumptions.
Best Practices
- Replace example metric names, targets, and thresholds with validated service data.
- Connect every postmortem action to an owner, due date, and tracking ticket.
- Review burn-rate alerts against historical incidents before paging the on-call team.
Avoid
- Do not adopt 100% SLOs without considering cost and error budgets.
- Do not page directly on raw SLIs when burn-rate context is available.
- Do not use postmortems to blame individuals or create unowned actions.
Frequently Asked Questions
Does this skill configure monitoring systems?
Which monitoring stack do the examples target?
Can this skill manage an active incident?
How should teams choose SLO targets?
Does the verification script validate alerts?
Which postmortem formats are included?
Developer Details
Author
AsmayaseenLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Repository
https://github.com/Asmayaseen/hackathon-2/tree/main/.claude/skills/operating-production-servicesRef
89edfdc710d0846129dcee6a929477b04f08052c
Maintenance freshness
7/24/2026
Usage
11 downloads · 208 views
File structure