tessl install https://github.com/softaworks/agent-toolkit --skill qa-test-plannergithub.com/softaworks/agent-toolkit
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
Average Score
79%
Content
85%
Description
68%
Generated
Validations
Total score
11/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md is long (758 lines); consider splitting into references/ and linking | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'qa-test-planner' | |
description_field 'description' field is valid (165 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys Unknown frontmatter key(s) found; consider removing or moving to metadata | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Suggestions 2
Total score
11/12| Dimension | 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 |
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
Overall Assessment
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.
Description
Suggestions 2
Total score
10/12| Dimension | 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 |
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'
Overall Assessment
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.