Complex delivery and reliability work often spans disconnected tools and operational practices. This skill provides structured workflows for implementation, diagnosis, automation, and review.
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.
Agent request
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.
Most 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.
The command mounts `/var/run/docker.sock` into a remote image with host namespaces and host data. Docker socket control can provide effective root access.
The container joins host network, PID, and user namespaces while inspecting `/var/lib`. This grants extensive host visibility beyond ordinary container isolation.
The skill recommends high-rate tests against a target without requiring ownership, authorization, environment isolation, rate ceilings, monitoring, or stop conditions.
The examples specify 100 to 1,000 concurrent or per-second requests, and no nearby text limits them to authorized non-production targets.
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.
The command applies a Kubernetes manifest directly from a mutable GitHub `main` branch. Upstream changes could alter cluster resources without local review.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
zl2023github. (2026). devops-sre-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-devops-sre-engineer/audits/4
BibTeX 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 scoreEvidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
74
Spec Compliance
What 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
Review my deployment setup for [service] in [environment]. Identify missing checks, risks, and the next three safe improvements.
Diagnose an Incident
Diagnose [symptom] using these metrics, logs, events, and recent changes: [evidence]. Separate observations, hypotheses, tests, mitigation, and follow-up.
Design a Delivery System
Design a CI/CD and GitOps workflow for [stack], [repository], and [platform]. Include approvals, security scans, promotion, rollback, and verification.
Plan Reliability Engineering
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?
It can propose and support operational steps when tools are available. Human approval remains required for changes to live infrastructure.
Which platforms does it cover?
It covers common CI/CD, container, Kubernetes, GitOps, infrastructure, observability, testing, backup, security, and cloud cost workflows.
Can it troubleshoot production incidents?
Yes. Provide symptoms, timelines, recent changes, metrics, logs, traces, events, and dependency status for a structured investigation.
Does it replace an SRE or security review?
No. Teams must review generated plans against access controls, policies, risk tolerances, compliance duties, and production conditions.
How should load tests be handled?
Use only approved targets with staged rates, monitoring, stop conditions, capacity owners, and a documented test window.
What context improves the output?
Include the service architecture, deployment model, environments, objectives, constraints, tooling, permissions, recent changes, and available operational evidence.