Name: netalertx-testing-workflow
Rating: 67.2 (1 reviews)
Author: netalertx

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 strong, actionable testing-workflow body with concrete code, a mandatory pre-flight validation checkpoint, and a genuinely non-obvious project-specific pitfall. The main weakness is minor over-explanation of pytest/sys.modules fundamentals.

Suggestions

Trim the general explanation of how sys.modules and pytest collection work in the Pitfall section, keeping only the project-specific failure mode and fix pattern.

Give concrete invocation syntax for runTests (e.g. exact parameter examples) instead of prose like "invoke runTests with the test file path".

Fix the typo in the PYTHONPATH comment ("/wprkspaces" → "/workspaces").

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete code and commands, but the sys.modules pitfall explains general pytest/sys.modules mechanics Claude already knows ("a single process-wide cache shared by the whole pytest session", "pytest imports all test files during collection"), which could be trimmed.	4 / 5
Actionability	Guidance is fully executable: a copy-paste API_TOKEN snippet, a concrete docker buildx command, a complete sys.modules stub/pop fix pattern, and a reproduce command; the runTests invocations are described in prose but the code examples cover the common cases.	5 / 5
Workflow Clarity	The mandatory Pre-Flight Check is an explicit validation checkpoint and the 403 troubleshooting section has verify steps, but the document is a collection of reference sections rather than one coherent multi-step workflow with feedback loops throughout.	4 / 5
Progressive Disclosure	No bundle files exist and the ~107-line body is well organized into clearly headed sections; it is over the 50-line simple-skill threshold so the well-organized-only 5 anchor does not apply, and the detailed sys.modules pitfall is appropriately inline rather than nested.	4 / 5
	Total	17 / 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-constructed description that clearly answers both what it does and when to use it, with natural trigger terms and a project-specific niche. Specificity is the weakest dimension since it names only two actions.

Dimension	Reasoning	Score
Specificity	"Run and debug tests" names the testing domain with two concrete actions (run, debug), but does not enumerate several specific actions, matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	It states what ("Run and debug tests in the NetAlertX devcontainer") and an explicit when with concrete trigger phrases ("Use this when asked to run tests, check test failures, debug failing tests, or execute pytest"), matching the both-what-and-when anchor.	5 / 5
Trigger Term Quality	"run tests, check test failures, debug failing tests, or execute pytest" gives good natural keyword coverage including the tool name pytest; a few common synonyms like "fix tests" or "test suite" are missing, so it sits below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The "NetAlertX devcontainer" binding gives it a clear niche, but the trigger phrases (run tests, execute pytest) are generic enough to overlap with a general testing skill, so it is mostly distinct with minor overlap rather than minimal conflict.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 257431b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.