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 well-structured description that clearly states capabilities and includes an explicit 'Use when...' clause with natural trigger terms. Its main weakness is its extreme breadth—covering nearly all of DevOps—which could cause conflicts with more specialized skills in overlapping areas like cloud platforms, containerization, or monitoring. The description would benefit from either narrowing scope or adding distinguishing details about what makes it the right choice over more specialized alternatives.
Suggestions
Consider narrowing the scope or clarifying boundaries—e.g., specify this is for general DevOps orchestration rather than deep platform-specific work, to reduce overlap with specialized AWS/GCP/Azure or Kubernetes skills.
Add differentiating language like 'Use this skill for cross-cutting DevOps workflows; for platform-specific deep dives, prefer dedicated skills' to help Claude disambiguate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: CI/CD, infrastructure automation, containerization, pipeline setup, infrastructure as code, deployment automation, and monitoring. These are distinct, identifiable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (CI/CD, infrastructure automation, containerization, cloud platforms, pipeline setup, IaC, deployment automation, monitoring) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'CI/CD', 'pipelines', 'deploying applications', 'infrastructure', 'monitoring', 'AWS', 'GCP', 'Azure', 'containerization', 'infrastructure as code'. Good coverage of terms a user would naturally use when needing DevOps help. | 3 / 3 |
Distinctiveness Conflict Risk | While DevOps is a recognizable domain, the description is extremely broad—covering CI/CD, infrastructure, containerization, cloud platforms, monitoring, and deployment. This breadth could overlap with more specialized skills for AWS, Docker/Kubernetes, monitoring tools, or individual CI/CD platforms. The scope is so wide it risks conflicting with narrower skills in any of these sub-domains. | 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 well-structured DevOps skill with excellent actionability and workflow clarity, featuring production-ready code examples and clear validation checkpoints throughout. The progressive disclosure is well-handled with appropriate references to companion files. The main weakness is verbosity — the multi-cloud decision guidance, IaC tool comparison tables, and explanatory content about when to use various tools could be moved to reference files, as much of this is general knowledge Claude already possesses.
Suggestions
Move the 'Multi-Cloud Cross-References' and 'Cloud-Agnostic IaC' sections to a reference file (e.g., references/cloud_strategy.md) and replace with a brief pointer, as this advisory content inflates the main skill without adding actionable instructions.
Trim explanatory prose like 'Terraform (or its open-source fork OpenTofu) is the recommended IaC tool for most teams' and the bullet-point rationales — Claude knows what these tools are and can infer recommendations from the examples provided.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~200+ lines) with some unnecessary explanations Claude already knows (e.g., multi-cloud vs single-cloud decision rationale, when to use Pulumi vs Terraform, what Terraform is). The IaC comparison tables and multi-cloud guidance add bulk that could be in reference files. However, the code examples themselves are lean and relevant. | 2 / 3 |
Actionability | The skill provides fully executable code examples across multiple domains: complete GitHub Actions YAML, production-ready Terraform HCL, Kubernetes deployment manifests, and concrete CLI commands with real flags and arguments. All examples are copy-paste ready with realistic configurations. | 3 / 3 |
Workflow Clarity | The Development Workflow section provides clear sequential steps with explicit validation checkpoints: terraform validate → plan → apply → verify, deploy with health-check gate → verify pods → switch traffic, and a dedicated rollback procedure with verification. The feedback loop pattern (validate, check health, rollback on failure) is well-established throughout. | 3 / 3 |
Progressive Disclosure | The skill has a clear Quick Start section, well-organized core capabilities, and appropriately references detailed content in separate files (references/cicd_pipeline_guide.md, references/infrastructure_as_code.md, references/deployment_strategies.md). Cross-references to companion skills are clearly signaled in a table. All references are one level deep. | 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
a96cc20
- 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.