devops-engineer_skill

This skill helps you design, implement, and automate CI/CD pipelines, containerization, and infrastructure across cloud environments with best practices.
  • HTML

22

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill nahisaho/musubi --skill devops-engineer

  • ci-cd-templates.md9.3 KB
  • SKILL.md22.7 KB

Overview

This skill is a DevOps Engineer copilot that guides CI/CD pipeline design, infrastructure automation, containerization, and deployment orchestration. It helps build GitHub Actions/GitLab CI workflows, Docker images, Kubernetes manifests, Terraform/Ansible infrastructure, and monitoring stacks. The goal is faster, reliable deployments and repeatable operational processes.

How this skill works

I inspect the project's tech stack, current deployment flow, and repository layout to recommend concrete pipeline and IaC artifacts. I can generate YAML workflows, Dockerfiles, Kubernetes manifests, Helm charts, Terraform modules, and monitoring configurations (Prometheus/Grafana/Loki). I produce stepwise deliverables, verify prerequisites, and provide commands and rollbacks for safe operations.

When to use it

  • When you want a repeatable CI/CD pipeline (GitHub Actions, GitLab CI, Jenkins).
  • When containerizing an app or optimizing Dockerfile and image strategy.
  • When deploying to Kubernetes and needing manifests, ingress, or Helm charts.
  • When automating cloud infrastructure with Terraform or config management with Ansible.
  • When setting up monitoring, alerting, and log aggregation for production.

Best practices

  • Design pipelines in stages: build → test → security scan → image build → deploy.
  • Use multi-stage Docker builds and small base images to reduce attack surface and size.
  • Keep secrets out of repos: use CI/CD secrets and Kubernetes Secrets or Vault.
  • Prefer declarative IaC modules and versioned Helm charts for predictable deployments.
  • Add health, readiness, and resource probes; enforce resource requests/limits.
  • Implement progressive deployment strategies (canary/rolling/blue-green) and automated smoke tests.

Example use cases

  • Create a GitHub Actions workflow that builds, tests, scans, builds a Docker image, and deploys to staging and production clusters.
  • Convert a legacy VM deployment into Terraform-managed infrastructure with automated CI-driven provisioning.
  • Write Kubernetes deployment, service, and ingress manifests with liveness/readiness probes and resource tuning.
  • Generate Prometheus scrape configs, Grafana dashboards, and alert rules for key app metrics.
  • Build a Dockerfile with multi-stage build and caching, plus CI cache layers for fast image builds.

FAQ

Use rolling updates for simplicity, canary or blue-green for lower risk. Combine with automated smoke tests and metrics-based promotion.

How do you handle secrets and credentials?

Keep secrets in CI/CD secret stores or a secrets manager (Vault, cloud KMS). Inject into runtime via Kubernetes Secrets or environment variables with restricted access.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational