CtrlK
BlogDocsLog inGet started
Tessl Logo

nic-add-policy

Step-by-step checklist for adding a new Policy CRD type to NIC. Use when implementing a new policy like AccessControl, RateLimit, JWTAuth, ExternalAuth, BasicAuth, IngressMTLS, EgressMTLS, OIDC, WAF, APIKey, Cache, or CORS, or extending the policy system with a new policy type.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%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, well-sequenced checklist that gives exact files, commands, and reusable code patterns with minimal padding. Its main gap is the absence of an explicit validation feedback loop and any external reference files.

Suggestions

Add an explicit validation checkpoint after codegen (e.g., 'Run make test; if failures appear, fix types.go/validation and re-run') to close the feedback-loop gap in workflow_clarity.

Consider moving the add*Config() and NGINX template patterns into a references/ file linked from the body to strengthen progressive_disclosure.

DimensionReasoningScore

Conciseness

Lean bullet points with exact file paths and commands; no concept over-explanation and every line is actionable. Assumes Claude's competence throughout.

5 / 5

Actionability

Every step names a concrete file path and named function, plus copy-paste-ready Go (add*Config pattern) and NGINX template examples covering the common cases.

5 / 5

Workflow Clarity

13 strictly ordered steps with an explicit dependency note and embedded test checkpoints (Steps 4, 10, 13), but no explicit validate-then-retry feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist; the single body is well-sectioned into steps, gotchas, and patterns. Content is appropriately placed though the pattern blocks could optionally be split into reference files.

4 / 5

Total

18

/

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 specific, well-triggered description that clearly answers both what and when with concrete policy-name triggers. Minor room to broaden specificity beyond the single add-policy action.

DimensionReasoningScore

Specificity

Names a concrete action ('adding a new Policy CRD type to NIC') and enumerates many specific policy types, but it is a single action rather than multiple distinct actions.

4 / 5

Completeness

Explicitly states both what it does ('Step-by-step checklist for adding a new Policy CRD type') and when to use it ('Use when implementing a new policy like...').

5 / 5

Trigger Term Quality

Strong natural keyword coverage via concrete policy names (RateLimit, JWTAuth, WAF, CORS) a user would actually say; no file extensions, though the domain is internal CRDs.

4 / 5

Distinctiveness Conflict Risk

Clear NIC policy-CRD niche with distinct triggers (specific policy names, 'Policy CRD type'); minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nginx/kubernetes-ingress
Reviewed

Table of Contents

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.