qa-engineer

Quality assurance specialist - manual testing, test planning

Quality

37%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/qa-engineer/SKILL.md

Quality

Content

52%

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

This skill provides useful, concrete templates for QA documentation but lacks workflow guidance on how and when to apply them. The templates are actionable and well-structured, but the skill reads more like a reference document than operational guidance for conducting QA activities.

Suggestions

Add a workflow section explaining when to use each template and how they connect (e.g., 'After exploratory testing, create bug reports for each finding')

Include validation checkpoints such as 'Before submitting bug report, verify: reproducibility confirmed, severity assessed, screenshots attached'

Remove the persona introduction and closing quote to improve token efficiency

Add guidance on prioritization decisions (when is something P1 vs P2, High vs Medium severity)

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient with templates, but includes unnecessary elements like the Aristotle quote and the persona framing ('You are QA Engineer, the manual testing and quality assurance specialist') that Claude doesn't need.	2 / 3
Actionability	Provides concrete, copy-paste ready templates for test cases, bug reports, and exploratory testing sessions with specific field examples and realistic sample data.	3 / 3
Workflow Clarity	No workflow or process is defined - just templates without guidance on when to use each, how they connect, or any validation/review steps. Missing sequence for how to conduct QA activities.	1 / 3
Progressive Disclosure	Content is organized into clear sections with headers, but everything is inline in one file. For a skill of this size, some content (like detailed templates) could be referenced separately, and there's no navigation to related resources.	2 / 3
	Total	8 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too brief and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient detail to distinguish it from other potential testing or development skills. The description reads more like a job title than a functional skill description.

Suggestions

Add specific concrete actions like 'Creates test plans, writes test cases, executes manual test scenarios, documents defects, performs regression testing'

Include a 'Use when...' clause with explicit triggers such as 'Use when the user needs help with test planning, writing test cases, manual QA processes, or documenting bugs'

Add more natural trigger terms users would say: 'QA', 'test cases', 'bug reports', 'test scenarios', 'regression testing', 'test documentation'

Dimension	Reasoning	Score
Specificity	The description uses vague terms like 'quality assurance specialist' and 'manual testing, test planning' without describing concrete actions. It doesn't specify what actions are performed (e.g., 'create test cases', 'execute test scripts', 'document defects').	1 / 3
Completeness	The description only vaguely addresses 'what' (QA/testing) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('manual testing', 'test planning', 'quality assurance') that users might say, but missing common variations like 'QA', 'test cases', 'bug reports', 'regression testing', 'test scenarios'.	2 / 3
Distinctiveness Conflict Risk	While 'manual testing' and 'test planning' provide some specificity to the QA domain, the description could overlap with automated testing skills or general software development skills without clearer boundaries.	2 / 3
	Total	6 / 12 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: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 4 months 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.