CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

netalertx-plugin-run-development

Create and run NetAlertX plugins. Use this when asked to create plugin, run plugin, test plugin, plugin development, or execute plugin script.

Quality

82%

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 high-quality, information-dense skill body that delivers non-obvious project-specific gotchas (timeout semantics, silent default-value failures, cache identity checks, sanitization rules) with concrete commands and file paths. Its weaknesses are modest: a few trimmable asides, an elided `add_object` signature with no sample manifest, and no error-recovery guidance around the run workflow.

Suggestions

Show a minimal `add_object(...)` call with its actual arguments and a short example `config.json` manifest so the Data Contract and Structure sections are fully copy-paste ready.

Add a brief failure-path note to the run workflow (e.g., what to check if the result file is empty or the script exits non-zero) to close the feedback-loop gap.

Trim explanatory asides like the garbage-collection/id-reuse rationale and "Read this skill document for context and instructions" to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely project-specific knowledge (RUN_TIMEOUT kill semantics, dataType/default_value JSON-literal gotcha, `is`-based cache invalidation, field sanitization), with little padding. A few asides could be trimmed — e.g., the garbage-collection/id-reuse rationale in the `all_plugins` section, "as in the template", and workflow step 1 "Read this skill document for context and instructions" — matching the anchor for efficient content with minor over-explanation rather than fully lean (5).

4 / 5

Actionability

Concrete, runnable guidance throughout: `python3 server/plugins/<code_name>/script.py`, the exact result-file path `/tmp/log/plugins/last_result.<PREF>.log`, a working `Plugin_Objects` import/usage snippet, and precise file paths like `server/plugins/__template`. Minor gaps keep it below fully copy-paste-ready (5): `add_object(...)` arguments are elided and no example `config.json` manifest is shown.

4 / 5

Workflow Clarity

The "Expected Workflow for Running Plugins" is a clear 5-step sequence with concrete commands and an explicit time-critical checkpoint ("Retrieve the result... quickly, as the backend may delete it after processing"), plus a pre-PR checklist section. There is no validate/fix/retry feedback loop for failures (e.g., what to do when the result file is empty or the script errors), so it does not reach the explicit-validation anchor (5).

4 / 5

Progressive Disclosure

No bundle files exist, and the ~100-line body is well-sectioned (Workflow, Structure, Settings, Data Contract, Phases, Formats, PR checklist) with clearly signaled one-level-deep pointers to repo docs (`docs/PLUGINS_DEV.md`, `docs/PLUGINS_IMPORT_BEHAVIOR.md`). Some inline detail (settings gotchas, `all_plugins` caching internals) could arguably move to a reference file, and the skill exceeds the under-50-lines simple-skill case, so it sits at good-structure (4) rather than the ideal split (5).

4 / 5

Total

16

/

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, natural trigger list and a clearly distinct NetAlertX-specific niche. The main weakness is that the what-clause states only two capabilities (create, run) while the trigger list implies more (test), leaving the capability statement slightly under-specified.

Suggestions

Mirror the trigger list in the capability statement, e.g., "Create, run, and test NetAlertX plugins" so the what-clause covers testing as well as creation and execution.

Consider adding one or two natural synonyms such as "debug plugin" or "NetAlertX extension" to the trigger list for broader coverage.

DimensionReasoningScore

Specificity

"Create and run NetAlertX plugins" names the domain and exactly two concrete actions, which matches the anchor for 1-2 concrete actions without comprehensive coverage. The trigger list mentions "test plugin" but testing is not stated as a capability in the what-clause, so it falls short of the several-actions anchors (4-5).

3 / 5

Completeness

It explicitly answers both questions: what ("Create and run NetAlertX plugins") and when ("Use this when asked to create plugin, run plugin, test plugin, plugin development, or execute plugin script") with concrete trigger phrases. This matches the anchor-5 example structure; the thinner what-side is already reflected in the specificity score.

5 / 5

Trigger Term Quality

The trigger list "create plugin, run plugin, test plugin, plugin development, or execute plugin script" covers good natural phrasings users would say, including the variation "plugin development" and "execute plugin script". A few natural terms are missing (e.g., "debug plugin", "NetAlertX extension"), so it does not reach comprehensive synonym coverage (5).

4 / 5

Distinctiveness Conflict Risk

"NetAlertX plugins" carves out a clear product-specific niche with distinct triggers (create/run/test plugin), giving minimal overlap risk with other skills. It is not generic in any dimension that would conflict with unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

netalertx/NetAlertX

Path

.github/skills/plugin-run-development/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.