full-page-screenshot

Capture full-page screenshots of web pages via Chrome DevTools Protocol with zero dependencies. Useful for portfolios, case studies, and audit reports.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/full-page-screenshot/SKILL.md

Quality

Content

57%

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

The content is concise and well-organized with a single clearly signaled external reference, but it provides no executable guidance for the actual screenshot task, capping actionability at the lowest level and leaving workflow clarity with gaps.

Suggestions

Add a minimal executable example for the core task (e.g. a short CDP/Playwright snippet or an exact CLI command) so the skill is actionable without round-tripping to the upstream README.

Replace the macOS-only 'open <url>' with a portable pointer (e.g. 'clone https://github.com/LewisLiu007/full-page-screenshot and follow its README') and state the install path concretely.

Include at least one validation checkpoint (e.g. 'confirm the output PNG height matches the full page height') to raise workflow_clarity above 2.

Dimension	Reasoning	Score
Conciseness	The body is short and lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the only mild redundancy is the verbatim repeat of the frontmatter description under 'What it does', which does not rise to padding.	3 / 3
Actionability	The only instruction is 'open https://github.com/...' (a non-portable browser-open command) plus 'Inspect the upstream README for exact paths'; there is no executable code or command for the skill's actual task of capturing a screenshot via CDP, so it describes rather than instructs.	1 / 3
Workflow Clarity	A loose sequence is present (advertise in Open Design, install the upstream bundle, invoke by name or trigger), but there are no validation checkpoints and the real capture workflow is delegated to an unseen upstream README, so the sequence has gaps.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is under 50 lines with clean, well-organized sections (What it does / Source / How to use); the only external pointer is a one-level-deep upstream URL, satisfying the simple-skill allowance for a top score.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 clear and specific about a single capability with a distinct niche, but it lists only one main action and lacks an explicit 'Use when...' trigger clause, leaving completeness and specificity at the mid level.

Suggestions

Add an explicit 'Use when...' clause naming concrete user intents, e.g. 'Use when the user asks for a full-page or scrolling screenshot of a web page, or needs a long web capture for an audit report.'

Broaden trigger coverage to include natural phrasings like 'website screenshot', 'scrolling screenshot', or 'capture whole page' to improve trigger_term_quality.

Optionally enumerate one or two more concrete actions (e.g. '...and save them as PNG files at full viewport height') to lift specificity toward level 3.

Dimension	Reasoning	Score
Specificity	It names a concrete action ("Capture full-page screenshots of web pages via Chrome DevTools Protocol with zero dependencies") and the domain, but lists only one primary action rather than multiple specific concrete actions, so it stops short of the level-3 anchor.	2 / 3
Completeness	The 'what' is stated clearly, but the 'when' is only implied via 'Useful for portfolios, case studies, and audit reports' with no explicit 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like "full-page screenshots" and "web pages" appear and the frontmatter triggers add coverage ("full page screenshot", "long screenshot", "devtools screenshot", "web capture"), but common variations a user might say (e.g. "website screenshot", "scrolling screenshot") are missing, so it matches 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The niche is clear and specific (full-page web screenshots via Chrome DevTools Protocol with zero dependencies), with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/full-page-screenshot/SKILL.md
Commit: f2760fd

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