CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

netalertx-settings-management

Manage NetAlertX configuration settings. Use this when asked to add setting, read config, get_setting_value, ccd, or configure options.

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/settings-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 lean, well-sectioned guide with concrete code snippets and a useful PR checklist, but the central plugin-settings workflow — the path the skill itself says to prefer — is described only in prose with no config.json example and no syntax for types, categories, or validation. The runtime lifecycle diagram and source-of-truth rules are clear strengths.

Suggestions

Add a minimal plugin config.json settings example showing the actual field syntax (type, default_value, category, name/description, validation) so the preferred plugin-first path is executable rather than prose-only.

Enumerate the valid categories and the available validation fields (min/max, regex, allowed options) — the guide repeatedly says to use them but never defines their syntax.

Add a short verification step after adding a setting (e.g. how to confirm it renders in the Settings UI or round-trips through get_setting_value()) to close the workflow with a feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean: imperative one-liners, code snippets, and tables with no padding or explanation of concepts Claude already knows. Only minor trimming is needed — 'never read app.conf directly' and the defaults rule are each stated twice (Quick Reference vs §12, §6 vs checklist). Matches anchor 4 rather than 5 due to that small duplication.

4 / 5

Actionability

Strong concrete material exists (get_setting_value()/getSetting()/ccd() snippets, file-path table, naming examples, localization JSON, lifecycle diagram), but the primary plugin path has no example at all — 'define in the plugin's config.json under the settings key' shows no sample object, and no syntax is given for the type, category, or validation fields referenced throughout. Matches anchor 3 ('missing key details') rather than 4 because the main workflow lacks executable specifics.

3 / 5

Workflow Clarity

Sections follow a sensible development order (find pattern → name → category → type → validation → defaults → localization → lifecycle) and the PR checklist serves as an explicit verification gate. Not 3 because checkpoints are explicit; not 5 because the sequence is implicit rather than framed as steps and there is no validate-then-fix feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist; the ~180-line body is well-sectioned with a Quick Reference up front and clearly labeled external doc links. The 16-section Development Guide could arguably live in a separate reference file, which keeps this at anchor 4 rather than 5 ('good structure, minor organization gaps').

4 / 5

Total

15

/

20

Passed

Description

75%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 focused, third-person description with a fully explicit 'Use this when...' trigger clause and low conflict risk. Its main weaknesses are a generic one-verb capability statement and a trigger list that omits common phrasings like 'settings', 'change a setting', or 'app.conf'.

Suggestions

Expand the capability statement into concrete actions, e.g. 'Add, read, and update NetAlertX configuration settings (core settings via ccd(), plugin settings via config.json, reads via get_setting_value())'.

Add natural trigger synonyms users would say, such as 'settings', 'change/update a setting', 'configuration', 'app.conf', or 'plugin settings'.

Briefly distinguish core vs plugin setting workflows in the description so the 'what' is comprehensive rather than a single generic verb.

DimensionReasoningScore

Specificity

The 'what' is a single generic verb ('Manage NetAlertX configuration settings', akin to 'Processes PDF files'), but the when-clause explicitly lists concrete actions ('add setting, read config, get_setting_value, ccd, or configure options'), lifting it between anchors 2 and 3. It cannot reach 4 because the capability statement itself remains minimal and coverage is thin (no mention of updating/removing settings or plugin vs core distinction).

3 / 5

Completeness

Explicitly answers both what ('Manage NetAlertX configuration settings') and when ('Use this when asked to add setting, read config, get_setting_value, ccd, or configure options') with concrete trigger phrases, in third person. Matches the anchor-5 pattern; not 4 because the when-clause is fully explicit rather than only implied or partial.

5 / 5

Trigger Term Quality

Includes natural phrases ('add setting', 'read config', 'configure options') plus API names ('get_setting_value', 'ccd') a developer might paste, but misses common variations and synonyms such as 'settings', 'change/update a setting', 'configuration', 'app.conf', or 'plugin settings'. Matches anchor 3 rather than 4 because several everyday phrasings are absent and 'ccd' is internal jargon.

3 / 5

Distinctiveness Conflict Risk

Names a specific application (NetAlertX) and its internal API functions as triggers, giving it a clear niche with minimal overlap risk against generic settings- or config-related skills.

5 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

netalertx/NetAlertX

Path

.github/skills/settings-management/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.