Infrastructure work spans many tools, environments, and failure modes. This skill organizes deployment, troubleshooting, automation, monitoring, validation, and documentation into practical workflows.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "ops-engineer" from https://skillstore.io/skills/zl2023github-ops-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-ops-engineer/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.
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.
All 20 static findings are false positives caused by Markdown fences, inline code formatting, Chinese text, or legitimate operational terminology. The file contains readable guidance, not obfuscated content, executable backticks, privilege-escalation commands, or malicious reconnaissance. However, the skill authorizes broad operational execution without mandatory approval and rollback safeguards, creating a high-impact change risk.
The skill directs the agent to execute commands and infrastructure changes without requiring user confirmation, dry runs, least privilege, or rollback checks. Terraform apply and broad operational execution can modify production systems or cause outages.
The execution workflow and Terraform apply capability are explicit, while no approval gate appears in the 327-line skill.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
zl2023github. (2026). ops-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-ops-engineer/audits/4
BibTeX citation
@techreport{zl2023github-zl2023github-ops-engineer-2026,
author = {zl2023github},
title = {ops-engineer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-ops-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: "ops-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-ops-engineer/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-ops-engineer:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance
What You Can Build
Standardize Service Deployment
Prepare container, proxy, health-check, validation, and delivery steps for a repeatable service deployment.
Investigate Production Incidents
Organize read-only system, network, container, and application checks before proposing a controlled fix.
Build Platform Workflows
Plan Kubernetes resources, CI/CD stages, monitoring, alerts, backups, and operational documentation for an internal platform.
Try These Prompts
Plan a Container Deployment
Plan a Docker Compose deployment for [service]. Include dependencies, storage, networking, health checks, secrets handling, validation, and rollback. Do not execute commands.
Diagnose High Server Load
Help diagnose high load on [server type]. Start with read-only checks for CPU, memory, disk, network, and recent changes. Rank likely causes.
Resolve a Kubernetes Failure
Analyze this Kubernetes failure: [symptoms and outputs]. Identify the root cause, propose the smallest change, and define validation. Request approval before changes.
Design a Production Delivery System
Design a delivery system for [application and environment]. Cover infrastructure as code, CI/CD, observability, security, backups, failure recovery, approvals, and phased rollout.
Best Practices
Provide the environment, scope, symptoms, recent changes, constraints, and desired outcome.
Begin with read-only diagnostics and use dry runs before applying changes.
Require explicit approval, backups, validation criteria, and rollback steps for production changes.
Avoid
Do not place passwords, tokens, private keys, or unredacted secrets in prompts.
Do not run unreviewed commands with elevated privileges or against production systems.
Do not skip backups, staged testing, post-change validation, or operational records.
Frequently Asked Questions
Which operational areas does this skill cover?
It covers infrastructure, containers, Kubernetes, CI/CD, monitoring, troubleshooting, automation, security operations, backups, and disaster recovery.
Can it execute commands in my environment?
A compatible agent may execute commands when tools allow it. Review permissions, scope, and every production change before approval.
Does it support Kubernetes troubleshooting?
Yes. It guides pod inspection, log and event analysis, resource checks, corrective changes, and validation.
Can it create monitoring configurations?
Yes. It can guide Prometheus collection, alert rules, Grafana data sources, dashboards, and logging pipelines.
Does it protect secrets automatically?
No. Users must redact credentials, use approved secret stores, restrict access, and review generated configurations.
What should I provide for incident analysis?
Provide symptoms, timestamps, environment details, sanitized logs, metrics, recent changes, and business impact.