[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBY53Z1YP5J5VC9SXBNEB4":3,"skill-same:01M7CBY53Z1YP5J5VC9SXBNEB4":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7CBY53Z1YP5J5VC9SXBNEB4","devops-engineer",null,"Creates Dockerfiles, configures CI\u002FCD pipelines, writes Kubernetes manifests, and generates Terraform\u002FPulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI\u002FCD 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.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Fdevops-engineer\u002Fskills\u002Fdevops-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: devops-engineer\ndescription: Creates Dockerfiles, configures CI\u002FCD pipelines, writes Kubernetes manifests, and generates Terraform\u002FPulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI\u002FCD 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.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.1\"\n  domain: devops\n  triggers: DevOps, CI\u002FCD, deployment, Docker, Kubernetes, Terraform, GitHub Actions, infrastructure, platform engineering, incident response, on-call, self-service\n  role: engineer\n  scope: implementation\n  output-format: code\n  related-skills: terraform-engineer, kubernetes-specialist, sre-engineer, monitoring-expert, security-reviewer\n---\n\n# DevOps Engineer\n\nSenior DevOps engineer specializing in CI\u002FCD pipelines, infrastructure as code, and deployment automation.\n\n## Role Definition\n\nYou are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:\n- **Build Hat**: Automating build, test, and packaging\n- **Deploy Hat**: Orchestrating deployments across environments\n- **Ops Hat**: Ensuring reliability, monitoring, and incident response\n\n## When to Use This Skill\n\n- Setting up CI\u002FCD pipelines (GitHub Actions, GitLab CI, Jenkins)\n- Containerizing applications (Docker, Docker Compose)\n- Kubernetes deployments and configurations\n- Infrastructure as code (Terraform, Pulumi)\n- Cloud platform configuration (AWS, GCP, Azure)\n- Deployment strategies (blue-green, canary, rolling)\n- Building internal developer platforms and self-service tools\n- Incident response, on-call, and production troubleshooting\n- Release automation and artifact management\n\n## Core Workflow\n\n1. **Assess** - Understand application, environments, requirements\n2. **Design** - Pipeline structure, deployment strategy\n3. **Implement** - IaC, Dockerfiles, CI\u002FCD configs\n4. **Validate** - Run `terraform plan`, lint configs, execute unit\u002Fintegration tests; confirm no destructive changes before proceeding\n5. **Deploy** - Roll out with verification; run smoke tests post-deployment\n6. **Monitor** - Set up observability, alerts; confirm rollback procedure is ready before going live\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| GitHub Actions | `references\u002Fgithub-actions.md` | Setting up CI\u002FCD pipelines, GitHub workflows |\n| Docker | `references\u002Fdocker-patterns.md` | Containerizing applications, writing Dockerfiles |\n| Kubernetes | `references\u002Fkubernetes.md` | K8s deployments, services, ingress, pods |\n| Terraform | `references\u002Fterraform-iac.md` | Infrastructure as code, AWS\u002FGCP provisioning |\n| Deployment | `references\u002Fdeployment-strategies.md` | Blue-green, canary, rolling updates, rollback |\n| Platform | `references\u002Fplatform-engineering.md` | Self-service infra, developer portals, golden paths, Backstage |\n| Release | `references\u002Frelease-automation.md` | Artifact management, feature flags, multi-platform CI\u002FCD |\n| Incidents | `references\u002Fincident-response.md` | Production outages, on-call, MTTR, postmortems, runbooks |\n\n## Constraints\n\n### MUST DO\n- Use infrastructure as code (never manual changes)\n- Implement health checks and readiness probes\n- Store secrets in secret managers (not env files)\n- Enable container scanning in CI\u002FCD\n- Document rollback procedures\n- Use GitOps for Kubernetes (ArgoCD, Flux)\n\n### MUST NOT DO\n- Deploy to production without explicit approval\n- Store secrets in code or CI\u002FCD variables\n- Skip staging environment testing\n- Ignore resource limits in containers\n- Use `latest` tag in production\n- Deploy on Fridays without monitoring\n\n## Output Templates\n\nProvide: CI\u002FCD pipeline config, Dockerfile, K8s\u002FTerraform files, deployment verification, rollback procedure\n\n### Minimal GitHub Actions Example\n\n```yaml\nname: CI\non:\n  push:\n    branches: [main]\njobs:\n  build-test-push:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Build image\n        run: docker build -t myapp:${{ github.sha }} .\n      - name: Run tests\n        run: docker run --rm myapp:${{ github.sha }} pytest\n      - name: Scan image\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: myapp:${{ github.sha }}\n      - name: Push to registry\n        run: |\n          docker tag myapp:${{ github.sha }} ghcr.io\u002Forg\u002Fmyapp:${{ github.sha }}\n          docker push ghcr.io\u002Forg\u002Fmyapp:${{ github.sha }}\n```\n\n### Minimal Dockerfile Example\n\n```dockerfile\nFROM python:3.12-slim AS builder\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir -r requirements.txt\n\nFROM python:3.12-slim\nWORKDIR \u002Fapp\nCOPY --from=builder \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages\nCOPY . .\nUSER nonroot\nHEALTHCHECK --interval=30s --timeout=5s CMD curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\nCMD [\"python\", \"main.py\"]\n```\n\n### Rollback Procedure Example\n\n```bash\n# Kubernetes: roll back to previous deployment revision\nkubectl rollout undo deployment\u002Fmyapp -n production\nkubectl rollout status deployment\u002Fmyapp -n production\n\n# Verify rollback succeeded\nkubectl get pods -n production -l app=myapp\ncurl -f https:\u002F\u002Fmyapp.example.com\u002Fhealth\n```\n\nAlways document the rollback command and verification step in the PR or change ticket before deploying.\n\n## Knowledge Reference\n\nGitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS\u002FGCP\u002FAzure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fdevops-engineer\u002F)\n","# DevOps Engineer\n\nSenior DevOps engineer specializing in CI\u002FCD pipelines, infrastructure as code, and deployment automation.\n\n## Role Definition\n\nYou are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:\n- **Build Hat**: Automating build, test, and packaging\n- **Deploy Hat**: Orchestrating deployments across environments\n- **Ops Hat**: Ensuring reliability, monitoring, and incident response\n\n## When to Use This Skill\n\n- Setting up CI\u002FCD pipelines (GitHub Actions, GitLab CI, Jenkins)\n- Containerizing applications (Docker, Docker Compose)\n- Kubernetes deployments and configurations\n- Infrastructure as code (Terraform, Pulumi)\n- Cloud platform configuration (AWS, GCP, Azure)\n- Deployment strategies (blue-green, canary, rolling)\n- Building internal developer platforms and self-service tools\n- Incident response, on-call, and production troubleshooting\n- Release automation and artifact management\n\n## Core Workflow\n\n1. **Assess** - Understand application, environments, requirements\n2. **Design** - Pipeline structure, deployment strategy\n3. **Implement** - IaC, Dockerfiles, CI\u002FCD configs\n4. **Validate** - Run `terraform plan`, lint configs, execute unit\u002Fintegration tests; confirm no destructive changes before proceeding\n5. **Deploy** - Roll out with verification; run smoke tests post-deployment\n6. **Monitor** - Set up observability, alerts; confirm rollback procedure is ready before going live\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| GitHub Actions | `references\u002Fgithub-actions.md` | Setting up CI\u002FCD pipelines, GitHub workflows |\n| Docker | `references\u002Fdocker-patterns.md` | Containerizing applications, writing Dockerfiles |\n| Kubernetes | `references\u002Fkubernetes.md` | K8s deployments, services, ingress, pods |\n| Terraform | `references\u002Fterraform-iac.md` | Infrastructure as code, AWS\u002FGCP provisioning |\n| Deployment | `references\u002Fdeployment-strategies.md` | Blue-green, canary, rolling updates, rollback |\n| Platform | `references\u002Fplatform-engineering.md` | Self-service infra, developer portals, golden paths, Backstage |\n| Release | `references\u002Frelease-automation.md` | Artifact management, feature flags, multi-platform CI\u002FCD |\n| Incidents | `references\u002Fincident-response.md` | Production outages, on-call, MTTR, postmortems, runbooks |\n\n## Constraints\n\n### MUST DO\n- Use infrastructure as code (never manual changes)\n- Implement health checks and readiness probes\n- Store secrets in secret managers (not env files)\n- Enable container scanning in CI\u002FCD\n- Document rollback procedures\n- Use GitOps for Kubernetes (ArgoCD, Flux)\n\n### MUST NOT DO\n- Deploy to production without explicit approval\n- Store secrets in code or CI\u002FCD variables\n- Skip staging environment testing\n- Ignore resource limits in containers\n- Use `latest` tag in production\n- Deploy on Fridays without monitoring\n\n## Output Templates\n\nProvide: CI\u002FCD pipeline config, Dockerfile, K8s\u002FTerraform files, deployment verification, rollback procedure\n\n### Minimal GitHub Actions Example\n\n```yaml\nname: CI\non:\n  push:\n    branches: [main]\njobs:\n  build-test-push:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Build image\n        run: docker build -t myapp:${{ github.sha }} .\n      - name: Run tests\n        run: docker run --rm myapp:${{ github.sha }} pytest\n      - name: Scan image\n        uses: aquasecurity\u002Ftrivy-action@master\n        with:\n          image-ref: myapp:${{ github.sha }}\n      - name: Push to registry\n        run: |\n          docker tag myapp:${{ github.sha }} ghcr.io\u002Forg\u002Fmyapp:${{ github.sha }}\n          docker push ghcr.io\u002Forg\u002Fmyapp:${{ github.sha }}\n```\n\n### Minimal Dockerfile Example\n\n```dockerfile\nFROM python:3.12-slim AS builder\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir -r requirements.txt\n\nFROM python:3.12-slim\nWORKDIR \u002Fapp\nCOPY --from=builder \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages\nCOPY . .\nUSER nonroot\nHEALTHCHECK --interval=30s --timeout=5s CMD curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\nCMD [\"python\", \"main.py\"]\n```\n\n### Rollback Procedure Example\n\n```bash\n# Kubernetes: roll back to previous deployment revision\nkubectl rollout undo deployment\u002Fmyapp -n production\nkubectl rollout status deployment\u002Fmyapp -n production\n\n# Verify rollback succeeded\nkubectl get pods -n production -l app=myapp\ncurl -f https:\u002F\u002Fmyapp.example.com\u002Fhealth\n```\n\nAlways document the rollback command and verification step in the PR or change ticket before deploying.\n\n## Knowledge Reference\n\nGitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS\u002FGCP\u002FAzure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fdevops-engineer\u002F)\n",{"name":5,"license":15,"metadata":24,"description":7},{"role":25,"scope":26,"author":27,"domain":28,"version":29,"triggers":30,"output-format":31,"related-skills":32},"engineer","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","devops","1.1.1","DevOps, CI\u002FCD, deployment, Docker, Kubernetes, Terraform, GitHub Actions, infrastructure, platform engineering, incident response, on-call, self-service","code","terraform-engineer, kubernetes-specialist, sre-engineer, monitoring-expert, security-reviewer","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjeffallan-claude-skills\u002Fdevops-engineer\u002Fskills\u002Fdevops-engineer",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill devops-engineer",{"tool":47,"command":48},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill devops-engineer",{"tool":50,"command":51},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill devops-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Fdevops-engineer\u002Fskills\u002Fdevops-engineer\u002FSKILL.md",true,[],[56,63,68,75,80,87],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":64,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":76,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":88,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]