Name: nic-add-feature
Rating: 78.4 (1 reviews)
Author: nginx

nic-add-feature

Checklists for adding Ingress annotations, VirtualServer/VSR fields, or Helm chart values to NIC. Use when adding new configuration options, new NGINX directives, new annotations, new CRD fields, or new Helm values.

Quality

98%

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

96%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, actionable skill body with lean stepwise workflows, real commands and code, and built-in validation feedback loops for code-gen and template batch operations. The only gap is progressive disclosure: reference-style material (kubebuilder marker table, CEL examples) lives inline rather than in a split reference file.

Suggestions

Move the Kubebuilder Markers table and CEL Validation Examples into a references/ file (e.g. references/virtualserver-conventions.md) and link to it from the VirtualServer/VSR section to push progressive_disclosure to 5.

Add a one-line 'Prerequisites / repo layout' pointer at the top so contributors new to the NIC tree know where the version1 vs version2 template trees live before following the steps.

Dimension	Reasoning	Score
Conciseness	Dense, lean step lists with specific file paths and commands; no padding and no explanation of concepts Claude already knows — every line (including the gotchas) earns its place.	5 / 5
Actionability	Fully executable guidance: concrete file paths, exact make targets (make update-codegen, make update-crds, make test-update-snaps), and real Go/CEL code examples that are copy-paste ready.	5 / 5
Workflow Clarity	Three clearly sequenced workflows with explicit validation checkpoints (snapshot cases, make test-update-snaps) and feedback loops ('An unchanged __snapshots__ diff ... means no fixture exercises the new branch — the annotation is untested'), satisfying the batch-operation validation requirement.	5 / 5
Progressive Disclosure	Well-organized into three top-level sections with targeted subsections (Gotchas, JSON Tag Conventions, Kubebuilder Markers, CEL Examples), but it is a single ~100-line file with reference-like tables inlined and no one-level-deep external references to offload them.	4 / 5
	Total	19 / 20 Passed

Description

100%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 tightly written, third-person description that concretely names what the skill provides and when to invoke it, with strong natural trigger-term coverage and a distinct niche. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names the NIC domain and multiple concrete actions across three feature surfaces — 'adding Ingress annotations, VirtualServer/VSR fields, or Helm chart values' — giving comprehensive coverage rather than a single generic action.	5 / 5
Completeness	Explicitly answers both 'what' (checklists for adding annotations, VSR fields, Helm values to NIC) and 'when' (a concrete 'Use when adding...' clause listing the triggering situations).	5 / 5
Trigger Term Quality	The 'Use when' clause enumerates natural trigger terms a NIC contributor would actually say — 'new configuration options, new NGINX directives, new annotations, new CRD fields, or new Helm values' — with synonym coverage (VSR/VirtualServer).	5 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (NIC feature addition) with distinct, domain-specific triggers; minimal risk of firing for an unrelated skill.	5 / 5
	Total	20 / 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-add-feature/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.