container-manager

Use this skill when the user wants to manage Docker containers, build images, inspect logs, handle Docker Compose, or work with container orchestration.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/container-manager/SKILL.md

Quality

Content

76%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 tight, highly actionable code reference that assumes Claude's competence and avoids conceptual padding. Its main weakness is the absence of validation/verification safeguards around destructive operations (container removal and volume-removing compose down), which caps workflow clarity.

Suggestions

Add an explicit verification step before destructive calls — e.g. confirm the container identity/status before 'remove_container', and warn that 'compose_down -v' permanently deletes named volumes.

Consider moving the Docker Compose and Stats sections into a separate reference file so SKILL.md stays a lean overview with one-level-deep pointers.

Trim the Quick Reference table or the Overview line where they duplicate the inline code to recover token budget.

Dimension	Reasoning	Score
Conciseness	Largely lean and code-first with no padding or explanation of concepts Claude already knows, but the Quick Reference table and Overview line restate content already shown in the code sections, leaving minor redundancy that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready Python using the real docker SDK and subprocess calls, covering the common cases (list/start/stop/remove, logs, build, stats, compose, exec) with complete function definitions.	5 / 5
Workflow Clarity	Sections are clearly organized but destructive operations — 'remove_container' (force) and 'compose_down' with 'volumes=True' — have no validation or verification checkpoints, which caps workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and a useful summary table in a single self-contained file; no bundle files exist and none are strictly needed, but the ~100-line monolithic body could split Compose/Stats detail into reference files for clearer navigation.	4 / 5
	Total	16 / 20 Passed

Description

75%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 strong, trigger-rich description that names a Docker-specific niche with concrete actions and an explicit 'Use when' clause. It falls just short of the top anchors because the 'what' is fused into the 'when' clause and a couple of terms ('manage', 'orchestration') are slightly generic.

Suggestions

Lead with a concise declarative 'what' statement (e.g. 'Manage the full Docker container lifecycle...') before the 'Use when' clause to fully separate what from when.

Replace the generic 'manage Docker containers' / 'container orchestration' phrasing with concrete verbs (start, stop, remove, network, volume) to lift specificity.

Add natural synonyms or CLI cues users actually say (e.g. 'docker ps', 'container logs', 'images') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'build images, inspect logs, handle Docker Compose' — but 'manage Docker containers' and 'container orchestration' remain somewhat generic, leaving minor gaps in coverage.	4 / 5
Completeness	Explicitly answers 'when' via 'Use this skill when the user wants to...' and conveys 'what' through the embedded action list, but lacks a separate declarative capability statement that the top anchor requires.	4 / 5
Trigger Term Quality	Includes natural user-facing terms ('Docker containers', 'build images', 'inspect logs', 'Docker Compose') with good coverage, though it misses common synonyms and CLI-style phrases users might say.	4 / 5
Distinctiveness Conflict Risk	Clearly Docker-focused with a distinct niche and minimal conflict risk, though the 'container orchestration' phrase introduces minor overlap with dedicated orchestration (e.g. Kubernetes) skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ProwlrBot/prowlr-marketplace
Path: skills/container-manager/SKILL.md
Commit: 32f0050

Reviewed: 3 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.