CtrlK
BlogDocsLog inGet started
Tessl Logo

netalertx-code-standards

NetAlertX coding standards and conventions. Use this when writing code, reviewing code, or implementing features.

64

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/code-standards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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, code-rich standards skill with excellent concrete examples. Its main weakness is duplication between the opening bullet list and the sectioned rules, and the absence of a structured workflow despite process-oriented hints.

Suggestions

Remove the duplicated rules between the opening bullet list and the sectioned headers (e.g., 500 LOC, DRY, DB access) so each standard appears once, ideally in the sectioned body with the bullet list as a brief index.

Turn the process-oriented bullets ('ask me to review before each next step', 'prepare implementation plan') into an explicit numbered workflow with validation checkpoints for PR/review cycles.

Consider moving long examples (the sys.modules stubbing pattern, the test-helpers import block) into a reference file and linking to it, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Mostly lean bullet standards with concise code examples, but the introductory bullet list duplicates the later sectioned rules (e.g., 500 LOC and DRY appear twice), which could be trimmed.

4 / 5

Actionability

Fully executable guidance with real import paths, helper locations, and copy-paste code (normalize_mac, timeNowUTC, subprocess timeouts) plus correct/wrong MAC examples covering common cases.

5 / 5

Workflow Clarity

Standards are listed clearly but there is no sequenced multi-step workflow with validation checkpoints; process hints like 'ask me to review before each next step' are mentioned but never structured into an explicit workflow.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and no external bundle files to manage, though the top bullet list and later sections overlap instead of one cleanly pointing to the other.

4 / 5

Total

16

/

20

Passed

Description

78%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 clear, trigger-rich description with a distinct project niche. It loses specificity for using generic action verbs rather than naming the concrete standards the skill enforces.

DimensionReasoningScore

Specificity

Names the domain (NetAlertX coding standards) and a few actions ('writing code, reviewing code, or implementing features'), but the actions are generic high-level verbs rather than the concrete standards the skill actually covers (MAC normalization, UTC timestamps, DB helpers).

3 / 5

Completeness

Explicitly answers both what ('NetAlertX coding standards and conventions') and when ('Use this when writing code, reviewing code, or implementing features') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would say ('writing code, reviewing code, implementing features') are present with decent coverage, though synonyms and a NetAlertX-specific trigger are missing.

4 / 5

Distinctiveness Conflict Risk

The NetAlertX-specific niche is clearly bounded, though 'writing/reviewing code' triggers carry minor overlap risk with other generic coding skills.

4 / 5

Total

16

/

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
netalertx/NetAlertX
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.