docker

Author and harden Dockerfiles for Node/.NET/Angular on AKS. Trigger: create/audit a Dockerfile, container findings.

Quality

77%

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 ./ywai/skills/docker/SKILL.md

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.

An exceptionally lean, actionable, and well-sequenced skill body with strong validation in the Review workflow. Its one real defect is bundle integrity: the Author branch repeatedly points to templates/ files that are not shipped.

Suggestions

Ship the referenced templates/ files (node-backend.Dockerfile, spa-nginx.Dockerfile + spa-nginx.conf, dotnet-api.Dockerfile, node.dockerignore, dotnet.dockerignore) so the Author branch's "copy the matching template" instruction actually resolves.

If the templates live elsewhere, either inline minimal starter Dockerfiles or correct the paths to point at the real bundle location.

Consider folding the brief "Our stance" restatement of Rules 6 and 10 into the rules themselves to remove the small redundancy.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Docker competence throughout, with no concept padding; every line carries specific rules, commands, or image references. The only mild repetition (Rules 6/10 restated in "Our stance") is deliberate reinforcement, not verbosity.	5 / 5
Actionability	Copy-paste securityContext YAML and concrete commands (docker buildx imagetools inspect, npm ci --ignore-scripts --no-audit --no-fund, --mount=type=secret) cover the common cases, but the Author branch leans on templates/*.Dockerfile files that are not present in the bundle, leaving a gap.	4 / 5
Workflow Clarity	The Review branch is a clear six-step sequence with explicit validation (docker build + smoke test + id + /health_check), a three-iteration plan, and a referenced checklist; validation is present so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	Section structure is good and references/review-checklist.md resolves one level deep, but five referenced templates/ files (node-backend.Dockerfile, spa-nginx.Dockerfile, dotnet-api.Dockerfile, node.dockerignore, dotnet.dockerignore, spa-nginx.conf) do not exist in the bundle, leaving the Author branch's primary references dangling.	3 / 5
	Total	17 / 20 Passed

Description

70%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 compact, specific description that states both capability and trigger, well-targeted to a Dockerfile/AKS niche. The main weakness is terseness in the trigger clause and only two named actions.

Suggestions

Expand the trigger clause into a fuller "Use when…" sentence with variations, e.g. "Use when creating or auditing a Dockerfile, containerizing a Node/.NET/Angular app, or addressing container scan findings."

Add one or two more concrete actions (e.g. "pin and scan images") to lift specificity from two actions to several.

Include common synonyms like "containerize" or "image" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Author and harden Dockerfiles" names the domain plus two concrete actions, matching the 1-2-actions anchor; it does not enumerate several actions, so it stays at 3 rather than 4.	3 / 5
Completeness	Both what ("Author and harden Dockerfiles for Node/.NET/Angular on AKS") and when (an explicit "Trigger:" clause) are present, but the when is terse compared to a full multi-variation "Use when…" sentence.	4 / 5
Trigger Term Quality	"create/audit a Dockerfile, container findings" are natural phrases a user would say, giving good keyword coverage, though synonyms like "containerize" or "image" are missing.	4 / 5
Distinctiveness Conflict Risk	The Dockerfiles-on-AKS niche is mostly distinct with concrete triggers, but there is minor overlap risk with a generic devops or Kubernetes skill.	4 / 5
	Total	15 / 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: YoizenSA/dev-ai-workflow
Path: ywai/skills/docker/SKILL.md
Commit: 36f5af5

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.