devops-engineer
DevOps specialist - CI/CD, deployment, infrastructure
56
Quality
43%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/devops-engineer/SKILL.mdQuality
Discovery
22%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 description is too brief and abstract to effectively guide skill selection. It reads more like a job title than a functional skill description, lacking concrete actions, explicit trigger guidance, and specific tooling references that would help Claude distinguish when to use this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about CI/CD pipelines, deployment automation, Docker, Kubernetes, or infrastructure as code'
Replace the vague 'DevOps specialist' label with concrete actions like 'Configures CI/CD pipelines, automates deployments, manages container orchestration, provisions cloud infrastructure'
Include specific tool names users would mention: Jenkins, GitHub Actions, GitLab CI, Docker, Kubernetes, Terraform, AWS, Azure, GCP
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('DevOps specialist') and lists only broad domain categories (CI/CD, deployment, infrastructure) without any concrete actions like 'configure pipelines', 'deploy containers', or 'provision servers'. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (DevOps topics) and completely lacks any 'when' guidance or 'Use when...' clause to help Claude know when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant domain keywords (CI/CD, deployment, infrastructure) that users might mention, but misses common variations and specific terms like 'pipeline', 'Docker', 'Kubernetes', 'AWS', 'terraform', 'Jenkins', 'GitHub Actions'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'DevOps' provides some domain specificity, the broad terms 'deployment' and 'infrastructure' could overlap with cloud-specific skills, container skills, or general system administration skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, executable DevOps configurations that are immediately usable. However, it lacks workflow guidance around validation, rollback procedures, and error recovery that are critical for production deployments. The persona framing adds no value and the content would benefit from progressive disclosure to separate detailed configurations.
Suggestions
Add validation and rollback steps: include commands to verify deployment success (e.g., kubectl rollout status) and how to rollback on failure
Remove the persona framing ('You are DevOps Engineer') and decorative tagline - they consume tokens without adding instructional value
Add a troubleshooting section or feedback loop for common deployment failures (image pull errors, health check failures, resource limits)
Consider splitting into overview + detailed reference files for each major topic (CI/CD, containers, K8s, monitoring)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient with concrete examples, but includes unnecessary persona framing ('You are DevOps Engineer') and a decorative tagline that don't add instructional value. The expertise list is somewhat redundant given the examples that follow. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready configurations for GitHub Actions, Dockerfile, Kubernetes deployment, and Prometheus. All examples are complete and production-ready with proper syntax. | 3 / 3 |
Workflow Clarity | The CI/CD pipeline shows a clear sequence (test -> build -> deploy), but lacks explicit validation checkpoints or error recovery guidance. No instructions on what to do if deployment fails, how to rollback, or how to verify successful deployment. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections (CI/CD, Docker, K8s, Monitoring), but everything is inline in one file. For this breadth of topics, references to separate detailed guides (e.g., KUBERNETES.md, MONITORING.md) would improve navigation and reduce cognitive load. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- TurnaboutHero/oh-my-antigravity
- Commit
fab464f
- 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.