screenshot
Find and display recent screenshots. Triggers: screenshot, check screenshot, show screenshot, recent screenshot, last screenshot.
85
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
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, functional description that excels at trigger term coverage and completeness. The main weakness is the somewhat limited specificity - it could benefit from more detail about what 'find and display' actually does (e.g., file paths, preview capabilities, filtering options).
Suggestions
Expand the capability description to include more specific actions, e.g., 'Find and display recent screenshots from the desktop or downloads folder, show file paths and timestamps'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (screenshots) and two actions (find and display), but lacks comprehensive detail about what 'find' and 'display' entail or additional capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('Find and display recent screenshots') and when ('Triggers: screenshot, check screenshot...'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'screenshot', 'check screenshot', 'show screenshot', 'recent screenshot', 'last screenshot' - these are common, natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Screenshots are a distinct niche with specific trigger terms; unlikely to conflict with other skills like document processing or image editing. | 3 / 3 |
Total | 11 / 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 skill provides solid, actionable guidance with executable code for multiple platforms and a clear workflow. However, it's overly verbose for what is essentially a simple file-finding operation - Claude doesn't need extensive explanations of common screenshot directories or multiple redundant code examples. The content would benefit from trimming redundancy and potentially splitting advanced configuration into a separate file.
Suggestions
Consolidate the platform-specific directory lists into a single compact table rather than separate code blocks for each OS
Choose one primary implementation approach (e.g., fd or native tools) rather than showing both - Claude can adapt
Move the custom directory configuration and edge case handling to a separate ADVANCED.md file to keep the main skill lean
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity - the extensive platform-specific path listings, multiple code examples for the same operation (fd, PowerShell, Bash), and the detailed edge case explanations could be condensed. Claude doesn't need this level of hand-holding for basic filesystem operations. | 2 / 3 |
Actionability | Provides fully executable code examples for multiple platforms (PowerShell, Bash, fd), concrete command syntax, and specific file patterns. The implementation steps are copy-paste ready with real commands. | 3 / 3 |
Workflow Clarity | Clear 3-step workflow (detect directory → find screenshots → display) with explicit sequencing. For this non-destructive read-only operation, validation checkpoints aren't critical, and the workflow is unambiguous. | 3 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but it's somewhat monolithic at ~150 lines. The custom directory config, integration notes, and detailed edge cases could be split into separate reference files. No external file references are used. | 2 / 3 |
Total | 10 / 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 | |
- 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.