docker-extend

Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install tools in docker'. Does: Interactively sets up Dockerfile.user and docker-compose.override.yml so users can add personal tools to their Docker environment without affecting maintainer files or committing user-specific config to git.

Quality

95%

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

Quality

Content

100%Weight 40%Scale 1-3

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

The content is well-crafted: concise yet fully actionable, with a clearly sequenced five-step workflow that includes mode-detection branching, safety guards against overwriting files, and explicit reminders that user files are gitignored. No bundle files are needed or referenced, and the organization is clean.

Dimension	Reasoning	Score
Conciseness	The body is lean: it assumes Claude's competence, avoids explaining what Docker or compose files are, and every step (mode detection, copy commands, apt-get block, rebuild command) earns its place with no padded concepts.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands — `cp Dockerfile.user.example Dockerfile.user`, a concrete `RUN apt-get install` Dockerfile block, and `docker compose build && docker compose up -d` — plus an explicit instruction to use the Edit tool rather than rewriting files.	3 / 3
Workflow Clarity	A five-step sequence is clearly ordered with decision checkpoints: mode detection branches (DEV/DEPLOY/UNKNOWN), file-existence checks that gate whether to copy, an explicit 'Do NOT overwrite existing files' guard, and 'Do NOT run it automatically' for the rebuild — matching the level-3 sequencing-with-checkpoints anchor.	3 / 3
Progressive Disclosure	This is a self-contained single-file skill with no bundle references; content is organized into clearly numbered steps and well-signaled sections, so per the simple-skill scoring note it earns a 3 without external file references.	3 / 3
	Total	12 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 is strong: it gives explicit 'Use when'/'Does' guidance, a rich set of natural trigger phrases, and a distinctive niche around gitignored user Docker customization. Its only weakness is that the capability statement is a single setup action rather than an enumeration of multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Names concrete artifacts ('Dockerfile.user and docker-compose.override.yml') and a clear action ('Interactively sets up ... so users can add personal tools'), but the description centers on a single verb ('sets up') rather than listing multiple distinct concrete actions, so it falls short of the level-3 anchor.	2 / 3
Completeness	It explicitly answers both 'when' via the 'Use when:' clause and 'what' via the 'Does:' clause with explicit trigger guidance, matching the level-3 example structure.	3 / 3
Trigger Term Quality	The Triggers list provides strong natural coverage users would actually say — 'extend docker', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'install tools in docker' — matching the level-3 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche — user-specific, gitignored Docker override customization — with distinct triggers ('docker-extend', 'personalize docker setup') unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: coleam00/Archon
Path: .claude/skills/docker-extend/SKILL.md
Commit: ace0a41

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