senior-devops
Comprehensive 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.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly articulates what the skill does and when to use it, with good trigger term coverage across the DevOps domain. Its main weakness is the extremely broad scope, which could create conflicts with more specialized skills covering individual areas like AWS-specific infrastructure, Kubernetes/containerization, or monitoring. The description would benefit from either narrowing its scope or more explicitly delineating boundaries.
Suggestions
Consider narrowing the scope or adding boundary clarifications to reduce potential overlap with more specialized cloud, container, or monitoring skills (e.g., 'Use this for general DevOps workflows; for AWS-specific tasks, prefer the AWS skill').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: CI/CD, infrastructure automation, containerization, pipeline setup, infrastructure as code, deployment automation, monitoring, and names specific cloud platforms (AWS, GCP, Azure). | 3 / 3 |
Completeness | Clearly answers both what (CI/CD, infrastructure automation, containerization, cloud platforms, pipeline setup, IaC, deployment automation, monitoring) and when ('Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'CI/CD', 'pipelines', 'deploying applications', 'infrastructure', 'monitoring', 'AWS', 'GCP', 'Azure', 'containerization', 'deployment'. These are terms users naturally use when requesting DevOps help. | 3 / 3 |
Distinctiveness Conflict Risk | While it names specific DevOps domains and cloud platforms, the scope is extremely broad ('comprehensive DevOps skill') covering CI/CD, infrastructure, containers, monitoring, and three cloud providers. This breadth could overlap with more specialized skills for individual cloud platforms, container orchestration, or monitoring tools. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured DevOps skill with excellent actionability and workflow clarity. The executable examples (GitHub Actions, Terraform, Kubernetes) are production-quality and the development workflow sections include proper validation gates and rollback procedures. The main weakness is verbosity — the multi-cloud comparison, IaC tool selection guidance, and some explanatory text (e.g., Pulumi description, multi-cloud vs single-cloud decision criteria) are general knowledge that inflates the token budget without adding unique value.
Suggestions
Remove or drastically condense the 'Multi-Cloud Cross-References' decision guidance and 'Cloud-Agnostic IaC' tool comparison sections — Claude already knows when to use Terraform vs Pulumi vs CloudFormation. Keep only the cross-reference table to companion skills.
Move the IaC tool selection guidance to a reference file (e.g., references/iac_tool_selection.md) if it must be retained, and link to it with a one-line summary.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with some unnecessary content. The multi-cloud decision guidance, cloud-agnostic IaC comparison tables, and Pulumi/CloudFormation sections add bulk that Claude already knows. The core examples are well-chosen but the overall document could be significantly tightened. | 2 / 3 |
Actionability | The skill provides fully executable code examples throughout — complete GitHub Actions YAML, Terraform HCL modules, Kubernetes deployment manifests, and concrete CLI commands with real flags and arguments. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The Development Workflow section provides clear sequential steps with explicit validation checkpoints: terraform validate → plan → apply → verify, deploy → verify pods → switch traffic, and a dedicated rollback procedure with a health check verification and escalation path on failure. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to companion files (references/cicd_pipeline_guide.md, references/infrastructure_as_code.md, references/deployment_strategies.md) and cross-references to companion skills. Content is appropriately split between the overview and reference materials. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- alirezarezvani/claude-skills
- Commit
967fe01
- 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.