CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-first-screenshots

Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.

75

Quality

92%

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

100%

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

An excellent, focused skill body: concise, concrete, with a well-sequenced verify-capture loop and explicit validation feedback, and progressive disclosure via two real referenced scripts. It assumes competence and every section carries non-obvious, actionable detail.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence throughout — it never explains what CDP, a PNG, or layout engines are, and every section (Zero-Defect Bar, Golden Rules, verify loop, failure-mode table) earns its tokens with non-obvious domain specifics like variance thresholds.

3 / 3

Actionability

Gives concrete executable guidance: specific CDP metrics (1440x900 at deviceScaleFactor:2), explicit commands (location.reload()), quantified pixel checks (variance >~200, bgRatio >0.97), a full vision JSON schema, and named executable bundle scripts with described behavior.

3 / 3

Workflow Clarity

The capture loop is a clear sequenced workflow with explicit validation checkpoints (DOM pre-check → pixel post-check → vision gate) and a genuine feedback loop ('If any_obvious_defect is true... Diagnose, fix the root cause... recapture'), matching the validate→fix→retry anchor.

3 / 3

Progressive Disclosure

A well-organized overview with clearly-signaled, one-level-deep references to real bundle scripts (screenshot-verify.mjs and capture-verify.mjs, both present in scripts/); no nested references and executable detail appropriately offloaded to those scripts.

3 / 3

Total

12

/

12

Passed

Description

85%

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, specific description that clearly states capabilities and an explicit use-trigger in third person. It only loses points on trigger-term breadth — it names screenshot phrasing but omits the common 'marketing/product images' variations a user might actually say.

Suggestions

Broaden the 'Use when...' clause to include common phrasings like 'marketing images', 'product images', or 'redo screenshots' so it surfaces on more natural requests.

Keep the explicit 'NOT e2e evidence' disambiguation from the body — consider a brief conflict note in the description to further reduce overlap with the fraimz skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('drives the real app via CDP', 'produces clean, defect-free product screenshots') plus enumerated artifact types (newsletters, landing pages, social, decks, PR) and a concrete dual-channel verification method, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('drives the real app via CDP and produces clean, defect-free product screenshots ... Dual-channel verification') and when ('Use for any "take/redo screenshots of the app" task'), matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Includes a natural trigger ('Use for any "take/redo screenshots of the app" task') a user would say, but coverage is narrow — missing common variations like 'marketing images' or 'product images' that the body itself mentions.

2 / 3

Distinctiveness Conflict Risk

Clear niche (CDP-driven screenshot pipeline) with distinct screenshot-specific triggers and an explicit exclusion of e2e evidence, making it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Devin-AXIS/iPolloWork
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.