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

81%

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

68%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 dense, well-structured reference for the build system that is strong on concrete facts and non-obvious gotchas, with no padding. Its main gap is workflow: the "add a new image variant" flow is scattered across Gotchas bullets rather than presented as a sequenced, validated checklist.

Suggestions

Add a numbered "Adding a new image variant" workflow that sequences the required steps (Dockerfile stage pair, Makefile target, all-images entry, matrix-images-nap.json entries) and ends with an explicit validation step such as a local build or running the agentv2/agentv3 pytest markers.

Include one complete example build command (e.g., a fully expanded docker build invocation with BUILD_OS, NAP_MODULES, and --secret flags) so the guidance is copy-paste ready.

Replace the full 25-row Makefile target table with the non-obvious exceptions (the DoS-only -agent targets, the FIPS/NAP asymmetries) and point to the Makefile as the source of truth for the rest.

Dimension	Reasoning	Score
Conciseness	Dense, unpadded, table-driven content of repo-specific facts that assumes Claude's competence (no explanation of Docker or multi-stage builds); the full 25-row Makefile target table duplicates what the Makefile already states and could be trimmed to exceptions plus a pointer to the source of truth.	4 / 5
Actionability	Concrete commands ("make all-images", "make ubi10-dependency-image-local"), exact build args with sources of truth, and exact script paths give mostly executable guidance; there is no complete copy-paste build invocation showing the $(DOCKER_CMD) pattern with real values.	4 / 5
Workflow Clarity	No sequenced workflow for the skill's core task (adding a new variant) — the required steps appear only as one Gotchas bullet — and there are no validation checkpoints (e.g., verify with a local build or the agentv2/agentv3 pytest markers); below 4 due to missing checkpoints, above 2 because steps are enumerated and coherent.	3 / 5
Progressive Disclosure	Well-organized into clear sections and tables with one-level navigation and no nested references; the large target/args tables are inlined, which is acceptable for a self-contained skill but leaves minor organization gaps versus an ideal split.	4 / 5
	Total	15 / 20 Passed

Description

83%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 description: specific, third-person, and concise, with an explicit "Use when..." clause covering the main user intents. Trigger coverage is good but could add common synonyms like "docker build" or "base image" to fully match the top anchors.

Dimension	Reasoning	Score
Specificity	Names several concrete capabilities ("Dockerfile structure, image variants, build scripts, and Makefile targets") tied to a specific system (NIC), though they are listed as nouns rather than actions and omit build conventions/gotchas covered in the body.	4 / 5
Completeness	Clearly answers "what" (build system, Dockerfile structure, variants, scripts, Makefile targets) and "when" with an explicit multi-trigger "Use when..." clause containing concrete phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"building container images, modifying the Dockerfile, adding new image variants, debugging image builds" are natural phrases a user would say; a few common synonyms (e.g., "docker build", "base image") are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (NIC's image build system) with distinct triggers; "building container images" is generic enough to carry minor overlap risk with a general Docker skill.	4 / 5
	Total	17 / 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: 499c5f6

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