CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

about-netalertx-project-structure

Navigate the NetAlertX codebase structure. Use this when asked about file locations, project structure, where to find code, or key paths.

74

Quality

93%

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

100%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.

The body is a lean, high-signal reference: concrete paths organized in clearly labeled tables, with only genuinely project-specific knowledge beyond the tables. It fully serves the description's promise of codebase navigation.

DimensionReasoningScore

Conciseness

The body is almost entirely path tables plus project-specific facts Claude cannot know (PHP+Nginx frontend, Python backend, supercronic scheduler, NETALERTX_* env vars). No padding or explanation of known concepts — every token earns its place.

5 / 5

Actionability

Exact, copy-paste-ready paths cover all common lookup cases (backend entry, API server, plugins, device model, DB, config, logs, docs). Per the rubric's scoring notes, an instruction-only skill is not penalized for lacking code when the guidance is this concrete.

5 / 5

Workflow Clarity

This is a single-purpose lookup skill (~54 lines) where the one action — find the right path — is unambiguous and the content is organized by category; the simple-skill exception applies. No destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

Well-organized sections (Key Paths, Architecture, Runtime Paths, Environment Variables, Documentation) with no bundle files needed, and the docs/ pointers are one-level-deep, clearly signaled references within the project. Easy to navigate.

5 / 5

Total

20

/

20

Passed

Description

82%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 description with an explicit 'Use when...' trigger clause and a well-scoped, unambiguous niche. The main weakness is the thin 'what' clause — a single generic verb ("Navigate") rather than several concrete capabilities.

Suggestions

Expand the what-clause with 1-2 more concrete actions, e.g. "Locate backend, frontend, plugin, database, and config paths in the NetAlertX codebase" instead of the single generic verb "Navigate".

Add common trigger synonyms such as "directory structure", "repo layout", or "where a file/component lives" to broaden natural keyword coverage.

Mention the runtime/data paths (config, DB, logs) in the description so users asking about runtime file locations also match this skill.

DimensionReasoningScore

Specificity

"Navigate the NetAlertX codebase structure" names a specific domain with a single concrete action, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not score 4 because no list of several specific actions is given, and not score 2 because the domain is precise rather than generic.

3 / 5

Completeness

It explicitly answers both what ("Navigate the NetAlertX codebase structure") and when ("Use this when asked about file locations, project structure, where to find code, or key paths") with four concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"file locations, project structure, where to find code, or key paths" provides good natural-phrase coverage a user would actually say. Not 5 because common variations like "directory structure", "repo layout", or "where things live" are missing.

4 / 5

Distinctiveness Conflict Risk

The description targets a clear niche (the NetAlertX codebase specifically) with distinct triggers, so the risk of firing for an unrelated skill is minimal.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

netalertx/NetAlertX

Path

.github/skills/project-navigation/SKILL.md

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.