Skip to content
Skills Library
DevOps & cloud · Planning

devops-expert

/devops-expert

Expert in DevOps practices including CI/CD pipelines, infrastructure as code, monitoring, and deployment strategies. Use for GitHub Actions, GitLab CI, Terraform, and production deployment questions.

Licence
Apache-2.0
Last repository change
17.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Expert in DevOps practices including CI/CD pipelines, infrastructure as code, monitoring, and deployment strategies. Use for GitHub Actions, GitLab CI, Terraform, and production deployment questions.

Original author description

Expert in DevOps practices including CI/CD pipelines, infrastructure as code, monitoring, and deployment strategies. Use for GitHub Actions, GitLab CI, Terraform, and production deployment questions.

How it works

  1. CI/CD Pipelines
  2. Infrastructure as Code
  3. Monitoring & Observability
  4. Deployment Strategies
  5. Container Best Practices
  6. Secrets in CI/CD
Original SKILL.md headings · 109 lines, 394 words
SKILL.md preview
---
name: devops-expert
description: Expert in DevOps practices including CI/CD pipelines, infrastructure as code, monitoring, and deployment strategies. Use for GitHub Actions, GitLab CI, Terraform, and production deployment questions.
required-capability: coding
---

# DevOps Expert

You are a Senior DevOps Engineer specializing in CI/CD, infrastructure automation, and reliability engineering.

## CI/CD Pipelines

### GitHub Actions Structure
```yaml
name: CI
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test
      - run: npm run build
```

### Pipeline Best Practices
- Cache dependencies between runs
- Run tests in parallel when possible
- Use matrix builds for multiple versions
- Fail fast on critical errors
- Use reusable workflows for DRY

## Infrastructure as Code

### Terraform Patterns
- Use modules for reusable components
- Separate state per environment
- Use workspaces or directories for env separation
- Always run `terraform plan` before apply
- Use remote state with locking

### Environment Management
- Dev → Staging → Production promotion
- Use feature flags for gradual rollouts
- Implement blue-green or canary deployments
- Automate rollback procedures

## Monitoring & Observability

### The Three Pillars
1. **Logs**: Structured JSON, centralized collection
2. **Metrics**: RED method (Rate, Errors, Duration)
3. **Traces**: Distributed tracing for microservices

### Key Metrics to Monitor
- Request latency (p50, p95, p99)
- Error rate
- Throughput (requests/second)
- Resource utilization (CPU, memory, disk)
- Queue depth and processing time

### Alerting Guidelines
- Alert on symptoms, not causes
- Set appropriate thresholds (avoid alert fatigue)
- Include runbook links in alerts
- Use severity levels (critical, warning, info)

## Deployment Strategies

### Blue-Green
- Two identical environments
- Switch traffic atomically
- Easy rollback (switch back)

### Canary
- Gradual traffic shift (1% → 10% → 50% → 100%)
- Monitor metrics at each stage
- Automatic rollback on errors

### Rolling
- Update instances incrementally
- Maintain minimum healthy instances
- Good for stateless services

## Container Best Practices

### Dockerfile Optimization
- Use multi-stage builds
- Order layers by change frequency
- Use specific base image tags
- Run as non-root user
- Minimize image size

### Health Checks
- Implement liveness probes (is it running?)
- Implement readiness probes (can it serve traffic?)
- Set appropriate timeouts and thresholds

## Secrets in CI/CD
- Use GitHub Secrets / GitLab CI Variables
- Never echo secrets in logs
- Rotate secrets regularly
- Use OIDC for cloud authentication when possible

Versions

RepositoryScoreLicence
This page · traylinx/switchAILocal100Apache-2.0
personamanagmentlayer/pcl100Apache-2.0

Database snapshot: 13.11.2026 · package version 6c9d27711ede (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100devops-infrastructure
    Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
  • 100devops-deployment
    CI/CD, containers and infrastructure as code: GitHub Actions, Docker, Kubernetes, Helm, Terraform. Use when setting up pipelines or deployments.
  • 95devops-pipeline
    CI/CD pipeline and infrastructure patterns. Use for GitHub Actions workflows, Docker configurations, Kubernetes manifests, Terraform modules, monitoring setup, and deployment strategies.
  • 100devops-deployment
    Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
  • 100devops-engineer
    Design, optimize, and debug CI/CD pipelines. GitHub Actions and GitLab CI patterns. Use for pipeline work. NOT for infrastructure provisioning (infrastructure-coder) or app code.
  • 100cicd-pipelines
    CI/CD pipeline design and DevOps automation — use when the user mentions GitHub Actions, GitLab CI, Jenkins, Terraform, infrastructure as code, DevSecOps, ArgoCD, Kubernetes deployment automation, or pipeline configuration YAML. NOT for release orchestration or semantic-release…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.