operate
Infrastructure as code, CI/CD pipelines, containerization, observability, environment management. Read what exists before proposing change; preview blast radius before applying; never modify live infrastructure silently.
40
41%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./deliver/skills/operate/SKILL.mdQuality
Discovery
32%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 identifies a clear DevOps/infrastructure domain and includes useful operational guardrails (read before changing, preview blast radius), which is a nice touch. However, it lacks specific concrete actions, misses common tool-specific trigger terms users would naturally use, and critically omits any 'Use when...' guidance for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about deploying services, writing Terraform/CloudFormation configs, setting up CI/CD pipelines, Docker/Kubernetes configuration, or monitoring infrastructure.'
Replace broad category names with specific actions, e.g., 'Writes Terraform and CloudFormation configs, builds Dockerfiles, configures CI/CD pipelines (GitHub Actions, GitLab CI), sets up monitoring and alerting.'
Include common tool names and file extensions as trigger terms: Terraform, Docker, Kubernetes, Helm, GitHub Actions, .tf, Dockerfile, docker-compose.yml, etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DevOps/infrastructure) and lists several areas (IaC, CI/CD, containerization, observability, environment management), but these are broad categories rather than specific concrete actions. The second sentence adds operational constraints but not specific capabilities like 'write Terraform configs' or 'build Docker images'. | 2 / 3 |
Completeness | Describes 'what' at a high level (infrastructure/DevOps topics) and includes operational guardrails, but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also fairly vague, bringing this to 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'infrastructure as code', 'CI/CD pipelines', 'containerization', 'observability', and 'environment management' that users might mention. However, it misses common natural variations like 'Terraform', 'Docker', 'Kubernetes', 'deploy', 'monitoring', 'Helm', 'GitHub Actions', '.yml', 'pipeline', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of IaC, CI/CD, containerization, and observability points to a DevOps niche, which is somewhat distinctive. However, the broad category names could overlap with more specific skills for Docker, Terraform, or monitoring individually. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%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-organized operational guidance skill that clearly defines scope, transitions, and failure modes. However, it reads more like a philosophy document than an actionable skill — it tells Claude what to value (read before writing, plan before applying) without providing concrete examples, commands, or templates. The lack of executable code/config examples significantly limits its actionability.
Suggestions
Add concrete, executable examples for key workflows: a terraform plan/apply sequence, a sample alert definition (e.g., Prometheus/CloudWatch), a sample structured logging snippet, or a pipeline YAML fragment showing the recommended patterns.
Include a concrete runbook template or example showing what a good runbook entry looks like when paired with a new alert.
Tighten the Failure Modes section — the Cause/Fix pattern is repetitive and could be condensed into a table or shorter bullet list, saving tokens.
Add a validation checkpoint to the observability workflow (e.g., 'After wiring metrics, verify they appear in the dashboard before merging').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some verbose sections that explain concepts Claude already understands (e.g., what observability means, what reproducible pipelines are). The 'Failure Modes' section repeats the 'Cause/Fix' pattern six times with somewhat obvious advice. The 'What Operate Does NOT Do' section is useful for scoping but could be tighter. | 2 / 3 |
Actionability | The skill provides directional guidance (e.g., 'generate the plan,' 'read existing modules,' 'alert on SLO breaches') but lacks concrete, executable examples. No actual code snippets, terraform commands with flags, example alert definitions, example dashboard configs, or pipeline YAML are provided. It describes what to do rather than showing how. | 2 / 3 |
Workflow Clarity | The IaC section has a reasonable sequence (read → plan → name blast radius → apply with approval), which is good. However, other areas (observability, environments, CI/CD) lack clear step-by-step workflows. There's no explicit validation/feedback loop for observability setup or pipeline changes, and the plan-then-apply workflow could be more explicit about error recovery. | 2 / 3 |
Progressive Disclosure | The skill references external files (foundation skill, model.md, guidelines.md, devops agent) which is good structure, but no bundle files are provided to verify these exist. The content itself is somewhat monolithic — the four operating areas, failure modes, transitions, and cross-plugin context are all inline rather than being split into focused reference documents. For a skill of this length (~120 lines), some of this could be externalized. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- audenaert/etak
- Commit
632c389
- 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.