agent-ops-docker-review
Docker image reviews, optimization, and step-building guidance. Analyzes Dockerfiles for best practices, security issues, and anti-patterns.
66
Quality
58%
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/analysis/agent-ops-docker-review/SKILL.mdQuality
Discovery
40%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 establishes a clear Docker-focused niche and mentions relevant capabilities, but lacks explicit trigger guidance ('Use when...') which is critical for skill selection. The specificity of actions could be improved by listing concrete tasks like layer optimization, multi-stage build guidance, or specific security checks.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Dockerfile', 'container image', 'docker build', 'image size', 'container security'
Include common user phrases and file patterns such as '.dockerfile', 'multi-stage builds', 'layer caching', 'base image selection'
List more specific concrete actions like 'reduces image size', 'identifies vulnerable base images', 'recommends multi-stage build patterns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Docker) and some actions ('reviews, optimization, step-building guidance', 'Analyzes Dockerfiles'), but doesn't list comprehensive concrete actions like specific optimizations or security checks performed. | 2 / 3 |
Completeness | Describes what it does (analyzes Dockerfiles, reviews images) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Docker', 'Dockerfiles', 'image', 'security issues', 'best practices', but missing common variations users might say like 'container', 'dockerfile optimization', 'docker build', 'multi-stage builds', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Docker/Dockerfiles with distinct domain terminology; unlikely to conflict with other skills as Docker is a specific technology. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
77%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, highly actionable skill with clear workflows for each mode and executable examples throughout. The main weakness is that it's quite long with all language templates and rules inline, which could be better organized through progressive disclosure to separate reference files. The forbidden behaviors section and tool detection are good safety practices.
Suggestions
Move language-specific templates to a separate TEMPLATES.md file and reference it from the main skill
Consider moving the detailed best practices rules table to a RULES.md reference file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy—the language templates are quite verbose and could reference external files. The tables and structure are good, but the full templates inline add significant length. | 2 / 3 |
Actionability | Excellent actionability with fully executable Dockerfile examples, specific bash commands for scanning tools, concrete output formats, and copy-paste ready templates for multiple languages. | 3 / 3 |
Workflow Clarity | Each mode has clear numbered procedures with explicit steps. The Review mode has locate→analyze→generate sequence, Build mode has interview→generate→review flow, and Scan mode includes tool detection before execution. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but the skill is monolithic—language templates and detailed rules could be split into separate reference files. All content is inline rather than appropriately distributed. | 2 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- majiayu000/claude-skill-registry
- Commit
6213d1a
- 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.