Content
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 simple screenshot-finding task. It suffers from excessive verbosity, repeating information (usage examples appear twice), including unnecessary sections (Performance, Integration, Notes), and inlining all platform-specific details rather than keeping the overview lean. The actionability is moderate — real commands are provided but fragmented and sometimes malformed.
Suggestions
Cut the content by at least 60%: remove the Performance, Integration, and Notes sections; consolidate the repeated usage examples; trim edge cases to a brief list rather than full output templates.
Move platform-specific directory listings and commands into a separate reference file (e.g., PLATFORMS.md) and keep SKILL.md as a concise overview with one canonical example.
Fix the truncated PowerShell snippet and provide a single unified implementation approach rather than listing multiple alternative tools (fd, find, PowerShell) inline.
Show the actual Read tool invocation syntax concretely rather than describing it abstractly as '[Read tool displays image visually]'.
| 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. The output format section, edge cases, and custom directory config are all padding that Claude could infer. This could easily be 1/3 the length. | 1 / 3 |
Actionability | Provides concrete commands for finding files (fd, find, PowerShell) and lists specific directory paths, but the code snippets are fragmented across platforms without a cohesive executable implementation. The PowerShell snippet is truncated/malformed. The 'Read tool' usage is described abstractly rather than with concrete tool invocation syntax. | 2 / 3 |
Workflow Clarity | The three-step process (detect directory → find files → display) is clearly sequenced, and edge cases are covered. However, there are no validation checkpoints between steps — e.g., no explicit check that the directory detection succeeded before proceeding to file search, and no error handling flow between steps. | 2 / 3 |
Progressive Disclosure | All content is inlined 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, custom config, and integration notes should be split out or omitted. The file reads as a wall of text despite having headers. | 1 / 3 |
Total | 6 / 12 Passed |