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.
Install with Tessl CLI
npx tessl i github:softaworks/agent-toolkit --skill qa-test-planner76
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 95%
↑ 1.58xAgent success when using this skill
Validation for skill structure
Discovery
50%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 excels at specificity with concrete QA deliverables and has a distinctive niche that reduces conflict risk. However, it critically lacks any 'Use when...' guidance, making it incomplete for skill selection purposes. The trigger terms are adequate but could include more natural variations users might say.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user needs help with QA testing, writing test cases, creating test plans, documenting bugs, or validating designs against Figma mockups.'
Include common user variations such as 'QA', 'quality assurance', 'testing strategy', 'test coverage', or 'software testing' to improve trigger term coverage.
| 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 capability with Figma MCP. | 3 / 3 |
Completeness | Clearly describes WHAT it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Contains relevant keywords like 'test plans', 'test cases', 'regression test', 'bug reports', 'QA engineers', 'Figma', 'design validation'. 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 domain with specific deliverables (test plans, test cases, bug reports) and unique Figma integration. Unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured QA skill with strong actionability through concrete templates and examples. The progressive disclosure using collapsible sections is effective, and workflow clarity is excellent with explicit checklists and pass/fail criteria. The main weakness is verbosity - the ASCII diagram, motivational quotes, and some redundant explanations could be trimmed to improve token efficiency.
Suggestions
Remove the ASCII workflow diagram and motivational quotes at the end - they add little value for Claude
Consolidate the 'How It Works' section into the Quick Start or remove it entirely as the workflow is self-evident from the commands and deliverables sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary content like ASCII workflow diagrams, motivational quotes at the end, and verbose explanations in the deep dive sections that could be trimmed. The quick reference table and commands section are well-organized but the overall document is longer than necessary. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for test cases, bug reports, and test plans. The examples section includes fully detailed test case formats with specific expected results, and the deep dive sections contain executable templates that QA engineers can directly use. | 3 / 3 |
Workflow Clarity | Clear multi-phase QA process workflow with explicit checkpoints (Planning → Test Design → Execution → Reporting). The verification checklists provide validation steps, and the regression testing section includes clear pass/fail criteria and execution order with explicit 'stop and fix' guidance. | 3 / 3 |
Progressive Disclosure | Excellent use of collapsible details sections for deep dives, keeping the main content scannable. References to external files (test_case_templates.md, bug_report_templates.md, etc.) are clearly signaled and one level deep. Quick start and quick reference sections provide immediate value before detailed content. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (758 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
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.