devops-engineer
Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill devops-engineer77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger terms and distinctiveness, providing clear DevOps-specific keywords that would help Claude select this skill appropriately. However, it fails to describe what the skill actually does - it only describes when to use it, not the concrete actions or capabilities it provides. The description reads more like a trigger list than a capability description.
Suggestions
Add concrete actions at the beginning describing what the skill does, e.g., 'Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/CloudFormation templates.'
Restructure to lead with capabilities before the 'Use when...' clause to clearly answer 'what does this do' before 'when to use it'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD, containers, infrastructure) and mentions technologies (Docker, Kubernetes, GitOps), but lacks concrete actions - doesn't specify what it actually does with these technologies (e.g., 'write Dockerfiles', 'configure pipelines', 'deploy to clusters'). | 2 / 3 |
Completeness | Has a 'Use when...' clause addressing when to invoke, but the 'what does this do' portion is weak - it describes contexts/domains but not the actual capabilities or actions the skill performs. | 2 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'CI/CD pipelines', 'Docker', 'Kubernetes', 'cloud platforms', 'GitOps', 'containerizing applications', 'infrastructure as code' - these are all terms users naturally use when requesting DevOps help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear DevOps/infrastructure niche with distinct triggers like Docker, Kubernetes, CI/CD, and GitOps that are unlikely to conflict with other skill types like document processing or data analysis. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates excellent organization and token efficiency with a well-structured reference system for progressive disclosure. However, it lacks concrete executable examples (no actual Dockerfile, pipeline config, or Terraform snippets) and the workflow section needs explicit validation checkpoints for the destructive/deployment operations that are core to DevOps work.
Suggestions
Add at least one concrete, executable example for a common task (e.g., a minimal GitHub Actions workflow or Dockerfile snippet) to improve actionability
Include explicit validation checkpoints in the Core Workflow, such as 'Validate Terraform plan' before Deploy and 'Run smoke tests' after Deploy
Add a brief example of what a rollback procedure looks like, since it's mentioned in MUST DO but not demonstrated
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and bullet points effectively. No unnecessary explanations of concepts Claude already knows - it jumps straight to actionable guidance and references. | 3 / 3 |
Actionability | Provides clear constraints and workflow steps, but lacks concrete executable code examples. The 'Output Templates' section mentions what to provide but doesn't show actual examples of Dockerfiles, CI/CD configs, or K8s manifests. | 2 / 3 |
Workflow Clarity | The 5-step core workflow is clear but lacks validation checkpoints. For DevOps operations involving deployments and infrastructure changes, there should be explicit verification steps between stages (e.g., 'validate Terraform plan before apply'). | 2 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' guidance. Content is appropriately split with one-level-deep references to detailed topic files, making navigation easy and context-aware. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 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.