qa-test-planner

tessl i github:softaworks/agent-toolkit --skill qa-test-planner

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

79%

Overall

Validation — 69%

Implementation — 85%

Activation — 68%

SKILL.md

Review

Evals

Validation

69%

Warnings & errors only

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (758 lines); consider splitting into references/ and linking	Warning
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	11 / 16 Passed

Implementation

85%

This is a well-structured QA skill with excellent actionability through concrete templates and examples. The progressive disclosure via collapsible sections is effective, and workflow clarity is strong with explicit validation checkpoints. However, the content is somewhat verbose with decorative elements (ASCII diagrams, quotes) and could be more token-efficient.

Suggestions

Remove the ASCII workflow diagram and motivational quotes at the end - they add no actionable value

Consolidate the 'How It Works' section into the Quick Start or remove it entirely, as the process is self-evident from the deliverables

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes unnecessary elements like ASCII workflow diagrams, motivational quotes, and some redundant explanations. The extensive use of collapsible sections helps, but the overall content could be tightened significantly.	2 / 3
Actionability	Provides concrete, copy-paste ready templates for test cases, bug reports, and test plans. The examples include specific field values, expected results, and complete markdown structures that are immediately usable.	3 / 3
Workflow Clarity	Clear multi-phase QA process workflow with explicit checkpoints, pass/fail criteria for regression testing, and verification checklists. The execution tracking section includes clear go/no-go criteria and blocking conditions.	3 / 3
Progressive Disclosure	Excellent use of collapsible details sections for deep dives, keeping the main content scannable. References to external template files are clearly signaled and one level deep. Quick reference table provides immediate overview.	3 / 3
	Total	11 / 12 Passed

Activation

68%

This description has strong specificity with concrete deliverables and a clear QA testing niche that distinguishes it from other skills. However, it lacks an explicit 'Use when...' clause which limits its completeness score, and could benefit from additional natural trigger terms that users might actually say when needing QA assistance.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user needs help with testing, QA, quality assurance, writing test cases, or validating designs against requirements.'

Include additional natural trigger terms users might say: 'testing', 'QA', 'quality assurance', 'test coverage', 'test scenarios', 'acceptance criteria'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Generate comprehensive test plans, manual test cases, regression test suites, and bug reports' - these are distinct, actionable deliverables. Also mentions specific integration (Figma MCP) for a specific purpose (design validation).	3 / 3
Completeness	Clearly answers 'what' (generate test plans, test cases, regression suites, bug reports with Figma integration), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the target audience mention.	2 / 3
Trigger Term Quality	Contains relevant keywords like 'test plans', 'test cases', 'regression test', 'bug reports', 'QA engineers', and 'Figma'. However, missing common variations users might say like 'testing', 'QA', 'quality assurance', 'test coverage', or file extensions.	2 / 3
Distinctiveness Conflict Risk	Clear niche focused on QA/testing artifacts with specific deliverables. The combination of test plans, manual test cases, regression suites, bug reports, and Figma design validation creates a distinct profile unlikely to conflict with general coding or documentation skills.	3 / 3
	Total	10 / 12 Passed

Reviewed

15 days ago

Table of Contents

Validation Implementation Activation

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.