Name: agent-ops-docker-review
Rating: 62.4 (1 reviews)
Author: majiayu000

agent-ops-docker-review

Docker image reviews, optimization, and step-building guidance. Analyzes Dockerfiles for best practices, security issues, and anti-patterns.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./analysis/agent-ops-docker-review/SKILL.md

The canonical home for this skill is agent-ops-docker-review in majiayu000/claude-skill-registry

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete executable templates and commands, and the multi-mode workflows are clearly sequenced with safety checks. Its main weakness is progressive disclosure: substantial reference material is inlined rather than split into one-level-deep reference files.

Suggestions

Move the per-language Dockerfile templates into a references/ file (e.g., references/templates.md) and link to them from Build mode.

Move the full Best Practices Rules tables into a references file, keeping only a concise summary inline.

Add an explicit validate-fix-retry loop in Optimize mode (e.g., re-run Review on the optimized Dockerfile to confirm findings are resolved).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference material (rule tables, templates, commands) without explaining concepts Claude already knows, though some full output-format examples could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready executable Dockerfile templates for Python/Node/Go/.NET plus concrete scanner commands (trivy, grype, dockle, dive, hadolint) covering the common cases.	5 / 5
Workflow Clarity	Each mode has a clearly numbered procedure with safety checkpoints (tool detection, user confirmation, diff-before-modify), but there is no explicit validate-fix-retry feedback loop, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but all content — including four full language templates and the complete best-practices rule tables — is inlined in a single ~400-line file with no reference files to split it.	3 / 5
	Total	16 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 clearly conveys what the skill does and occupies a distinct Docker-specific niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding natural trigger phrasing would raise the score.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when reviewing or optimizing Dockerfiles, or when the user mentions Docker images, container security, or image size').

Replace the generic 'step-building guidance' with a concrete action like 'generate Dockerfiles step-by-step'.

Include common synonyms such as 'containers' and 'Docker image size' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'reviews, optimization, and step-building guidance' and 'Analyzes Dockerfiles for best practices, security issues, and anti-patterns' — but 'step-building guidance' is slightly generic, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Natural terms like 'Docker image', 'Dockerfiles', 'best practices', 'security issues', and 'anti-patterns' are present, but common variations such as 'container' or file-context phrases are missing.	4 / 5
Distinctiveness Conflict Risk	The Docker/Dockerfile niche is clearly defined with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: majiayu000/claude-skill-registry-data
Path: analysis/agent-ops-docker-review/SKILL.md
Commit: d5a9e94

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.