CtrlK
BlogDocsLog inGet started
Tessl Logo

full-page-screenshot

Use when the user asks to capture a full-page screenshot, long screenshot, or complete page capture of a web page. Handles SPA scroll containers, lazy-loaded images, and very tall pages via Chrome DevTools Protocol with zero external dependencies.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

A well-structured, executable skill body that puts usage guidance in SKILL.md and implementation in the bundled script, with explicit pre/post validation and troubleshooting recovery. It is dense without padding and does not re-explain concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean, dense, and assumes Claude's competence — it does not explain what Chrome/CDP/SPAs are; sections are tables and tight lists where every token earns its place, with only trivial repetition of 'zero external dependencies'.

5 / 5

Actionability

Provides copy-paste-ready, fully executable commands for every mode (--check, --list, targetId, --url) plus a parameters table with defaults and concrete verification commands (sips, file).

5 / 5

Workflow Clarity

Clear two-option workflow with explicit validation checkpoints (--check before capture, Verify Output after) and a troubleshooting table that supplies error-recovery feedback loops for the common failure modes.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with implementation detail correctly split into the bundled scripts/full-page-screenshot.mjs (verified present and real); cross-references to sibling skills are one level deep and clearly signaled.

5 / 5

Total

20

/

20

Passed

Description

100%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.

A strong, concise description that explicitly covers what the skill does and when to use it, with concrete trigger synonyms and specific capability claims. No fluff or over-claims detected.

DimensionReasoningScore

Specificity

Names concrete capabilities beyond the core action — 'SPA scroll containers, lazy-loaded images, and very tall pages via Chrome DevTools Protocol' — giving comprehensive, specific coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what (capture full-page screenshots, handle SPAs/lazy-load/tall pages via CDP, zero external deps) and when via a concrete 'Use when the user asks to capture...' trigger clause.

5 / 5

Trigger Term Quality

Includes the natural synonyms users actually say ('full-page screenshot', 'long screenshot', 'complete page capture of a web page') alongside technical terms, with no meaningful natural variation missing.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (full-page web capture via CDP) with distinct triggers unlikely to fire for unrelated screenshot or browser-automation skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.