devops-automator
Expert DevOps engineer specializing in infrastructure automation, CI/CD pipeline development, and cloud operations
31
14%
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 ./devops-automator/skills/SKILL.mdQuality
Discovery
14%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 reads like a job title or resume summary rather than a functional skill description. It lacks concrete actions, explicit trigger conditions, and specific tooling references. It would be very difficult for Claude to reliably select this skill over others in a large skill library due to its vagueness and broad scope.
Suggestions
Replace the persona-style description with specific concrete actions, e.g., 'Writes Terraform/OpenTofu configurations, creates CI/CD pipelines (GitHub Actions, GitLab CI), configures Docker/Kubernetes deployments, manages cloud infrastructure on AWS/GCP/Azure.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about deploying applications, writing pipeline YAML, configuring infrastructure as code, Docker containers, Kubernetes manifests, or cloud resource provisioning.'
Use third-person action verbs instead of a persona description — 'Generates and debugs CI/CD pipeline configurations' rather than 'Expert DevOps engineer specializing in...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, resume-like language ('specializing in', 'infrastructure automation', 'CI/CD pipeline development', 'cloud operations') without listing any concrete actions. It describes a persona rather than specific capabilities like 'write Terraform configs, create GitHub Actions workflows, configure Docker containers'. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (infrastructure automation, CI/CD, cloud ops) and completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, which per the rubric should cap completeness at 2, but the 'what' is also weak, so it scores 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant domain keywords like 'CI/CD', 'infrastructure automation', and 'cloud operations' that users might mention, but misses common specific terms like 'Terraform', 'Docker', 'Kubernetes', 'AWS', 'deploy', 'pipeline', 'YAML', etc. The terms are broad categories rather than natural user language. | 2 / 3 |
Distinctiveness Conflict Risk | The description is extremely broad — 'infrastructure automation', 'CI/CD pipeline development', and 'cloud operations' could overlap with numerous other skills covering Docker, Kubernetes, Terraform, AWS, GitHub Actions, or any cloud-related tooling. There are no distinct triggers to differentiate it. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a high-level role description or persona prompt rather than an actionable skill file. It tells Claude what a DevOps engineer does conceptually but provides zero concrete guidance—no code, no commands, no configuration examples, no validation steps. Claude already knows what Terraform, Kubernetes, and CI/CD pipelines are; the skill needs to add specific, executable patterns and workflows that Claude wouldn't otherwise produce.
Suggestions
Replace abstract bullet points with concrete, executable examples—e.g., a sample Terraform module, a GitHub Actions workflow YAML, a Kubernetes deployment manifest with health checks and rollback annotations.
Add explicit validation checkpoints to the workflow—e.g., 'Run `terraform plan` and review diff before applying,' 'Verify health check endpoint returns 200 after deploy, rollback if not.'
Remove capability and tool listings that merely name technologies Claude already knows; instead, document specific patterns, conventions, or project-specific configurations that add novel information.
Structure content with progressive disclosure: keep a concise quick-start in SKILL.md and link to separate files for detailed IaC patterns, CI/CD templates, observability setup, and incident response runbooks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but reads more like a role description or persona definition than a skill file. It lists capabilities and tools Claude already knows about without adding novel, specific guidance. Phrases like 'reduce deployment risk' and 'without manual heroics' are filler. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, configuration snippets, or executable examples. Every section is abstract and descriptive—'Standardize infrastructure definitions,' 'Instrument logs, metrics, traces'—without showing how to actually do any of it. There is nothing copy-paste ready or directly executable. | 1 / 3 |
Workflow Clarity | The workflow is a high-level sequence of abstract steps with no validation checkpoints, no feedback loops, and no concrete commands. For a skill covering destructive/batch operations like infrastructure automation and deployments, the absence of any verification or rollback validation steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic list of bullet points with no references to external files, no links to detailed guides, and no layered structure. Everything is at the same shallow level of abstraction with no way to drill deeper into any topic. | 1 / 3 |
Total | 5 / 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
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.