CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

netalertx-testing-workflow

Run and debug tests in the NetAlertX devcontainer. Use this when asked to run tests, check test failures, debug failing tests, or execute pytest.

Quality

81%

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 tight, highly actionable skill body: every section carries project-specific knowledge (devcontainer PYTHONPATH, token retrieval, test-image rebuild timings, a subtle sys.modules stubbing pitfall with a complete fix pattern). Scores are capped at 4 by implicit runTests parameters, no post-run verification step, and the long inline pitfall section that could be split into a reference.

Suggestions

Specify the runTests tool's concrete invocation forms (exact parameter names/values) the way the pytest and docker commands are given, so every instruction is copy-paste ready.

Add a short post-run verification step (e.g., how to confirm the run succeeded and read the failure report) to close the workflow's feedback loop.

Move the sys.modules stubbing pitfall to references/pitfalls.md with a one-line pointer, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense with project-specific facts Claude cannot infer (PYTHONPATH layout, ~30s/~90s build timings, the process-wide sys.modules leak mechanism) and explains nothing Claude already knows. Minor trimming is possible — e.g., the eight-line PYTHONPATH bullet list could be compressed — keeping it at anchor 4 rather than 5.

4 / 5

Actionability

Mostly executable guidance: a runnable `get_setting_value("API_TOKEN")` snippet, a complete `_stub`/unstub code pattern, concrete `docker buildx build` and `pytest file1 file2 -v` commands. It is not a 5 because 'invoke runTests without file filter / with the test file path' leaves the tool's actual parameters implicit.

4 / 5

Workflow Clarity

The MANDATORY pre-flight check ('gather current failure information... only then proceed') is an explicit validation checkpoint, and the 403 troubleshooting section plus the cross-file pollution reproduction command provide feedback loops for error recovery. It stops short of anchor 5 because there is no step for verifying or interpreting results after a test run, and the 'Running Tests' options are a loose bullet list rather than a sequenced flow.

4 / 5

Progressive Disclosure

Sections are clearly headed and appropriately ordered (pre-flight, running, environment, auth, troubleshooting, pitfall) with no nested references. It is not a 5 because the ~45-line sys.modules pitfall section is substantial inline content that could live in a one-level-deep reference file, and no external organization is used at all for a body over 100 lines.

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 well-formed description with an explicit 'Use this when' trigger clause and natural trigger terms, clearly scoped to the NetAlertX devcontainer. Its main gaps are limited action specificity and missing common synonyms such as 'unit tests' or 'test suite'.

Suggestions

Broaden the action list beyond 'run and debug' to match the body's actual coverage, e.g. 'Run, debug, and triage test failures, retrieve API tokens for authenticated tests, and rebuild the test image'.

Add common trigger synonyms such as 'unit tests', 'test suite', or 'CI failures' to the 'Use this when' clause to improve recall.

Consider naming the pytest/VS Code test tooling explicitly in the what-clause so it reads as distinct from a generic pytest skill even when the project name is truncated.

DimensionReasoningScore

Specificity

"Run and debug tests in the NetAlertX devcontainer" names the domain and exactly two concrete actions (run, debug), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because it does not list several specific actions (e.g., checking failures, rebuilding the test image, handling auth in tests — capabilities the body actually covers).

3 / 5

Completeness

The description explicitly answers both questions: "Run and debug tests in the NetAlertX devcontainer" (what) and "Use this when asked to run tests, check test failures, debug failing tests, or execute pytest" (when, with concrete trigger phrases). This is a direct match for the anchor-5 example structure.

5 / 5

Trigger Term Quality

"run tests, check test failures, debug failing tests, or execute pytest" provides good natural keyword coverage a user would actually say. It falls short of anchor 5 because common variations like "unit tests", "test suite", or "CI" are missing.

4 / 5

Distinctiveness Conflict Risk

"NetAlertX devcontainer" scoping gives it a clear niche with mostly distinct triggers, but the fairly generic phrases "run tests" and "execute pytest" carry minor overlap risk with any general testing/pytest skill. It is not a 5 because the triggers alone (without the project qualifier) would not be fully distinctive.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

netalertx/NetAlertX

Path

.github/skills/testing-workflow/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.