qa-test-management
Automatic QA test lifecycle management, naming conventions, and directory structure. Use when creating, organizing, or tracking QA tests to ensure proper naming, directory structure, and status transitions.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill qa-test-management81
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/skillValidation for skill structure
Discovery
75%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 has good structure with explicit 'Use when...' guidance and a clear domain focus on QA test management. However, it lacks specificity in describing concrete actions (what naming conventions? what directory structures?) and could benefit from more natural trigger terms that users would actually say when needing this skill.
Suggestions
Add specific concrete actions like 'generates test file names following [pattern], creates test directories under /tests/, tracks test status from draft to approved'
Include more natural trigger term variations such as 'test files', 'test organization', 'test naming', 'test folders', 'test workflow', or 'test structure'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (QA test lifecycle) and mentions actions like 'creating, organizing, or tracking QA tests' with aspects like 'naming conventions' and 'directory structure', but doesn't list multiple concrete specific actions (e.g., what specific naming conventions, what directory structures, what status transitions). | 2 / 3 |
Completeness | Clearly answers both what ('Automatic QA test lifecycle management, naming conventions, and directory structure') and when ('Use when creating, organizing, or tracking QA tests to ensure proper naming, directory structure, and status transitions') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'QA tests', 'naming conventions', 'directory structure', and 'status transitions', but misses common variations users might say like 'test files', 'test organization', 'test naming', 'test folders', or 'test workflow'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on QA test lifecycle management with distinct triggers around naming conventions and directory structure for tests; unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill for QA test management with clear workflows and concrete templates. Its main weakness is moderate verbosity - the content could be tightened by removing some redundancy and potentially splitting detailed reference material into separate files. The lifecycle management and validation checklists are particularly well-executed.
Suggestions
Remove redundant directory/location information that appears in both the tree structure and the status table
Consider moving 'Metrics to Track' and detailed 'Archival Rules' to a separate REFERENCE.md file, keeping only essential guidance in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (e.g., the directory structure is shown twice - once in the tree and again in the status table). Some sections like 'Priority Definitions' and 'Metrics to Track' add value but could be more compact. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for file naming, metadata blocks, execution logs, and traceability tables. The checklist for activation and archival metadata are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Clear lifecycle sequence (DRAFT → ACTIVE → EXECUTED → ARCHIVED) with explicit transition criteria. The 'Quality Checks Before Activation' checklist serves as a validation checkpoint, and status transitions are well-defined with conditions. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single file. For a skill of this length (~150 lines), some content like 'Metrics to Track' or detailed archival rules could be split into reference files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.