screenshot

Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.

3.63x

Quality

88%

Does it follow best practices?

Impact

69%

3.63x

Average score across 5 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands per OS, a clear preflight-to-capture workflow, and well-signaled references to real bundled scripts. Minor conciseness and progressive-disclosure refinements would push it to the top anchor.

Dimension	Reasoning	Score
Conciseness	Largely efficient with concrete commands and minimal concept explanation, but repeated boilerplate (e.g. the full powershell invocation per pattern, full script paths) could be tightened.	4 / 5
Actionability	Fully executable, copy-paste-ready commands with real flags and example values across macOS, Linux, and Windows, covering the common capture cases per OS.	5 / 5
Workflow Clarity	Clear sequenced flow (permission preflight -> capture -> view -> report path) with an enumerated save-location ruleset and an error-handling section providing validate/retry feedback loops.	5 / 5
Progressive Disclosure	Well-organized sections with one-level-deep references to real bundled scripts (ensure_macos_permissions.sh, take_screenshot.py, take_screenshot.ps1), though inline fallback commands partially duplicate the helper logic.	4 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and trigger-rich, with an explicit 'Use when...' clause and a well-scoped niche that distinguishes it from tool-specific capture skills. Minor gaps in synonym coverage and explicit verb naming keep a couple dimensions just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names the screenshot domain and enumerates concrete capture variants (full screen, specific app or window, pixel region), though the capture/save verbs are implied rather than listed explicitly.	4 / 5
Completeness	Explicitly answers 'when' with a concrete 'Use when the user explicitly asks for...' clause and clearly conveys the 'what' (OS-level screenshot capture) with specific trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrasing like 'desktop or system screenshot', 'full screen', 'specific app or window', and 'pixel region', though synonyms such as 'screen capture' are absent.	4 / 5
Distinctiveness Conflict Risk	Carves out a clear OS-level capture niche and explicitly excludes tool-specific captures (Figma MCP, Playwright), minimizing conflict risk with adjacent skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/screenshot/SKILL.md
Commit: d5ae560

Reviewed: 5 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.