senior-devops
tessl i github:alirezarezvani/claude-skills --skill senior-devopsComprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill is a hollow template with no substantive DevOps content. It lists generic scripts without explaining what they actually do, provides no real code examples for CI/CD pipelines, Terraform modules, or Kubernetes deployments, and fills space with best practices Claude already knows. The skill fails to teach anything specific about DevOps automation.
Suggestions
Replace placeholder script descriptions with actual executable examples showing real pipeline YAML (GitHub Actions, CircleCI), Terraform HCL code, and Kubernetes manifests
Add concrete workflow examples with validation checkpoints, e.g., 'terraform plan -> review -> terraform apply -> verify deployment -> rollback if needed'
Remove generic best practices sections (Code Quality, Security, Maintainability) that Claude already knows and replace with DevOps-specific patterns and gotchas
Provide at least one complete, copy-paste-ready example for each core capability (e.g., a working GitHub Actions workflow, a basic Terraform module structure)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic placeholder content that adds no value. Descriptions like 'Automated tool for pipeline generator tasks' and 'Comprehensive analysis and optimization tool' are meaningless filler. Lists generic best practices Claude already knows (validate inputs, write tests, keep it simple). | 1 / 3 |
Actionability | No concrete, executable guidance. Script commands show generic placeholders like '[options]' and '[arguments]' without actual parameters. No real examples of pipeline configurations, Terraform code, or deployment manifests. Everything defers to reference files without providing any substantive content. | 1 / 3 |
Workflow Clarity | No clear multi-step workflows with validation checkpoints. The 'Development Workflow' section is generic setup steps without DevOps-specific sequencing. Missing critical validation steps for infrastructure changes, deployment verification, or rollback procedures. | 1 / 3 |
Progressive Disclosure | Structure exists with references to external files (references/*.md), but the main content is so devoid of substance that it's unclear what value the skill provides. The overview doesn't give enough actionable content to be useful on its own. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
92%This is a strong skill description that clearly articulates capabilities and includes explicit trigger guidance. The description covers a comprehensive DevOps domain with specific actions and natural keywords. The main weakness is its broad scope which could create conflicts with more specialized infrastructure, cloud, or container-focused skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'CI/CD', 'infrastructure automation', 'containerization', 'pipeline setup', 'infrastructure as code', 'deployment automation', and 'monitoring'. Uses third person voice appropriately. | 3 / 3 |
Completeness | Clearly answers both what (CI/CD, infrastructure automation, containerization, cloud platforms, pipeline setup, IaC, deployment automation, monitoring) AND when with explicit 'Use when...' clause covering multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CI/CD', 'pipelines', 'deploying applications', 'AWS', 'GCP', 'Azure', 'infrastructure', 'containerization', 'monitoring', 'deployment'. These are terms users naturally use when discussing DevOps tasks. | 3 / 3 |
Distinctiveness Conflict Risk | While DevOps is a clear domain, terms like 'deploying applications' and 'monitoring' could overlap with application-specific skills or observability tools. The broad scope (AWS, GCP, Azure, containers, pipelines) increases potential for conflicts with more specialized cloud or container skills. | 2 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.