agent-ops-docker-review
Docker image reviews, optimization, and step-building guidance. Analyzes Dockerfiles for best practices, security issues, and anti-patterns.
74
68%
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 ./analysis/agent-ops-docker-review/SKILL.mdQuality
Discovery
67%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 does a good job specifying concrete capabilities around Docker image optimization and Dockerfile analysis, and it occupies a clear niche. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing some natural trigger term variations that users might employ when seeking Docker help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Dockerfiles, container images, Docker optimization, or image security.'
Include additional natural trigger terms like 'container', 'multi-stage build', 'image size', 'docker-compose', and '.dockerfile' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'reviews', 'optimization', 'step-building guidance', 'Analyzes Dockerfiles for best practices, security issues, and anti-patterns'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with reviews, optimization, and analysis of Dockerfiles. However, there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'Docker image', 'Dockerfiles', 'best practices', 'security issues', but misses common user variations like 'container', 'docker-compose', 'multi-stage build', '.dockerfile', or 'image size'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Docker images and Dockerfiles specifically, creating a distinct niche that is unlikely to conflict with other skills like general code review or security analysis tools. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
70%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 and highly actionable skill with clear workflows for each of its four modes, concrete code examples, and good safety constraints. Its main weakness is that it's monolithic — the language templates, output format examples, and scan details should be split into referenced files to improve token efficiency. The content would benefit significantly from progressive disclosure to reduce the ~300-line body to a concise overview with pointers to detailed references.
Suggestions
Move language templates (Python, Node, Go, .NET) to a separate TEMPLATES.md file and reference it from the Build Mode section
Move detailed output format examples (review report, optimize report, scan report) to a FORMATS.md reference file, keeping only a brief summary inline
Consider consolidating the rules tables into a separate RULES.md file, keeping only a summary count (e.g., '4 security, 6 optimization, 4 maintainability rules') in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) with four full language templates that are largely repetitive patterns. The templates could be referenced from a separate file. However, the content is mostly instructional rather than explanatory, and doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | Highly actionable with executable Dockerfile templates, specific bash commands for scanning tools, concrete output format examples, and copy-paste ready code blocks. The rules tables with IDs are specific and unambiguous. | 3 / 3 |
Workflow Clarity | Each mode has a clearly numbered procedure with explicit steps. The Review mode has a clear locate→analyze→report flow, Optimize builds on Review then shows before/after, Build mode has an interview→generate→review sequence, and Scan mode includes tool detection before execution. The forbidden behaviors section adds safety validation. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files for detailed content. The four language templates, detailed output format examples, and scan report examples should be split into separate reference files. Everything is inline in one large document. | 1 / 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
- majiayu000/claude-skill-registry-data
- Commit
6770aaa
- 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.