screenshot

Find and display recent screenshots. Triggers: screenshot, check screenshot, show screenshot, recent screenshot, last screenshot.

1.28x

Quality

58%

Does it follow best practices?

Impact

98%

1.28x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/screenshot/SKILL.md

Quality

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 concise and functional description that clearly identifies its niche (screenshots) and provides explicit trigger terms. Its main weakness is that the capability description is somewhat thin—it could benefit from listing more specific actions. Overall it performs well for skill selection purposes.

Suggestions

Expand the capability description with more specific actions, e.g., 'Find and display recent screenshots, list screenshots by date, open screenshot files from the desktop or default screenshot directory.'

Dimension	Reasoning	Score
Specificity	Names the domain (screenshots) and two actions (find and display), but doesn't elaborate on specific capabilities like filtering by date, opening in viewer, listing metadata, etc.	2 / 3
Completeness	Clearly answers both 'what' (find and display recent screenshots) and 'when' (explicit trigger terms listed). The 'Triggers:' clause serves as an explicit 'Use when' equivalent.	3 / 3
Trigger Term Quality	Includes a good set of 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	Screenshots are a distinct niche unlikely to conflict with other skills. The trigger terms are specific to screenshot-related tasks and wouldn't overlap with general file or image processing skills.	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 significantly over-engineered for a relatively simple task (find and display recent screenshots). It suffers from excessive verbosity, repeating information (usage examples appear twice), including sections Claude doesn't need (Performance, Integration, Notes), and cramming everything into one file. The actionable content is decent but incomplete in places, and the workflow lacks validation checkpoints.

Suggestions

Cut the content by at least 60% — remove the Performance, Integration, Notes, and repeated usage sections; Claude can infer most of this.

Fix the incomplete PowerShell snippet and provide actual Read tool invocation syntax instead of placeholder descriptions like '[Read tool displays image visually]'.

Move platform-specific directory lists and edge case handling to a separate reference file, keeping SKILL.md as a concise overview.

Add a validation step after directory detection (e.g., confirm directory exists and contains image 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 usage examples multiple times, includes unnecessary sections like 'Performance', 'Integration', and 'Notes' that add little value. The edge cases section, output format template, and custom directory config are all padding. Claude doesn't need this much hand-holding for finding and displaying files.	1 / 3
Actionability	Provides concrete commands for finding files (fd, find, PowerShell) and lists specific directory paths, which is useful. However, the code snippets are incomplete (the PowerShell snippet is cut off mid-regex), the Read tool usage is described abstractly rather than with actual tool invocation syntax, and the overall implementation is more of a description than a copy-paste-ready script.	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 detected directory is correct before proceeding, and no error handling between steps. The workflow reads more like a description of what happens than actionable instructions with feedback loops.	2 / 3
Progressive Disclosure	All content is in a single monolithic file with no references to external files. The content is far too long for a single SKILL.md — platform-specific paths, edge cases, output format templates, custom config, and integration notes could all be split out. The file is a wall of text that would benefit significantly from progressive disclosure.	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 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: 3ae408c

Reviewed: 2 days 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.