CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

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 content is highly actionable with executable commands and useful validation/troubleshooting feedback loops. Tightening conciseness by removing the duplicated final line and consolidating the scattered checkpoints would lift it further.

Suggestions

Remove the duplicated final line ('Verify Python can read it: ...'), which already appears in the Authentication & Environment Reset section.

Consolidate the validation checkpoints (pre-existing failures, 403/empty-token troubleshooting) into a single ordered 'Verify results' sequence for a clearer end-to-end workflow.

Trim minor prose such as the rebuild-time notes or fold them into the Docker command block to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and mostly executable commands with little padding, though the duplicated final token-retrieval line and a few prose notes could be trimmed.

4 / 5

Actionability

Commands are fully executable and copy-paste ready (pytest invocations, setup.sh, token retrieval), covering the common test-running cases concretely.

5 / 5

Workflow Clarity

Numbered auth-reset steps with a stabilization wait and a troubleshooting feedback loop are clear, and a pre-existing-failures checkpoint exists, but checkpoints are scattered across sections rather than one cohesive sequence.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers and no nested references is appropriate for this scope, though minor ordering/organization gaps remain (e.g. the stray duplicated line at the end).

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 specific and actionable, naming concrete test-related tasks plus a clear run-when-complete trigger. It would benefit from an explicit 'Use when...' clause with sharper trigger phrases to push completeness and distinctiveness higher.

Suggestions

Add an explicit 'Use when...' clause listing natural user triggers such as 'run tests', 'run the test suite', or 'verify changes with pytest'.

Include common synonyms/file markers (e.g. 'pytest', 'test suite') to broaden trigger coverage.

Tighten the 'when' guidance to concrete moments (e.g. 'after code changes, before reporting a task complete') rather than the generic 'when a job is complete'.

DimensionReasoningScore

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.

4 / 5

Completeness

Clearly states what the skill does and gives a 'when' ('Tests must be run when a job is complete'), though the trigger could be more explicit with concrete user phrases.

4 / 5

Trigger Term Quality

Natural terms like 'tests', 'unit tests', 'full suites', and 'API Token' are present, but a few common synonyms (e.g. 'pytest', 'test suite') are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a distinct testing-workflow niche with specific triggers (auth, API Token), with only minor overlap risk against generic test-running skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
netalertx/NetAlertX
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.