agent-ops-docker-review
Docker image reviews, optimization, and step-building guidance. Analyzes Dockerfiles for best practices, security issues, and anti-patterns.
Install with Tessl CLI
npx tessl i github:majiayu000/claude-skill-registry-data --skill agent-ops-docker-review73
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
57%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 adequately identifies the Docker/Dockerfile domain and lists relevant capabilities like optimization and security analysis. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know when to select this skill, and could benefit from more natural trigger terms users might actually say when needing Docker help.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Dockerfile optimization, container image size, Docker security, or building Docker images'
Include additional natural trigger terms users might say: 'container', 'docker build', 'multi-stage builds', 'image layers', '.dockerfile'
| 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 | Clearly answers 'what' (reviews, optimization, analyzes for best practices/security/anti-patterns), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 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', '.dockerfile', or 'multi-stage builds'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Docker/Dockerfiles with distinct terminology; unlikely to conflict with other skills as the domain is well-defined and specific to container image configuration. | 3 / 3 |
Total | 9 / 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 its length—at ~300 lines with multiple complete Dockerfile templates inline, it could benefit from splitting templates and detailed rules into separate reference files. The content is practical and covers security, optimization, and tooling comprehensively.
Suggestions
Move language-specific Dockerfile templates to a separate TEMPLATES.md file and reference it from the Build Mode section
Extract the Best Practices Rules tables to a RULES.md reference file to reduce main skill size
Trim explanatory text for tools like trivy, grype, dockle—Claude knows what vulnerability scanners do
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy—multiple complete Dockerfile templates for different languages add bulk. The tables and structured rules are good, but some explanations (like what each scanner does) could be trimmed since Claude knows these tools. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples, specific commands for each mode, complete Dockerfile templates with placeholders, and concrete scanner commands. The output formats are copy-paste ready with clear structure. | 3 / 3 |
Workflow Clarity | Each mode has a clear numbered procedure with explicit steps. The Review mode has locate→analyze→generate flow, Optimize shows before/after with changes applied, Build mode has an interview→generate→review sequence. Scan mode includes tool detection and aggregation steps. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but this is a monolithic file that could benefit from splitting. Language templates, best practices rules, and scanner details could be separate reference files. No external file references are provided. | 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 | |
- 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.