CtrlK
BlogDocsLog inGet started
Tessl Logo

nic-debugging

Debugging and troubleshooting patterns for NIC. Use when diagnosing failures, tracing issues, investigating NGINX reload errors, config generation bugs, or controller sync problems.

69

Quality

84%

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

81%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 debugging reference that uses concrete commands, specific file paths, and clearly sequenced workflows with validation feedback loops. It is lean and avoids concept padding, with only minor organization and directional-step gaps.

DimensionReasoningScore

Conciseness

The body is largely lean — tables, command lists, and concrete paths assume Claude's competence and avoid explaining basics — with only minor prose that could be trimmed, fitting anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

It provides dense concrete, copy-paste-ready commands ("kubectl get vs,vsr,ts,pol -A", "make test", "nginx -t", "kubectl exec <pod> -- cat /etc/nginx/conf.d/<file>") and specific file paths/function names, but blends them with directional steps ("Find the template struct"), leaving minor gaps that cap it at anchor 4.

4 / 5

Workflow Clarity

Multiple clearly sequenced workflows are present — a 7-step Debugging Workflow with explicit Verify and Prevent checkpoints, plus a snapshot-test regenerate feedback loop (update snaps, re-read git diff, confirm) — matching anchor 5's clear sequence with validation and error-recovery loops.

5 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear section headers and no nested references, but it exceeds 50 lines and has no external bundle files to signal, so it lands at anchor 4 (good structure, appropriately placed content) rather than 5.

4 / 5

Total

17

/

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 pairs a clear capability statement with an explicit "Use when" trigger listing concrete failure scenarios. It is distinctive to the NIC domain and well-targeted, with only minor room for synonym/variation coverage.

DimensionReasoningScore

Specificity

The description names the NIC domain and several concrete debugging targets ("diagnosing failures, tracing issues, investigating NGINX reload errors, config generation bugs, or controller sync problems"), which is several specific actions but not the comprehensive discrete-action list of anchor 5.

4 / 5

Completeness

It explicitly answers both "what" ("Debugging and troubleshooting patterns for NIC") and "when" with a concrete "Use when..." trigger clause, matching anchor 5.

5 / 5

Trigger Term Quality

Natural user phrases like "NGINX reload errors", "config generation bugs", "controller sync problems", and "diagnosing failures" give good keyword coverage, but it lacks synonyms or common variations that would reach anchor 5.

4 / 5

Distinctiveness Conflict Risk

The NIC / NGINX Ingress Controller debugging niche has distinct, specific triggers (reload errors, config generation bugs, controller sync problems) with minimal overlap risk against 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.