qa-testing

Skill do QA Engineer para testes unitarios, integracao e E2E. Use quando precisar escrever testes, validar regressao, revisar cobertura, configurar estrategia de QA, ou evidenciar qualidade antes de release. Trigger em: "teste", "test", "QA", "Playwright", "Vitest", "Jest", "E2E", "coverage", "mock", "fixture", "regressao", "teste de integracao", "testing library".

1.29x

Quality

76%

Does it follow best practices?

Impact

80%

1.29x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/05-qa-testing/SKILL.md

Quality

Content

57%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 actionable and well-structured with useful tables and real executable code, but it is padded with concepts Claude already knows and references numerous files that are absent from the bundle. The core workflow also lacks explicit validation/verification feedback loops.

Suggestions

Trim concept explanations Claude already knows (mutation mechanics, the inspiration blockquote, and the Anti-Rationalization table) to improve token efficiency.

Add explicit validation/verification checkpoints to the core QA workflow (run tests -> on failure fix and re-run -> only approve when green), so batch operations have a feedback loop.

Resolve or remove references to bundle files that do not exist (policies/*.md, docs/skill-guides/qa-testing.md, personas/test-engineer.md, GLOBAL.md), or move that material into actual reference files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and tight bullets, but it re-explains mutation-testing mechanics Claude already knows, includes an inspiration blockquote, and restates familiar QA truisms in an Anti-Rationalization table — several unnecessary explanations that could be trimmed.	3 / 5
Actionability	Provides executable code (SQLite WAL cleanup snippet), install commands (pip install mutmut, @stryker-mutator/core), and a numbered workflow with npx stryker run and thresholds — concrete guidance with only minor gaps such as no full config example.	4 / 5
Workflow Clarity	The mutation-testing section has a clear numbered sequence, but the core QA workflow lacks explicit validation/verification checkpoints and error-recovery feedback loops; per the batch/destructive-operations cap this caps clarity at 3 even though a CI threshold gate is mentioned.	3 / 5
Progressive Disclosure	Good section structure and a well-signaled, real one-level reference (references/playwright-patterns.md with a content summary), but many referenced paths (policies/.md, docs/, personas/*, GLOBAL.md) do not exist in the bundle, creating dangling navigation that weakens discoverability.	3 / 5
	Total	13 / 20 Passed

Description

95%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 strong: it states the skill's purpose, gives an explicit 'Use quando' trigger clause, and enumerates natural trigger terms including synonyms and tool names. The only gap is that the listed actions are moderately high-level rather than tool-specific verbs.

Dimension	Reasoning	Score
Specificity	Lists several concrete QA actions (escrever testes, validar regressao, revisar cobertura, configurar estrategia de QA, evidenciar qualidade) but they remain somewhat high-level without tool-specific verbs, fitting the 'several specific actions; minor gaps' anchor rather than fully comprehensive.	4 / 5
Completeness	Explicitly answers both 'what' (testes unitarios, integracao e E2E) and 'when' (Use quando precisar... antes de release) with a concrete 'Trigger em:' trigger phrase list.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural terms including synonyms (teste/test, regressao), tool names (Playwright, Vitest, Jest), and methodology terms (coverage, mock, fixture, testing library) users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear QA-testing niche with distinct triggers and minimal overlap risk; voice is impersonal third person ('Use quando...') so no voice penalty applies.	5 / 5
	Total	19 / 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: felvieira/claude-skills-fv
Path: skills/05-qa-testing/SKILL.md
Commit: f3492ef

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