Name: netalertx-docker-prune
Rating: 67.2 (1 reviews)
Author: netalertx

netalertx-docker-prune

Clean up unused Docker resources. Use this when asked to prune docker, clean docker, remove unused images, free disk space, or docker cleanup. DANGEROUS operation. Requires human confirmation.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

80%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, well-structured single-purpose skill that earns top marks for conciseness and organization. Its main weakness is the absence of explicit validation/verification steps for a destructive operation, which caps workflow clarity.

Suggestions

Add an explicit validation/verification step before and after the prune, e.g. check free disk space with `df -h` beforehand and confirm what will be removed, then re-check afterward, to satisfy the destructive-operation feedback-loop expectation.

Make the command portable or document the path requirement — the hardcoded "/workspaces/NetAlertX/..." path will fail outside that specific workspace; either reference a bundled script in ./scripts/ or note the path must be adjusted.

Show an example of the confirmation interaction (the prompt text and expected response) so Claude knows what to expect when invoking the script.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — a danger warning, one command, and terse bullet lists with no padding or explanations of what Docker is, so every token earns its place.	5 / 5
Actionability	It gives one concrete, copy-paste-ready command, but the hardcoded absolute path "/workspaces/NetAlertX/.devcontainer/scripts/confirm-docker-prune.sh" is environment-specific and no flags or example of the confirmation interaction are shown, leaving a minor executability gap.	4 / 5
Workflow Clarity	This is a destructive operation, and while confirmation is mentioned ("The script requires explicit confirmation before proceeding"), there is no explicit validation/verification checkpoint or feedback loop in the body, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the well-organized sections (Command, What Gets Deleted, When to Use, Safety) satisfy the simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

81%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 concise, well-triggered description with strong completeness and natural keywords, weakened only by a generic action verb and second-person phrasing. Tightening the capability list into third person would lift the specificity score.

Suggestions

Rewrite in third person and enumerate concrete actions, e.g. "Removes stopped containers, unused images, volumes, and networks. DANGEROUS — requires human confirmation." instead of "Clean up unused Docker resources".

Replace "Use this when..." with a third-person "Use when..." phrasing to avoid the second-person specificity penalty.

Dimension	Reasoning	Score
Specificity	"Clean up unused Docker resources" names the domain but offers only one generic action; the additional "DANGEROUS operation. Requires human confirmation" adds a second concrete characteristic, landing at base 3, but "Use this when..." is second-person voice which the rubric penalizes by -1.	2 / 5
Completeness	It explicitly answers both what ("Clean up unused Docker resources" plus the danger/confirmation behavior) and when ("Use this when asked to prune docker, clean docker, remove unused images, free disk space, or docker cleanup") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"prune docker, clean docker, remove unused images, free disk space, or docker cleanup" gives comprehensive natural synonyms a user would actually say, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The docker-specific framing is mostly distinct, but the trigger "free disk space" creates minor overlap risk with general disk-cleanup skills, so it stops just short of the clear-niche anchor.	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: netalertx/NetAlertX
Path: .github/skills/docker-prune/SKILL.md
Commit: 257431b

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