testing-workflow

Comprehensive testing workflow orchestrating functional testing, example validation, integration testing, and usability assessment. Sequential workflow for complete skill testing from examples through scenarios to integration validation. Use when conducting thorough testing, pre-deployment validation, ensuring skill functionality, or comprehensive quality checks.

Quality

65%

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

Quality

Content

46%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 lays out a clear, well-structured testing workflow but is held back by vague execution guidance (no commands for invoking component skills) and the absence of an explicit error-recovery loop. Triple restatement of the four steps also dilutes conciseness.

Suggestions

Add concrete invocation commands or syntax for skill-tester and skill-validator in each step so the guidance is executable, not just descriptive.

Add an explicit feedback loop (e.g., 'if Step 1 examples fail, debug and re-run before proceeding to Step 2') to formalize validation checkpoints.

Remove the redundancy between the Overview workflow list, the detailed Testing Workflow section, and the Quick Reference table — keep one detailed view plus a compact reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept over-explanation, but the four steps are restated three times (Overview list, detailed Testing Workflow section, and Quick Reference table), which is unnecessary repetition that could be tightened.	3 / 5
Actionability	Steps give high-level direction ('Extract and execute all examples', 'Run skill-validator') with time estimates and pass criteria, but provide no concrete commands or invocation syntax for the referenced component skills, leaving the specific execution path undefined.	2 / 5
Workflow Clarity	A clear four-step sequence with per-step pass criteria and a final validation check is present, but there is no explicit error-recovery/feedback loop (e.g., 'if examples fail, fix and re-run'), so checkpoints remain largely implicit for this batch testing operation.	3 / 5
Progressive Disclosure	Single-file skill with well-organized sections (Overview, When to Use, Testing Workflow, Quick Reference) and no external references needed; structure is clear though the modest length and triple repetition keep it just short of the lean ideal.	4 / 5
	Total	12 / 20 Passed

Description

83%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 states both capabilities and triggering contexts in third person. It is specific and actionable, with only minor gaps in trigger synonym coverage and a small overlap risk from the generic term 'testing'.

Dimension	Reasoning	Score
Specificity	Names several concrete testing actions ('functional testing, example validation, integration testing, and usability assessment') but the actions remain testing-category labels rather than fully comprehensive concrete operations, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('orchestrating functional testing, example validation, integration testing, and usability assessment') and when ('Use when conducting thorough testing, pre-deployment validation...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-trigger coverage with 'thorough testing, pre-deployment validation, ensuring skill functionality, comprehensive quality checks', but misses common synonyms like 'QA', 'test this skill', or 'validation' as a standalone phrase.	4 / 5
Distinctiveness Conflict Risk	The skill-testing niche is mostly distinct with clear triggers, but the broad word 'testing' carries minor overlap risk with general testing or QA skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/testing-workflow/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.