CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-screenshot

Captura screenshots via Playwright MCP de URLs/elementos pra usar em posts de blog ou documentação. Lida com viewport, cookie banners, full-page vs section, scroll a âncora, formatos PNG/JPG. Compõe com skill 41 (blog-publisher). Trigger em: "tira print", "screenshot do site", "captura tela", "screenshot da página", "print da landing", "print do dashboard", "screenshot pro blog".

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

A tightly structured, highly actionable protocol with concrete Playwright MCP calls, a decision tree, and explicit validation checkpoints. It is concise and well-navigable, with only minor redundancy between its checkpoint and completion checklist.

Suggestions

Merge or cross-link the inline "Checkpoint" (Protocolo step) and "Evidência de Conclusão" checklist to remove overlapping result-verification guidance and tighten the token budget.

Move the viewport table and "Anti-padrões" table into a short reference section or file so the core protocol reads as a lean overview with one-level-deep detail.

DimensionReasoningScore

Conciseness

The body is lean — compact tables, short protocol steps, no concept explanations of Playwright or screenshots — but the "Checkpoint" and "Evidência de Conclusão" sections partly overlap on result verification, leaving minor instances that could be trimmed rather than a fully frictionless token budget.

4 / 5

Actionability

Fully executable guidance throughout: real MCP tool calls (browser_resize, browser_navigate, browser_evaluate, browser_take_screenshot) with concrete arguments, an exact viewport table, a cookie-banner removal snippet, and a naming convention — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

A clearly numbered 1–7 protocol is sequenced with an explicit "Checkpoint" feedback loop ("ajustar o passo correspondente ... e capturar de novo") plus a completion checklist, satisfying the anchor for explicit validation steps and error-recovery loops; validation is present so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and a one-level-deep "Cross-references" section (skill 41, skill 17, GLOBAL.md, policies/tool-safety.md), and no bundle files exist to mis-split; it stops short of the 5 anchor only because all reference material is inline rather than split into separate files, which is acceptable for this scope.

4 / 5

Total

18

/

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, third-person description that pairs concrete capabilities with an explicit trigger-phrase block and a clear composition signal. It cleanly answers both what the skill does and when to invoke it with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "Lida com viewport, cookie banners, full-page vs section, scroll a âncora, formatos PNG/JPG" — giving comprehensive coverage of the screenshot-capture domain, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

It clearly answers "what" (captures screenshots via Playwright MCP of URLs/elements for blog/docs) and "when" (explicit "Trigger em:" with concrete trigger phrases), satisfying the anchor for both what AND when with concrete triggers.

5 / 5

Trigger Term Quality

An explicit "Trigger em:" block supplies seven natural Portuguese phrases users would say ("tira print", "screenshot do site", "captura tela", "print da landing", "print do dashboard") covering synonyms (print/screenshot/captura) and use-case variants, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — "via Playwright MCP de URLs/elementos" for blog/documentation — and it declares composition with skill 41 (blog-publisher), giving it a clear, low-conflict scope distinct from conceptual-image or asset-generation skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

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