list-qa-tests

List QA test procedures with status and priority

Quality

47%

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 ./plugins/product-design/skills/list-qa-tests/SKILL.md

Quality

Content

62%

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

This skill provides a well-structured reference for a QA test listing command with clear workflow steps and comprehensive output format documentation. However, it lacks executable code implementations and is verbose with full output examples that inflate token usage. The content describes behavior rather than providing copy-paste ready implementations.

Suggestions

Add executable Python/bash code for directory scanning and file parsing instead of abstract descriptions in the 'Execution Instructions' section

Condense the three output format examples into one primary example with brief notes about format variations, or move detailed format specs to a separate reference file

Replace pseudocode directory structure with actual glob patterns or code snippets that Claude can execute

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes verbose output examples that could be condensed. The three full output format examples (table, list, JSON) take significant space when a single example with brief notes about alternatives would suffice.	2 / 3
Actionability	Provides clear structure and output formats, but lacks executable code. The 'Execution Instructions for Claude Code' section describes what to do abstractly rather than providing actual implementation code for scanning directories, parsing files, or filtering.	2 / 3
Workflow Clarity	The 5-step execution workflow is clearly sequenced (scan → parse → filter → calculate → display). Error handling section covers edge cases. For a read-only listing operation, validation checkpoints aren't critical, and the workflow is unambiguous.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is inline in one file. The extensive output format examples could be moved to a separate FORMATS.md reference. Related commands are mentioned but not linked to actual files.	2 / 3
	Total	9 / 12 Passed

Description

32%

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 provides a basic understanding of the skill's function but is too terse and lacks critical guidance for skill selection. The absence of a 'Use when...' clause is a significant weakness that would make it difficult for Claude to reliably choose this skill from a large skill library. The single action verb 'list' undersells potential capabilities.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks about test status, QA progress, test case tracking, or needs to review testing priorities'

Expand trigger terms to include common variations: 'test cases', 'testing', 'quality assurance', 'QA status', 'test tracking'

Add more specific actions if applicable, such as 'filter by status', 'sort by priority', 'export test reports', or 'track test coverage'

Dimension	Reasoning	Score
Specificity	Names the domain (QA test procedures) and a single action (list), with attributes mentioned (status and priority), but lacks comprehensive actions like create, update, filter, or export.	2 / 3
Completeness	Only describes what (list QA test procedures with status/priority) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains relevant terms like 'QA', 'test procedures', 'status', and 'priority' that users might say, but missing common variations like 'test cases', 'testing', 'quality assurance', or 'test plan'.	2 / 3
Distinctiveness Conflict Risk	The QA/testing domain provides some specificity, but 'list' is generic and could overlap with other listing or reporting skills; the lack of explicit triggers increases conflict risk.	2 / 3
	Total	7 / 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: jpoutrin/product-forge
Commit: 0ebe7ae

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.