7K skills · sorted by relevance
Create CI/CD configurations, which automate build, test, and deployment steps, alongside Terraform infrastructure templates and Kubernetes deployment files. Generate health-check and rollback instructions to review before applying changes to cloud infrastructure or application environments.
Assess security weaknesses in CI/CD systems that automate software builds and delivery. Covering GitHub Actions, Jenkins, GitLab CI, and Azure DevOps, the skill examines unsafe inputs, excessive permissions, exposed credentials, and tampered build outputs, alongside detection and defensive controls.
DevOps 能力索引。Git、测试、DevSecOps、数据库。当用户提到 DevOps、CI/CD、Git、测试时路由到此。
The English summary is being prepared. Showing the original description.
Operate a live AWS workload with AWS DevOps Agent — incident investigation, root-cause analysis, and release-readiness review — for startups with no dedicated DevOps or SRE engineer. Use when a live AWS workload is misbehaving (production is down, 5xx errors, latency spike, timeouts, it broke after the last deploy, an alarm fired, a pasted CloudWatch alarm or stack trace, find the root cause, write a postmortem, no one on call), for pre-merge review (is this PR safe to ship, blast radius), or to set up, pause, stop, or check the cost of AWS DevOps Agent. Detects existing setup first and never re-onboards. Cost, account access, and code egress are each disclosed in one line with safe defaults: cost and access proceed, code egress stays off unless asked. Do not use for: new architecture (architect-for-startups), scaffolding (start-building-for-startups), migrations (gcp-to-aws, azure-to-aws, heroku-to-aws, llm-to-bedrock), or general Activate and credits questions (knowledge-base-for-startups).
The English summary is being prepared. Showing the original description.
Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch policies, PR checks/status, CodeQL/security scans, or Azure DevOps integrations, and other Azure Repos related development tasks. Not for Azure DevOps (use azure-devops), Azure Pipelines (use azure-pipelines), Azure Boards (use azure-boards), Azure Artifacts (use azure-artifacts).
The English summary is being prepared. Showing the original description.
Azure DevOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure DevOps data.
The English summary is being prepared. Showing the original description.
Use when adding, removing, or updating a local organizer on a devopsdays event team - covers the team_members entry, the photo, and the mandatory email to info@devopsdays.org that gates the merge.
The English summary is being prepared. Showing the original description.
软件架构 (含 应用架构 / 系统架构 / 分布式 后端架构 / 前后端 数据流 与 数据模型 设计 / API 边界 / 可扩展性 / 演进式架构 — 不含 硬件架构 / 纯企业架构 / 纯 DevOps / 纯安全架构) (software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).) Master OS — automated mastery of software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on software architecture — application & system architecture for web / mobile / distributed back-ends; designing services + data models + data flow + integration boundaries; making explicit trade-offs about scalability / coupling / consistency / evolvability; not hardware / chip architecture, not pure enterprise-architecture (TOGAF/Zachman), not pure DevOps / SRE, not pure security architecture (those are adjacent disciplines). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「软件架构」「系统设计」「system design」「应用架构」「service design」
The English summary is being prepared. Showing the original description.
Azure DevOps migration to GitHub Actions — syntax mappings and the migration report template for YAML pipelines, templates, variable groups, service connections, deployment jobs, stages, conditional logic. Load with `migration-core` when migrating Azure DevOps sources to GitHub Actions.
The English summary is being prepared. Showing the original description.
DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.
The English summary is being prepared. Showing the original description.
DevOps & Infrastructure IA — Gère le VPS, Docker, déploiements, monitoring, sécurité, tunnels Cloudflare. Expert Hetzner + Coolify + self-hosting.
The English summary is being prepared. Showing the original description.
DevOps infra v2 — VPS, Docker, Coolify, CI/CD, monitoring, Tailscale
The English summary is being prepared. Showing the original description.
Product-fleet ops desk (Busabase App-in-Skill) for uptime/service health, SSL certificate expiry, domain renewal, API key rotation, cloud spend anomalies, and a review queue of agent-proposed action cards. Use when the user invokes $kelly-devops or /kelly-devops, or asks about uptime, service health checks, SSL certificate expiry, domain renewal, domain expiry, API key rotation, token rotation reminders, cloud spend anomaly, billing spikes, ops desk, incident review, or reviewing agent-proposed action cards (renew domain, rotate key, investigate spend, restart service, acknowledge incident).
The English summary is being prepared. Showing the original description.
Cria e mantém o inventário da plataforma — contas AWS, clusters, ambientes, bancos, hosts e o mapeamento que distingue produção de staging. Use quando o usuário disser "configurar devops", "mapear a infra", "qual o ambiente", "cadastrar cluster", ou quando qualquer skill não encontrar .claude/pwdev-devops-context.md. Fundação: sem este arquivo, o plugin não sabe o que é produção — e trata tudo como produção.
The English summary is being prepared. Showing the original description.
Design and review infrastructure and release workflows with checks tailored to the environment. Covers automated build and deployment pipelines, containers, health checks, rollback plans, feature flags, and mobile releases to help assess readiness before deployment.
Create rollout plans for application and infrastructure changes. Organize readiness checks, deployment steps, health indicators, rollback procedures, and stakeholder communications, adapting the detail to the target environment, change type, and level of risk.
Organize responses to service outages and degraded performance, from initial assessment through recovery review. Classify severity, reconstruct event timelines, draft stakeholder updates, and create response guides and follow-up actions based on incident findings.
Find the engineering specialist skill that matches a task, from system design and frontend development to testing, security, and AI. This index explains each area of focus and directs agents to load the relevant skill’s instructions.
Create Dockerfiles, automated build and deployment pipelines, Kubernetes configurations, and infrastructure templates. The skill also prepares deployment checks, rollback procedures, and incident response runbooks to support application releases and production operations.
Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and synthesize, or compare findings across accounts. Use whenever the user has more than one AgentSpace configured, mentions multiple AWS accounts, or asks something like "check both prod and staging", "compare across accounts", or "ask the knowledge space".
The English summary is being prepared. Showing the original description.
Run a deep root-cause investigation on the AWS DevOps Agent. Use when the user describes an incident, alarm, outage, or unexplained behavior — keywords like "5xx", "503", "OOM", "latency spike", "deployment failure", "rollback", "sev1", "investigate", "root cause", "debug", "alarm fired", "service down". Polls and streams progress, then surfaces recommendations.
The English summary is being prepared. Showing the original description.
Have a fast, conversational analysis with the AWS DevOps Agent. Use for cost optimization, architecture review, topology mapping, knowledge / runbook discovery, security audits, dependency questions, and quick diagnostics — anything that needs a 5-30 second answer rather than a 5-8 minute deep investigation. Trigger words include cost, optimize, review, architecture, topology, what runbooks, show me, compare, audit, what if.
The English summary is being prepared. Showing the original description.
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use PROACTIVELY for debugging, incident response, or system troubleshooting.
The English summary is being prepared. Showing the original description.
Drafts or opens a GitHub pull request, runs changed-area preflight checks, and commits validated preflight repairs, and routes Azure DevOps repositories to the backlog-management pull request protocol. Use when a user asks to prepare, create, or update a pull request on GitHub or Azure DevOps.
The English summary is being prepared. Showing the original description.