CtrlK
BlogDocsLog inGet started
Tessl Logo

nic-testing

Testing patterns for NIC including Go table-driven tests, snapshot tests, and Python integration tests. Use when writing unit tests, snapshot tests, policy tests, template tests, Helm tests, or pytest integration tests for the Ingress Controller.

68

Quality

81%

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

75%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 well-structured, actionable testing reference that gives concrete commands and example patterns for Go, Helm, and Python tests. It is concise and clearly navigable, with only minor gaps in executable completeness and explicit validation checkpoints.

DimensionReasoningScore

Conciseness

Lean, dense reference with no over-explanation of basic concepts; a few inline numbering comments and the dual naming-convention explanation could be tightened slightly, keeping it just below fully efficient.

4 / 5

Actionability

Provides copy-paste-ready make targets and largely executable Go/Python examples; the Go table-driven example uses placeholder cases and a couple of helper calls are unexpanded, leaving minor gaps.

4 / 5

Workflow Clarity

The Python test pattern is a clear numbered sequence (create policy, patch VS, assert, cleanup) and the Gotchas act as guardrails with implicit validation (snapshot tests fail otherwise); lacks an explicit validate-before-proceed loop, so not a 5.

4 / 5

Progressive Disclosure

Well-organized into clear section headers with repo paths for deeper context and no bundle files needed; all content is inline and reasonably placed, though no file-level split is used.

4 / 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, third-person description that clearly states capabilities and gives an explicit 'Use when' trigger clause tied to concrete test types. It is specific, distinctive, and complete with only minor keyword-coverage gaps.

DimensionReasoningScore

Specificity

Lists several concrete testing patterns ('Go table-driven tests, snapshot tests, and Python integration tests') plus a broad trigger set; minor gaps in coverage keep it just below comprehensive.

4 / 5

Completeness

Explicitly answers both what ('Testing patterns for NIC including...') and when ('Use when writing unit tests... for the Ingress Controller') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural developer terms ('unit tests, snapshot tests, policy tests, template tests, Helm tests, or pytest integration tests'), with a few synonyms present but not exhaustive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (NIC / Ingress Controller testing) with distinct triggers; minimal overlap risk with unrelated 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.