screenshot
Find and display recent screenshots. Triggers: screenshot, check screenshot, show screenshot, recent screenshot, last screenshot.
71
58%
Does it follow best practices?
Impact
98%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/screenshot/SKILL.mdQuality
Discovery
89%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 solid, concise description that clearly communicates its purpose and provides explicit trigger terms for skill selection. Its main weakness is that the capability description could be slightly more specific about what 'find and display' entails (e.g., listing files, opening images, searching by date). Overall it performs well for disambiguation purposes.
Suggestions
Expand the capability description with more specific actions, e.g., 'Find and display recent screenshots from the desktop or screenshots folder, list screenshot files by date, open or preview screenshot images.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (screenshots) and two actions (find and display), but doesn't elaborate on specific capabilities like filtering by time range, opening files, or listing metadata. | 2 / 3 |
Completeness | Clearly answers both 'what' (find and display recent screenshots) and 'when' (explicit trigger terms listed), providing explicit guidance on when Claude should select this skill. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would actually say: 'screenshot', 'check screenshot', 'show screenshot', 'recent screenshot', 'last screenshot' — these cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on screenshots is a clear niche that is unlikely to conflict with other skills. The trigger terms are specific to screenshot-related tasks. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is far too verbose for a simple 'find and display recent screenshots' task. It repeats information (usage examples appear twice), over-specifies platform paths that could be in a reference file, and includes sections like Performance, Integration, and Notes that provide minimal actionable value. The core idea is sound but buried under excessive detail that wastes context window tokens.
Suggestions
Cut the content by at least 60%: remove the repeated usage examples, the Performance/Integration/Notes sections, and consolidate platform paths into a compact table or separate reference file.
Fix the malformed PowerShell snippet (unclosed regex pattern) and show actual Read tool invocation syntax instead of placeholder text in Step 3.
Move platform-specific directory lists and edge case output templates to a separate reference file (e.g., SCREENSHOT_PATHS.md) and link to it from the main skill.
Add a validation step after directory detection (e.g., confirm directory is readable and contains files before proceeding to display).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose for what is a simple task. The skill over-explains platform-specific paths, repeats the usage examples multiple times, includes unnecessary sections like 'Performance', 'Integration', and 'Notes' that add little value. Edge case output templates and the output format section are redundant. Claude doesn't need this level of hand-holding for finding and displaying files. | 1 / 3 |
Actionability | Provides concrete commands for finding files (fd, find, PowerShell) and lists specific directory paths, but the PowerShell snippet is malformed (unclosed regex), Step 3 uses placeholder '[Read tool displays image visually]' rather than showing actual tool invocation syntax, and the overall flow mixes pseudocode-level descriptions with real commands inconsistently. | 2 / 3 |
Workflow Clarity | The three-step process (detect directory, find files, display) is clearly sequenced, and edge cases are addressed. However, there are no validation checkpoints—no step to verify the directory is accessible, no error handling between steps, and no feedback loop if file reading fails. | 2 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to external files. Content that could be split out (platform-specific paths, edge case handling, configuration options) is all inline, making the document excessively long for what should be a simple skill overview. | 1 / 3 |
Total | 6 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.