nic-planning

Task planning and approach strategy for NIC. Use when starting any non-trivial task, reading issues or specs, planning before implementing, or when asked to create a plan for a change.

Quality

86%

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

88%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, project-specific planning skill with concrete commands, exact paths, explicit verification checkpoints, and strong sequencing. Its only weaknesses are mild cross-section repetition and a monolithic structure that makes no use of reference files.

Suggestions

Consolidate the three layer listings (Before Writing Code step 4, Layer Impact Checklist, Ordering Rules) so each layer is described once and cross-referenced, reducing repetition.

Move the Definition of Done table and Ordering Rules into a reference file under references/ and summarize them in SKILL.md to improve progressive disclosure and reduce the monolithic body.

Add a one-line pointer to where NIC invariants live beyond the AGENTS.md mention, so the security/codegen invariants are discoverable without re-reading the full checklist.

Dimension	Reasoning	Score
Conciseness	Dense, project-specific operational guidance with no concept-explanation fluff, but the affected layers appear in three sections (Before Writing Code step 4, Layer Impact Checklist, Ordering Rules) which is minor repetition that could be tightened; not a 5 due to that redundancy.	4 / 5
Actionability	Fully executable guidance: copy-paste-ready make commands (make update-codegen, make update-crds, make telemetry-schema, make test-update-snaps), exact file paths, and verification git commands covering the common multi-layer change cases.	5 / 5
Workflow Clarity	Clear sequenced 10-step ordering process plus a Definition of Done table with explicit verification commands and feedback loops (regenerate, re-run, "Both pass"), and the snapshot silent-failure rule provides an explicit checkpoint; validation is present so no cap applies.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with a single one-level external reference (AGENTS.md) and no nested references; not a 5 because the doc is a monolithic single file over 50 lines with no split of detailed material into bundle files.	4 / 5
	Total	18 / 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 well-constructed description that clearly states both capability and explicit trigger conditions in third person. It is specific and actionable, with only minor gaps in trigger-term breadth and distinctiveness against generic planning skills.

Dimension	Reasoning	Score
Specificity	Lists several specific actions ("reading issues or specs", "planning before implementing", "create a plan for a change") tied to the NIC domain, with only minor gaps; not a 5 because the actions are generic planning verbs rather than concrete technical operations.	4 / 5
Completeness	Explicitly answers both what ("Task planning and approach strategy for NIC") and when ("Use when starting any non-trivial task, reading issues or specs, planning before implementing, or when asked to create a plan for a change") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases users would say ("create a plan for a change", "planning before implementing", "reading issues or specs") with good coverage; not a 5 because synonyms like "design" or "break down this task" and the NIC jargon itself are not as comprehensively covered.	4 / 5
Distinctiveness Conflict Risk	The "for NIC" domain scope and issues/specs context give it a clear niche with only minor overlap risk; not a 5 because "starting any non-trivial task" is broad enough to overlap with general planning skills.	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-planning/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.