docker-management

Manage Docker containers, images, volumes, and Compose.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/devops/docker-management/SKILL.md

Quality

Content

82%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.

A well-structured, highly actionable Docker reference with executable commands, a real compose example, explicit verification, and sensible destructive-operation warnings; its main gaps are minor duplication and a monolithic structure that could offload some advanced material to reference files.

Suggestions

Consider moving the Dockerfile Optimization Tips (and perhaps the full compose.yml reference) into a separate reference file linked from SKILL.md to improve progressive disclosure.

Trim or consolidate the Quick Reference table since the same commands appear expanded in the Procedure section, reducing token duplication.

Optionally frame the Procedure as a short linear decision flow (identify domain -> act -> verify) so the workflow sequence and feedback loop read more explicitly.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with inline comments that earn their place and no padding about what Docker is; the Quick Reference table partially duplicates the Procedure section, keeping it just below anchor 5.	4 / 5
Actionability	It provides copy-paste-ready, executable commands across all domains plus a complete compose.yml example, covering the common cases fully as in anchor 5.	5 / 5
Workflow Clarity	The domain-organized procedure is paired with an explicit Verification section and destructive-operation warnings (e.g. 'Never run docker system prune -a --volumes without confirming'), so it is not capped at 3; it stays at 4 because the 'procedure' is categorical rather than a single linear sequence with feedback loops.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and appropriately placed inline content; it is a monolithic ~280-line file with no bundle files, and the Dockerfile Optimization Tips appendix could plausibly be split out, keeping it below anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

65%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.

A clean, domain-specific description that clearly states what it manages, but it is missing an explicit 'Use when...' trigger clause and relies on one generic verb rather than enumerating concrete actions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to run, build, debug, or clean up Docker containers, images, volumes, or Compose stacks.'

Replace the single verb 'Manage' with a few concrete actions (e.g. 'Run, build, stop, and inspect Docker containers, images, volumes, and Compose stacks') to lift specificity.

Include natural synonyms such as 'Dockerfile' and 'docker compose' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Docker domain and several managed objects ('containers, images, volumes, and Compose') but uses a single generic verb ('Manage'), matching anchor 3 rather than the multi-action anchor 4/5.	3 / 5
Completeness	It has a clear 'what' (manage Docker containers, images, volumes, Compose) but no 'Use when...' clause or explicit trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'Docker', 'containers', 'images', 'volumes', and 'Compose' are natural terms users say, giving good keyword coverage; a few synonyms like 'Dockerfile' are missing, so it is below anchor 5.	4 / 5
Distinctiveness Conflict Risk	The Docker-specific niche with named sub-objects (containers, images, volumes, Compose) is clearly distinct from other skills and unlikely to trigger for the wrong skill.	5 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/devops/docker-management/SKILL.md
Commit: 6680afb

Reviewed: about 5 hours 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.