qa-element-extraction
Extract and capture screenshots of specific UI elements mentioned in QA test procedures. Use when creating visual references for test steps to show exactly what buttons, fields, and components look like.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill qa-element-extraction78
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-crafted skill description that clearly communicates its purpose and when to use it. It excels at specificity and completeness with explicit 'Use when' guidance. Minor improvement could be made by expanding trigger terms to include more natural variations users might say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Extract and capture screenshots', 'specific UI elements', 'buttons, fields, and components'. Clearly describes what the skill does with concrete examples. | 3 / 3 |
Completeness | Clearly answers both what ('Extract and capture screenshots of specific UI elements mentioned in QA test procedures') and when ('Use when creating visual references for test steps') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'screenshots', 'UI elements', 'QA test procedures', 'buttons, fields, components', but missing common variations users might say like 'screen capture', 'snapshot', 'visual documentation', or 'test documentation'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche combining QA testing context with UI screenshot capture. The specific focus on 'test procedures' and 'visual references for test steps' distinguishes it from general screenshot or documentation 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 strong actionable guidance with executable Playwright code examples and clear naming conventions. However, it's overly verbose for its purpose, includes some obvious information Claude doesn't need, and lacks validation checkpoints in the workflow. The content would benefit from being split across multiple files with SKILL.md serving as a concise overview.
Suggestions
Add explicit validation steps after screenshot capture (e.g., verify file exists, check image dimensions, confirm element was visible)
Move the 'Glossary Building' and 'Edge Cases' sections to separate reference files, keeping SKILL.md focused on the core extraction workflow
Remove the lists of obvious action verbs and element type keywords that Claude already knows - focus on the parsing pattern itself
Add a verification step in the automated workflow to confirm each element was successfully located before capturing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity. The glossary building section and extensive tables could be condensed. Some sections like 'Element Identification Patterns' list obvious action verbs Claude already knows. | 2 / 3 |
Actionability | Provides fully executable Playwright code examples with multiple selector strategies (by role, text, test ID). Code is copy-paste ready with specific file paths and clear syntax. | 3 / 3 |
Workflow Clarity | The 'Automated Extraction Workflow' section provides a clear sequence, but lacks explicit validation checkpoints. No verification step to confirm screenshots captured correctly or that elements were found before proceeding. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one monolithic file. The extensive glossary building and edge cases sections could be split into separate reference files for better navigation. | 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.