devops-sre-engineer
Build Reliable DevOps and SRE Workflows
Complex delivery and reliability work often spans disconnected tools and operational practices. This skill provides structured workflows for implementation, diagnosis, automation, and review.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "devops-sre-engineer" from https://skillstore.io/skills/zl2023github-devops-sre-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-devops-sre-engineer/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.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 "devops-sre-engineer". Our API has rising latency and intermittent errors after yesterday's release.
Expected outcome:
- Impact: Confirm affected endpoints, users, regions, and the current error budget burn.
- First checks: Compare deployment timing with latency, errors, saturation, logs, traces, and dependency health.
- Mitigation: Prepare a reviewed rollback or traffic reduction after validating the suspected release.
Using "devops-sre-engineer". Design a release process for a containerized service on Kubernetes.
Expected outcome:
- Continuous integration: lint, test, build, dependency scan, image scan, and signed artifact publication.
- Promotion: deploy to development, verify health, promote to staging, require approval, then release to production.
- Recovery: retain the prior image and manifests, define rollback criteria, and verify service indicators after release.
Using "devops-sre-engineer". Help define an availability objective for a customer API.
Expected outcome:
- Indicator: Successful eligible requests divided by all eligible requests at the service boundary.
- Objective: Select a target from historical performance and customer needs, then calculate its monthly error budget.
- Policy: Slow releases when burn accelerates and freeze risky changes when the budget is exhausted.
Security Audit
CriticalMost alerts are false positives caused by Markdown backticks, placeholders, standard device handling, readable Chinese text, and routine local diagnostics. The Docker Bench example grants a remote image Docker socket and host namespace access, creating critical host compromise risk. Unpinned cluster installation, ungated destructive commands, and unrestricted load testing require correction before publication.
Confirmed security concerns (4)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (7)
📁 Filesystem access (3)
Detected Patterns
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/zl2023github-devops-sre-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/zl2023github-devops-sre-engineer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/zl2023github-devops-sre-engineer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-devops-sre-engineer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/zl2023github-devops-sre-engineer.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
zl2023github. (2026). devops-sre-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-devops-sre-engineer/audits/4BibTeX citation
@techreport{zl2023github-zl2023github-devops-sre-engineer-2026,
author = {zl2023github},
title = {devops-sre-engineer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-devops-sre-engineer/audits/4},
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: "devops-sre-engineer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/zl2023github-devops-sre-engineer/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-devops-sre-engineer:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Create a Delivery Pipeline
Design staged build, test, scan, approval, deployment, health check, and rollback workflows for an application.
Investigate a Production Incident
Organize impact assessment, recent-change review, metrics, logs, traces, dependency checks, recovery, and postmortem actions.
Establish Reliability Controls
Define service indicators, objectives, error budgets, dashboards, alerts, capacity assumptions, and release policies.
Try These Prompts
Review my deployment setup for [service] in [environment]. Identify missing checks, risks, and the next three safe improvements.
Diagnose [symptom] using these metrics, logs, events, and recent changes: [evidence]. Separate observations, hypotheses, tests, mitigation, and follow-up.
Design a CI/CD and GitOps workflow for [stack], [repository], and [platform]. Include approvals, security scans, promotion, rollback, and verification.
Create a reliability plan for [service]. Define SLIs, SLOs, error budgets, capacity tests, observability, failure experiments, governance, and implementation phases.
Best Practices
- Provide architecture, environment, constraints, recent changes, and available evidence before requesting operational guidance.
- Review plans and previews before changes, then verify health indicators and rollback readiness.
- Run performance, chaos, security, and recovery tests only in approved scopes with monitoring and stop conditions.
Avoid
- Do not execute destructive commands from a generic example against an unverified target.
- Do not place secrets, tokens, private keys, or sensitive production data in prompts.
- Do not treat generated guidance as approval for production, security, or compliance changes.
Frequently Asked Questions
Can this skill execute infrastructure changes?
Which platforms does it cover?
Can it troubleshoot production incidents?
Does it replace an SRE or security review?
How should load tests be handled?
What context improves the output?
Developer Details
Author
zl2023githubLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
5 downloads · 1 views
File structure
📄 SKILL.md