nic-structure

NIC architecture, resource processing pipeline, template systems, and key type definitions. Use when exploring the codebase, understanding data flow, debugging config generation, or working on controller logic.

Quality

83%

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

78%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 concrete architecture reference that excels at actionability with exact paths, functions, and commands, and sequences the processing pipeline clearly. Its main weakness is progressive disclosure: a large monolithic file with no external references where several tables and listings would benefit from being split into reference files.

Suggestions

Move the repository layout, secret-type table, and kubebuilder marker table into reference files under references/ (e.g. references/repo-layout.md, references/secret-types.md, references/markers.md) and link to them from SKILL.md to improve progressive disclosure.

Add an explicit regeneration workflow with validation checkpoints for generated artifacts, e.g. change source -> make update-codegen && make update-crds -> diff config/crd/bases AND deploy/crds*.yaml AND docs/crd/ -> commit only when diff is clean, to close the verify-codegen gap called out in 'Two traps'.

Trim or externalize the Key Types definitions section so the core SKILL.md stays a lean overview pointing to detail, reducing the monolithic length.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no basic explanations of k8s, CRDs, or templating), with nearly every line carrying concrete file/function info; it stays at 4 rather than 5 because the ~250-line monolith contains bulk reference material that could be trimmed or externalized.	4 / 5
Actionability	Highly concrete and executable guidance throughout: exact file paths (e.g. internal/configs/configurator.go), function names (AddOrUpdateVirtualServer, GetSecret), copy-paste-ready make commands (make update-codegen, make update-crds, make test-update-snaps), a real Go struct example, and explicit layer-crossing rules.	5 / 5
Workflow Clarity	The Resource Processing Pipeline is a clearly sequenced multi-step flow with inline source citations, and the "Two traps" section supplies verification guidance for the generated-artifacts regen workflow; it is not 5 because no explicit validate→fix→retry feedback loop is framed for the batch regeneration steps.	4 / 5
Progressive Disclosure	Sections are well organized with clear headers, but the skill is a monolithic single file with no external bundle references (references/scripts/assets are absent) and substantial reference-style content (secret-type table, kubebuilder marker table, full repository layout, key type definitions) is inlined in a ~250-line file rather than split into navigable reference files.	3 / 5
	Total	16 / 20 Passed

Description

87%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 that cleanly states both scope and trigger conditions in third person, with concrete, naturally-voiced trigger phrases tied to a distinct codebase niche. The only soft spot is that the "what" reads as a topic list rather than a list of concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ("NIC architecture, resource processing pipeline, template systems, and key type definitions") and lists several concrete actions ("exploring the codebase, understanding data flow, debugging config generation, or working on controller logic"); the "what" half is topic-based rather than action-based, so it stops short of comprehensive coverage at 5.	4 / 5
Completeness	Explicitly answers both what (the four architecture areas) and when ("Use when exploring the codebase, understanding data flow, debugging config generation, or working on controller logic") with concrete trigger phrases, matching the anchor for clearly answering both.	5 / 5
Trigger Term Quality	Natural developer phrases like "exploring the codebase", "understanding data flow", "debugging config generation", and "controller logic" would plausibly be said by a user needing this skill; a few synonyms or file extensions are missing, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	Targets a specific NIC codebase niche with distinct, domain-locked triggers; the generic "exploring the codebase" phrase is anchored by NIC-specific terms so conflict risk is minimal.	5 / 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-structure/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.