Automated summary
This skill walks through containerizing applications, deploying to Kubernetes, building GitHub Actions CI/CD pipelines, and provisioning infrastructure with Terraform.
Strengths
- Ships a ready-to-use multi-stage Dockerfile with a non-root user and HEALTHCHECK
- Includes a full Kubernetes Deployment manifest with resource limits plus liveness and readiness probes
- Provides a three-stage GitHub Actions pipeline (test, build, deploy) that can be reused as-is
- Offers a decision tree for choosing between Docker Compose, Kubernetes and other targets
Limitations
- Examples are Python/FastAPI- and GitHub Actions-centric, so they need rework for other stacks
- Terraform provisioning and the observability stack are mentioned but no concrete example is given
- The SASMP config (retries, exit codes, logging hooks) is declarative rather than spelled out as executable steps
Use it when you need to create or harden a Dockerfile, write a Kubernetes manifest, or structure an end-to-end CI/CD pipeline.
Avoid it for provider-specific cloud consulting (AWS cost tuning, fine-grained IAM) or live production incident debugging, which the skill does not cover.
Security analysis
SafeThe skill provides standard DevOps guidance and examples (Dockerfile, Kubernetes manifests, GitHub Actions, troubleshooting commands). It does not instruct destructive, exfiltrating, obfuscated, or safety-disabling actions; kubectl/docker commands are ordinary and non-destructive.
No concerns found
How this analysis is madeExamples
Containerize my FastAPI application with Docker using a multi-stage build, a non-root user and a health check.Write a Kubernetes Deployment and Service for my api-server image with 3 replicas, resource limits and liveness/readiness probes.Set up a GitHub Actions CI/CD pipeline that runs pytest, builds and pushes a Docker image, then deploys to Kubernetes on main.name: devops description: Deploy applications with Docker and Kubernetes, automate with CI/CD, manage infrastructure with code, and configure cloud platforms and networking. sasmp_version: "2.0.0" bonded_agent: 06-devops-infrastructure bond_type: PRIMARY_BOND
=== PRODUCTION-GRADE SKILL CONFIG (SASMP v2.0.0) ===
atomic_operations:
- CONTAINERIZATION
- KUBERNETES_DEPLOYMENT
- CI_CD_PIPELINE
- INFRASTRUCTURE_PROVISIONING
parameter_validation: query: type: string required: true minLength: 5 maxLength: 2500 platform: type: string enum: [aws, gcp, azure, on-prem] required: false orchestrator: type: string enum: [kubernetes, docker-swarm, ecs] required: false
retry_logic: max_attempts: 3 backoff: exponential initial_delay_ms: 2000
logging_hooks: on_invoke: "skill.devops.invoked" on_success: "skill.devops.completed" on_error: "skill.devops.failed"
exit_codes: SUCCESS: 0 INVALID_INPUT: 1 DEPLOYMENT_FAILED: 2 SECURITY_ISSUE: 3
DevOps & Infrastructure Skill
Bonded to: devops-infrastructure-agent
Quick Start
# Invoke devops skill
"Containerize my Python application with Docker"
"Set up a CI/CD pipeline with GitHub Actions"
"Deploy my app to Kubernetes"
Instructions
- Containerize: Create optimized Docker images
- Orchestrate: Configure Kubernetes or Docker Swarm
- Automate: Set up CI/CD pipelines
- Provision: Deploy infrastructure with Terraform
- Monitor: Configure observability stack
Docker Best Practices
Optimized Dockerfile
# Multi-stage build for smaller images
FROM python:3.12-slim AS builder
WORKDIR /app
COPY requirements.txt .
RUN pip install --user --no-cache-dir -r requirements.txt
FROM python:3.12-slim
RUN useradd --create-home appuser
USER appuser
WORKDIR /app
COPY --from=builder /root/.local /home/appuser/.local
ENV PATH=/home/appuser/.local/bin:$PATH
COPY --chown=appuser:appuser . .
HEALTHCHECK --interval=30s --timeout=3s \
CMD curl -f http://localhost:8000/health || exit 1
EXPOSE 8000
CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8000"]
Image Checklist
- [ ] Use slim/alpine base images
- [ ] Multi-stage builds
- [ ] Non-root user
- [ ] Health checks
- [ ] .dockerignore file
Kubernetes Essentials
Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
name: api-server
spec:
replicas: 3
selector:
matchLabels:
app: api-server
template:
metadata:
labels:
app: api-server
spec:
containers:
- name: api-server
image: myapp:v1.0.0
ports:
- containerPort: 8000
resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "256Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /health
port: 8000
readinessProbe:
httpGet:
path: /ready
port: 8000
CI/CD Pipeline (GitHub Actions)
name: CI/CD
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: '3.12'
- run: pip install -r requirements.txt
- run: pytest --cov=app tests/
build:
needs: test
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: docker/build-push-action@v5
with:
push: true
tags: myregistry/myapp:${{ github.sha }}
deploy:
needs: build
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- run: kubectl set image deployment/api-server api-server=myregistry/myapp:${{ github.sha }}
Decision Tree
Deployment need?
│
├─→ Simple app → Docker Compose
│
├─→ Production, scaling needed
│ ├─→ Cloud-native → Kubernetes
│ └─→ AWS only → ECS
│
└─→ Serverless → AWS Lambda / Cloud Functions
Troubleshooting
Common Issues
| Issue | Cause | Solution |
|-------|-------|----------|
| Pod CrashLoopBackOff | App crash | Check logs: kubectl logs <pod> |
| ImagePullBackOff | Registry auth | Verify imagePullSecrets |
| OOMKilled | Memory limit | Increase limits or optimize |
| Pending pods | No resources | Scale cluster |
Debug Commands
# Pod status
kubectl get pods -o wide
# Pod logs
kubectl logs <pod> --previous
# Describe pod
kubectl describe pod <pod>
# Events
kubectl get events --sort-by='.lastTimestamp'
# Exec into pod
kubectl exec -it <pod> -- /bin/sh
Test Template
# tests/test_docker.py
import subprocess
class TestDockerBuild:
def test_dockerfile_builds_successfully(self):
result = subprocess.run(
["docker", "build", "-t", "test-image", "."],
capture_output=True, text=True
)
assert result.returncode == 0
def test_container_starts_and_healthy(self):
subprocess.run(["docker", "run", "-d", "--name", "test", "test-image"])
# Wait for health check
result = subprocess.run(
["docker", "inspect", "--format", "{{.State.Health.Status}}", "test"],
capture_output=True, text=True
)
assert "healthy" in result.stdout
Resources
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/devops-infrastructure-ms1aw5km/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/devops-infrastructure-ms1aw5km' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/devops-infrastructure-ms1aw5km/download' --output '.skill-downloads/devops-infrastructure-ms1aw5km/SKILL.md.part' && mv '.skill-downloads/devops-infrastructure-ms1aw5km/SKILL.md.part' '.skill-downloads/devops-infrastructure-ms1aw5km/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/devops-infrastructure-ms1aw5km/SKILL.md' && test -s '.skill-downloads/devops-infrastructure-ms1aw5km/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/devops' && cp -R '.skill-downloads/devops-infrastructure-ms1aw5km' '.claude/skills/devops'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/devops-infrastructure-ms1aw5km'openskills read 'devops-infrastructure-ms1aw5km'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/devops-infrastructure-ms1aw5km/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.