Name: nic-docker-images
Rating: 64.8 (1 reviews)
Author: nginx

nic-docker-images

Docker image build system, Dockerfile structure, image variants, build scripts, and Makefile targets for NIC. Use when building container images, modifying the Dockerfile, adding new image variants, debugging image builds, or working with build scripts.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/nic-docker-images/SKILL.md

Quality

Content

65%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 accurate, dense, well-sectioned reference that assumes Claude's competence and avoids concept padding, but it behaves as a monolithic inlined manual with no progressive disclosure and no validation checkpoints for batch/push operations.

Suggestions

Move the exhaustive variant matrix and full Makefile target table into a references file (e.g. references/variants.md) and link to it from SKILL.md, keeping only the build command and key conventions inline.

Add a short sequenced build workflow with a validation checkpoint (e.g. 'make debian-image', then 'docker run --rm <image> nginx -t' to verify) before push, to lift workflow clarity above the batch-operation cap.

Trim or collapse the 9-column variant table to the OS-family/edition summary, since the per-cell yes/no grid is the densest token cost for limited marginal actionability.

Dimension	Reasoning	Score
Conciseness	The body is dense and fluff-free (no explaining what Docker is), but the full 9-column variant matrix and complete Makefile target table are heavy inlined reference material that could be trimmed or split.	4 / 5
Actionability	Concrete guidance is present — the actual 'docker build --platform linux/$(ARCH) --target $(TARGET) -f build/Dockerfile' invocation, '--secret id=nginx-repo.crt' flags, and exact script paths — with only minor gaps in copy-paste recipes.	4 / 5
Workflow Clarity	The content is a reference map (architecture, targets, args) rather than a sequenced build workflow, and it lacks validation/verification checkpoints; the batch 'all-images' (18 variants) and outward-facing 'push' targets trigger the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	Section headers and tables give decent structure, but with no bundle files present the entire reference bulk (variant matrix, full target list, script table) is inlined in SKILL.md with zero one-level-deep references to split it out.	3 / 5
	Total	14 / 20 Passed

Description

88%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, well-structured description that clearly states both capability and trigger conditions with concrete actions. The main gap is missing synonyms and file extensions in the trigger terms.

Suggestions

Add natural synonyms and file/path cues to the trigger clause, e.g. 'docker build', 'make targets', or 'build/Dockerfile', to lift trigger-term coverage toward comprehensive.

Consider naming the NGINX/App Protect variant angle (e.g. 'adding NAP/WAF/DoS variants') in the 'Use when' clause to further sharpen distinctiveness from generic container-build skills.

Dimension	Reasoning	Score
Specificity	The 'Use when' clause lists five concrete actions — 'building container images, modifying the Dockerfile, adding new image variants, debugging image builds, or working with build scripts' — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	It explicitly answers both 'what' ('Docker image build system, Dockerfile structure, image variants, build scripts, and Makefile targets for NIC') and 'when' ('Use when building container images, modifying the Dockerfile...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a developer would say are present (Dockerfile, Makefile, container images, image variants, build scripts), but it lacks synonyms and file extensions, so it falls short of the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The 'for NIC' scoping plus specific artifacts (Dockerfile, Makefile targets, image variants) carve a distinct niche, but Docker/container building is a common domain with minor overlap risk against generic docker skills.	4 / 5
	Total	18 / 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: nginx/kubernetes-ingress
Path: .github/skills/nic-docker-images/SKILL.md
Commit: 0eb3072

Reviewed: 1 day 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.