devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD 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.
87
84%
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 skill description that clearly articulates specific capabilities and provides explicit trigger guidance with both 'Use when' and 'Invoke for' clauses. The trigger term coverage is comprehensive, hitting many natural keywords a user would use. The main weakness is the very broad scope, which could cause conflicts with more specialized skills covering individual areas like Terraform, Kubernetes, or CI/CD specifically.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, generates Terraform/Pulumi templates, handles deployment automation, GitOps configuration, incident response runbooks, and developer platform tooling. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates Dockerfiles, configures CI/CD, writes K8s manifests, generates IaC templates, handles deployment automation) and 'when' with explicit 'Use when...' and 'Invoke for...' clauses listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, platform engineering, CI/CD, containerizing, infrastructure as code, cloud platforms, production incidents, automating releases. | 3 / 3 |
Distinctiveness Conflict Risk | While the DevOps/infrastructure niche is well-defined, the scope is very broad—covering CI/CD, Docker, Kubernetes, Terraform, incident response, and platform engineering could overlap with more specialized skills in any of those individual areas. The breadth increases conflict risk with narrower skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid DevOps skill with strong actionability through executable examples and good workflow clarity with explicit validation checkpoints. The progressive disclosure design is thoughtful but undermined by missing bundle files. Conciseness could be improved by trimming sections that restate obvious knowledge or duplicate the skill description.
Suggestions
Remove or significantly trim the 'When to Use This Skill' section since it duplicates the skill description metadata, and drop the 'Knowledge Reference' technology list which adds no value for Claude.
Provide the referenced bundle files (e.g., references/github-actions.md, references/docker-patterns.md) to make the progressive disclosure structure functional rather than aspirational.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the 'When to Use This Skill' section (which largely duplicates the description), the 'Role Definition' with hat metaphors, and the 'Knowledge Reference' list of technologies Claude already knows. The constraints section has some obvious items ('Deploy on Fridays without monitoring') that pad the content. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready examples: a complete GitHub Actions workflow, a multi-stage Dockerfile with best practices, and a rollback procedure with verification commands. The constraints are specific and actionable rather than vague. | 3 / 3 |
Workflow Clarity | The Core Workflow has a clear 6-step sequence with explicit validation checkpoints: 'Run terraform plan, lint configs, execute unit/integration tests; confirm no destructive changes before proceeding' at step 4, smoke tests at step 5, and rollback readiness confirmation at step 6. The rollback example includes a verification feedback loop. | 3 / 3 |
Progressive Disclosure | The reference table is well-structured with clear navigation signals and 'Load When' context, which is excellent design. However, no bundle files were provided, meaning all 8 referenced files (references/github-actions.md, etc.) are missing, so the progressive disclosure structure is aspirational rather than functional. The SKILL.md itself is well-organized with appropriate section splits. | 2 / 3 |
Total | 10 / 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
- Jeffallan/claude-skills
- Commit
5e8b6b8
- 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.