aif-dockerize

Analyze project and generate Docker configuration: Dockerfile (multi-stage dev/prod), compose.yml, compose.override.yml (dev), compose.production.yml (hardened), and .dockerignore. Includes production security audit. Use when user says "dockerize", "add docker", "docker compose", "containerize", or "setup docker".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%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 high-quality, highly actionable workflow with strong progressive disclosure and validation checkpoints. The main weakness is conciseness — the skill-context section and repeated Angie guidance add padding that could be trimmed.

Suggestions

Tighten the skill-context section (Step 0): the nested-CLAUDE.md analogy is explained at length; condense to a short rule that skill-context overrides general rules and apply to all artifacts.

Consolidate the Angie-over-Nginx preference, which currently appears in three separate places (Step 1.3, Step 2.5, Step 4.2), into a single stated rule referenced where needed.

Remove restated justifications (e.g. 'This prevents generating non-existent image tags') where the preceding instruction is already self-explanatory.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete detection tables and commands, but contains some unnecessary explanation — the skill-context analogy is restated at length and the Angie preference is repeated in three places — that could be tightened.	3 / 5
Actionability	Provides concrete, copy-paste-ready Glob/Grep/Read commands, base-image mapping tables, and specific hardening directives (read_only, cap_drop, user) that fully cover the common cases.	5 / 5
Workflow Clarity	A clearly sequenced multi-step process (Steps 0–9) with mode determination, validation checkpoints, quality-check checkboxes, and explicit feedback loops (e.g. fix-before-presenting, offer-to-fix on failing checks).	5 / 5
Progressive Disclosure	Acts as a well-organized overview with one-level-deep, clearly-signaled references (BEST-PRACTICES, SECURITY-CHECKLIST, ANGIE-ACME, etc.), each given with its purpose; all referenced files exist in references/.	5 / 5
	Total	18 / 20 Passed

Description

92%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, specific description that clearly states what the skill does and when to use it, with natural Docker-related trigger phrases and minimal conflict risk. The only minor gap is keyword synonym/extension coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete artifacts and actions — multi-stage Dockerfile, three distinct compose files, .dockerignore, and a production security audit — giving comprehensive coverage of its domain.	5 / 5
Completeness	Explicitly answers both what ('generate Docker configuration: Dockerfile...') and when ('Use when user says...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes several natural trigger phrases users would actually say ('dockerize', 'add docker', 'docker compose', 'containerize', 'setup docker'), though it omits a few synonyms or file-extension variants like 'Dockerfile'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Docker configuration generation — with distinct Docker-specific triggers, so overlap with other skills is minimal.	5 / 5
	Total	19 / 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
skill_md_line_count	SKILL.md is long (531 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: lee-to/ai-factory
Path: skills/aif-dockerize/SKILL.md
Commit: e144f95

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