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.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that thoroughly covers the DevOps and platform engineering domain. It lists specific concrete actions, provides comprehensive trigger terms that users would naturally use, explicitly states both what the skill does and when to invoke it, and occupies a clearly distinct niche. The description is well-structured and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates Dockerfiles', 'configures CI/CD pipelines', 'writes Kubernetes manifests', 'generates Terraform/Pulumi infrastructure templates', 'deployment automation', 'GitOps configuration', 'incident response runbooks', and 'internal developer platform tooling'. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates Dockerfiles, configures CI/CD, writes K8s manifests, generates IaC templates, handles deployment automation, etc.) 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'. These are all terms users would naturally use when requesting DevOps/infrastructure help. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear DevOps/infrastructure/platform engineering niche with highly distinct trigger terms like 'Dockerfiles', 'Kubernetes manifests', 'Terraform', 'GitOps', 'on-call', and 'incident response runbooks'. Unlikely to conflict with general coding or document-processing skills. | 3 / 3 |
Total | 12 / 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 strong actionability through executable examples and excellent progressive disclosure via the reference table. The main weaknesses are some unnecessary verbosity in the role definition, 'When to Use' section (which duplicates the skill description), and the bare knowledge reference list at the end. The workflow and validation checkpoints are well-designed for the destructive/deployment operations this skill covers.
Suggestions
Remove or significantly trim the 'Role Definition' and 'When to Use This Skill' sections, as they largely duplicate the skill description metadata and explain things Claude already knows.
Remove the 'Knowledge Reference' list at the end—it's just tool names with no actionable content and wastes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Role Definition' section with 'hats' metaphor and 'When to Use This Skill' section largely restate what Claude already knows or what's in the frontmatter description. The 'Knowledge Reference' list at the end is just a list of tool names adding no value. However, the examples and constraints sections are reasonably tight. | 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 section gives specific, concrete rules rather than vague guidance. | 3 / 3 |
Workflow Clarity | The Core Workflow has a clear 6-step sequence with explicit validation checkpoints (terraform plan, lint, tests at step 4), post-deployment verification (smoke tests at step 5), and a rollback readiness check before going live (step 6). The rollback procedure example includes a verification feedback loop. Destructive operations are gated by approval and validation. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table with 8 clearly signaled, one-level-deep references with specific 'Load When' conditions. The main skill provides a concise overview with minimal examples while pointing to detailed topic-specific files for deeper guidance. | 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
- jeffallan/claude-skills
- Commit
3d95bb1
- 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.