Covers CI/CD pipelines, Dockerfiles, Kubernetes manifests and Terraform, with a validation step and an explicit user approval gate before any production deployment.
Review scope
Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.
Observable capabilities
Assesses the application and environments, then designs the pipeline and deployment strategy.
Writes IaC, Dockerfiles and CI/CD configs, validating with terraform plan and linting.
Prepares a deployment summary and rollback command, and asks for explicit approval before production deploys.
Sets up observability and alerts and confirms the rollback procedure is ready.
Limitations & scope
Spans many tools; deep detail for GitLab CI, Terraform and incidents lives in separate references.
Examples such as the trivy-action@master reference and sample images are illustrative, not production-ready.
Not verified against any real cluster or pipeline in this review.
Relevant for
DevOps and platform engineers
Teams containerizing applications
On-call engineers writing runbooks
02 / STRUCTURE
What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
{
"name": "devops-engineer",
"description": "Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.",
"license": "MIT",
"metadata": {
"author": "https://github.com/Jeffallan",
"company": "https://synergetic.solutions",
"version": "1.2.0",
"domain": "devops",
"triggers": "DevOps, CI/CD, deployment, Docker, Kubernetes, Terraform, GitHub Actions, infrastructure, platform engineering, incident response, on-call, self-service",
"role": "engineer",
"scope": "implementation",
"output-format": "code",
"related-skills": "terraform-engineer, kubernetes-specialist, sre-engineer, monitoring-expert, security-reviewer"
}
}
03 / WORKFLOW
A reading of the operating sequence
This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.
01
Input
Assess
Understand the application, environments and requirements.
Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.
Attention recommended
71 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.
Network accessObserved
File writesObserved
Credential useObserved
Medium
Network access is mentioned
30 occurrences
A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 30 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 39 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Review every deploy, Terraform and kubectl command before it runs and never let it touch production without your explicit approval.
05 / CONTEXT
Where context can be spent
Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.
Exact token counts unavailable
All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.
No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.
06 / EVALUATION
Controlled evaluation
No controlled evaluation
This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.
Not tested
07 / USAGE
Use with the source in view
Install command
git clone https://github.com/Jeffallan/claude-skills.git
cd claude-skills
# Copy this skill directory into one of:
# ~/.claude/skills/devops-engineer
# .claude/skills/devops-engineer
Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/devops-engineer/SKILL.md.
Review the license, prerequisites and all bundled reference files.
Install the skill into a personal or project-level Claude Code skills directory.
Restart or refresh Claude Code so the skill can be discovered.
Verify installation
Confirm devops-engineer/SKILL.md exists at the destination, then ask Claude Code to use the devops-engineer skill on a small test task.
Prerequisites
Spans many tools; deep detail for GitLab CI, Terraform and incidents lives in separate references.
Examples such as the trivy-action@master reference and sample images are illustrative, not production-ready.
Not verified against any real cluster or pipeline in this review.
Example prompts
Representative task
Use the devops-engineer skill to containerize our Python service with a multi-stage Dockerfile, add a GitHub Actions CI pipeline that builds, tests and scans the image, and document a rollback procedure.
Inspect before use
Read the devops-engineer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/devops-engineer/SKILL.md and its referenced files. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.
08 / VERDICT
A decision, with its limits attached
Strengths
Requires explicit user approval and a blocked verdict if approval is withheld before production deployment.
Rules cover secret managers, health checks, resource limits and avoiding the latest tag.
Considerations
Broad scope means individual areas may need the dedicated terraform or kubernetes skills it lists as related.
Approval gates depend on the agent honoring them, so human oversight stays essential.
Research conclusion
A broad delivery-pipeline skill with a sensible production approval gate, suitable as a starting point rather than a turnkey solution.
09 / PROVENANCE
Traceable by construction
The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.
Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.