qa-screenshot-management
Screenshot capture, organization, and comparison for QA testing. Use when taking screenshots during test execution to ensure proper naming, organization, and traceability back to test cases.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill qa-screenshot-management78
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
85%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 is a well-structured description that clearly communicates the skill's purpose and when to use it. It uses proper third-person voice and includes an explicit 'Use when...' clause. The main weakness is limited trigger term coverage - it could benefit from additional natural keywords users might use when needing this functionality.
Suggestions
Add more natural trigger terms like 'visual testing', 'UI screenshots', 'regression testing', 'image comparison', or 'visual QA' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Screenshot capture, organization, and comparison for QA testing' clearly identifies three distinct capabilities in a testing context. | 3 / 3 |
Completeness | Clearly answers both what ('Screenshot capture, organization, and comparison for QA testing') and when ('Use when taking screenshots during test execution to ensure proper naming, organization, and traceability back to test cases'). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'screenshots', 'QA testing', 'test execution', and 'test cases', but missing common variations users might say like 'visual testing', 'image comparison', 'UI testing', or 'regression screenshots'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche combining screenshots specifically with QA testing context, test execution, and traceability - unlikely to conflict with general screenshot tools or generic testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable guidance for QA screenshot management with excellent concrete examples and executable code. However, it's somewhat verbose for a skill file, lacks explicit workflow validation steps, and would benefit from splitting advanced topics into separate reference documents to improve progressive disclosure.
Suggestions
Add an explicit numbered workflow for the core screenshot capture process with validation checkpoints (e.g., verify screenshot saved, verify naming matches convention)
Split advanced topics (visual comparison, cross-browser, accessibility guidelines) into separate reference files and link from a concise overview section
Remove obvious content like basic Playwright syntax that Claude already knows, focusing only on project-specific conventions and patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some content Claude would know (basic Playwright screenshot syntax, obvious naming conventions). Tables and examples are helpful but some sections like 'Bad vs Good Names' are somewhat verbose for obvious points. | 2 / 3 |
Actionability | Provides fully executable Playwright code examples, specific directory structures, concrete naming conventions with examples, and copy-paste ready commands. The bash cleanup command and JavaScript snippets are immediately usable. | 3 / 3 |
Workflow Clarity | The skill covers many scenarios but lacks explicit validation checkpoints. The 'When to Capture Screenshots' section lists triggers but doesn't provide a clear sequential workflow with verification steps. The failure documentation checklist is good but the overall process flow is implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear headers and tables, but it's a monolithic document (~200 lines) that could benefit from splitting advanced topics (visual comparison, cross-browser, accessibility) into separate reference files. No external file references are provided. | 2 / 3 |
Total | 9 / 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.