testing-workflow

Read before running tests. Detailed instructions for single, standard unit tests (fast), full suites (slow), handling authentication, and obtaining the API Token. Tests must be run when a job is complete.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/testing-workflow/SKILL.md

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.

The body is highly actionable with executable commands and well-sequenced procedures including validation checkpoints. It is concise overall, with one verbose pitfall section and a single-file structure that could optionally offload its deepest detail.

Suggestions

Tighten the sys.modules pitfall: lead with the symptom and fix pattern, and trim the general explanation of how sys.modules caching and pytest collection work.

Add an explicit validate-then-fix loop for the primary test run (e.g. run suite -> if failures in changed code, fix and re-run) so the main workflow has a feedback checkpoint.

Consider moving the extended sys.modules debugging pattern into a references/ file referenced one level deep, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and brief directives, but the 'Pitfall: sys.modules Stubbing' section explains process-wide caching mechanics Claude already knows, which could be trimmed without losing the valuable symptom/fix pattern.	4 / 5
Actionability	Every procedure ships copy-paste-ready, executable commands (pytest invocations, the setup.sh script, the API_TOKEN one-liner) plus a complete code fix pattern for the sys.modules pitfall, covering the common cases.	5 / 5
Workflow Clarity	Sequences are clear and numbered with real checkpoints (environment check, pre-existing-failures check, troubleshooting feedback loop for 403/empty tokens), but the main run-test flow lacks an explicit validate-then-fix loop tied to the user's own changes.	4 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and no nested references, but at over 50 lines the detailed sys.modules pitfall could plausibly live in a separate reference, leaving minor organization gaps versus an ideal split.	4 / 5
	Total	17 / 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.

The description is concrete and covers multiple specific testing actions with reasonable trigger terms and explicit (if slightly informal) usage guidance. It is well above baseline but stops short of comprehensive, polished trigger phrasing.

Suggestions

Add a dedicated 'Use when...' clause with concrete trigger phrases (e.g. 'Use when finishing a coding job, before marking work complete, or when the user asks to run tests').

Include common synonyms and the tool name (e.g. 'pytest', 'test suite') to broaden natural trigger coverage.

Tighten the opening 'Read before running tests.' into the action list so the 'what' reads as a single cohesive capability statement.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'single, standard unit tests (fast), full suites (slow), handling authentication, and obtaining the API Token' — with only minor coverage gaps, matching the 'several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	It states the 'what' ('Detailed instructions for...') and an explicit 'when' ('Tests must be run when a job is complete'), but the trigger guidance is not a crisp 'Use when...' clause with concrete trigger phrases, keeping it just below a 5.	4 / 5
Trigger Term Quality	Natural terms like 'running tests', 'unit tests', 'fast', 'full suites', and 'API Token' are present, but common synonyms (e.g. 'pytest', 'test suite') are missing, so it sits above 'some relevant keywords' but below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The API Token / authentication framing ties it to a specific project context, making it mostly distinct with only minor overlap risk against generic testing skills, short of a fully clear niche.	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: .gemini/skills/testing-workflow/SKILL.md
Commit: 014b960

Reviewed: 6 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.