testing-qa

Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.

Quality

35%

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-qa/SKILL.md

Quality

Content

21%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a table of contents or orchestration index that delegates everything to other skills without providing any concrete, actionable guidance itself. It lacks executable code, specific commands, configuration examples, or meaningful workflow details. The repetitive phase structure adds bulk without substance, and the generic action items ('Write unit tests', 'Configure mocking') tell Claude nothing it doesn't already know.

Suggestions

Add concrete, executable examples for at least the core phases (e.g., a sample pytest configuration, a Playwright test script, a CI pipeline YAML snippet) instead of only delegating to other skills.

Replace vague action items like 'Write unit tests' and 'Set up test fixtures' with specific, actionable steps including actual commands and code.

Add validation checkpoints and feedback loops, especially for quality gates (e.g., 'Run `pytest --cov` and verify coverage report shows >80% before proceeding').

Eliminate the repetitive 'Copy-Paste Prompts' sections that just say 'Use @skill-name to do X' — either provide real prompts with context or remove them entirely to reduce bloat.

Dimension	Reasoning	Score
Conciseness	The skill is heavily padded with repetitive structure (each phase follows the same template of Skills to Invoke, Actions, Copy-Paste Prompts) and the action items are extremely generic ('Write unit tests', 'Set up test fixtures'). Much of this is obvious to Claude and adds no real value. The 'When to Use This Workflow' section is also unnecessary padding.	2 / 5
Actionability	There is no concrete, executable guidance anywhere in this skill. No actual code, no specific commands, no configuration examples. Every 'action' is a vague directive like 'Write unit tests' or 'Configure mocking.' The copy-paste prompts are just 'Use @skill-name to do X' which are meta-references, not actionable instructions.	1 / 5
Workflow Clarity	While there is a rough sequence of 8 phases, the steps within each phase are vaguely defined ('Design integration tests', 'Set up test databases') with no validation checkpoints, no feedback loops, and no error recovery guidance. For a workflow involving testing infrastructure and quality gates, the absence of any concrete validation steps is a significant gap.	2 / 5
Progressive Disclosure	The skill references many other skills by name, which is a form of progressive disclosure. However, there are no bundle files provided, no linked files, and the references are just skill names without clear navigation paths. The structure within the file itself is organized into phases with consistent headings, which provides some navigability.	3 / 5
	Total	8 / 20 Passed

Description

50%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 identifies the testing/QA domain and enumerates several testing categories, but it reads more like a topic list than an actionable skill description. It lacks concrete actions (what does it actually do?), has no 'Use when...' clause to guide skill selection, and the broad scope increases conflict risk with more specialized testing skills.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks to write tests, debug test failures, set up test frameworks, or improve test coverage.'

Replace category labels with concrete actions, e.g., 'Writes unit and integration tests, sets up test frameworks (pytest, jest), automates browser testing with Playwright/Selenium, and generates coverage reports.'

Include common synonyms and file/tool references to improve trigger term quality, e.g., 'end-to-end tests', 'test suite', 'QA', 'spec files', '.test.js', '_test.py'.

Dimension	Reasoning	Score
Specificity	Names the domain (testing/QA) and lists several categories of testing (unit, integration, E2E, browser automation), but these are categories rather than concrete actions. It doesn't describe what it actually does with these (e.g., 'writes test cases', 'runs test suites', 'generates test reports').	3 / 5
Completeness	Has a reasonable 'what' (covers testing and QA workflow across multiple testing types) but completely lacks a 'when' clause. There is no 'Use when...' guidance, which per the rubric should cap completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords like 'unit testing', 'integration testing', 'E2E testing', 'browser automation', and 'quality assurance', which users might naturally say. However, it's missing common synonyms and variations like 'end-to-end', 'test coverage', 'pytest', 'jest', 'Selenium', 'Playwright', 'test suite', or 'QA'.	3 / 5
Distinctiveness Conflict Risk	The description is somewhat specific to testing/QA but is so broad within that domain that it could overlap with more specialized testing skills (e.g., a dedicated browser automation skill or a unit testing skill). The word 'comprehensive' and 'workflow' add to the vagueness.	3 / 5
	Total	12 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/testing-qa/SKILL.md
Commit: debb2ec

Reviewed: 15 hours 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.