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

84%

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

76%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 highly actionable, token-efficient reference for the NIC Docker image build system with concrete commands, lookup tables, and useful gotchas. Its main weakness is the absence of an explicit sequenced build/push workflow with validation checkpoints.

Suggestions

Add a short 'Build workflow' section that sequences the common path end-to-end (pick variant → run make target → verify image → push) with an explicit validation checkpoint before push.

For destructive/external operations like 'make push' and 'make patch-os', state a concrete verification step (e.g. inspect image labels/digest, run a smoke container) before proceeding.

Consider moving the full 25-row Makefile target matrix into a references/ file and keeping only the most common targets inline, to sharpen the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	Dense, information-packed reference with no padding or explanation of basics Claude already knows (Docker, multi-stage builds); every table and gotcha earns its place, with only minor spots that could be tightened.	4 / 5
Actionability	Provides copy-paste-ready commands ('docker build --platform linux/$(ARCH) --target $(TARGET) -f build/Dockerfile'), a full target→BUILD_OS/NAP_MODULES/Agent lookup table, named build args with their source of truth, and concrete script paths covering the common build cases.	5 / 5
Workflow Clarity	Content is well organized as a reference but is not framed as a sequenced multi-step workflow, and operations like 'push' and 'patch-os' lack explicit validation checkpoints; the Gotchas provide guardrails but no validate→fix→retry loop.	3 / 5
Progressive Disclosure	Single self-contained file with no bundle references, but cleanly divided into well-labeled sections (Architecture, Variants, Targets, Args, Scripts, Conventions, Gotchas) so navigation is easy; minor gap is that the large variant/target tables could optionally live in a reference file.	4 / 5
	Total	16 / 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 answers both what the skill covers and when to use it, with concrete actions and a well-scoped niche. The only minor gap is missing a few natural synonyms/invocations a user might say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('building container images, modifying the Dockerfile, adding new image variants, debugging image builds, or working with build scripts') plus concrete nouns (Dockerfile structure, image variants, Makefile targets), giving comprehensive coverage rather than just several.	5 / 5
Completeness	Explicitly states both the 'what' (Docker image build system, Dockerfile structure, image variants, build scripts, Makefile targets for NIC) and the 'when' ('Use when building container images, modifying the Dockerfile...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural domain terms are present ('building container images', 'modifying the Dockerfile', 'Makefile targets', 'debugging image builds'), but it lacks common synonyms or invocations a user might say (e.g. 'docker build', 'make') so it falls just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche ('for NIC' Docker image builds) with distinct triggers (Dockerfile, Makefile targets, image variants), minimizing overlap with unrelated skills.	5 / 5
	Total	19 / 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: 95d3987

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