CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lens-inspect

Use the Lens built-in browser to inspect a running web application. Trigger when the request involves previewing a page, taking screenshots, reading DOM, checking console errors, picking elements to locate source code, or comparing rendered output to a design spec.

1.42x
Quality

84%

Does it follow best practices?

Impact

100%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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-built, information-dense skill body: no filler, a compact tool reference, and one clear feedback-looped workflow. It falls short of top marks mainly on actionability (no per-tool argument examples) and workflow clarity (no error-recovery guidance), with mild conciseness and organization trim opportunities.

Suggestions

Add one-line usage examples showing argument shapes for the key tools, e.g. stave_lens_click("button#submit"), stave_lens_get_html("nav.sidebar"), and stave_lens_evaluate("document.title").

Add brief error-recovery guidance to the workflows, such as what to do when navigation fails, a selector matches nothing, or the console buffer shows errors after a click.

Trim agent-irrelevant detail (the WebContentsView backing, the Globe icon / Command Palette bullet) and consider moving the full session-presentation rules into a reference file, keeping only the decision rule inline.

DimensionReasoningScore

Conciseness

The body is dense and operational with no generic-concept padding, but a few tokens could be trimmed, such as the Electron "WebContentsView" implementation detail and the user-facing "Globe icon or Command Palette" bullet that adds little for the agent.

4 / 5

Actionability

Concrete MCP tool names, required parameters (workspaceId), and an executable workflow example (stave_lens_navigate("http://localhost:3000/page")) provide mostly executable guidance, but per-tool invocation examples with argument shapes (e.g., selector syntax for stave_lens_click or stave_lens_inspect) are missing.

4 / 5

Workflow Clarity

The Figma comparison workflow is a clear 6-step sequence with a validation step (compare rendered output to spec) and a feedback loop ("Repeat from step 2"), and the element picker is a numbered sequence, but there are no explicit error-recovery checkpoints (e.g., what to do when a tool call or navigation fails).

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and no nested references, but at ~95 lines the 15-row tool catalog and detailed session-presentation rules could partially live in a reference file; structure is good with minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

88%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 description with an explicit trigger clause and multiple concrete, naturally-phrased capabilities in third-person imperative voice. Keyword coverage and distinctiveness are good but not flawless: a few natural synonyms (console logs, debug, click/type interaction) are absent and some triggers are generic enough to overlap with other browser tools.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("taking screenshots, reading DOM, checking console errors, picking elements to locate source code, or comparing rendered output to a design spec") with comprehensive coverage of the inspection domain, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

It explicitly answers both "what" ("Use the Lens built-in browser to inspect a running web application") and "when" ("Trigger when the request involves...") with concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases like "previewing a page", "checking console errors", and "comparing rendered output to a design spec" give good keyword coverage, but common variations such as "console logs", "debug", network requests, and interaction terms (click, type) are missing despite being listed capabilities.

4 / 5

Distinctiveness Conflict Risk

"Lens built-in browser" and "running web application" carve a clear niche, but generic triggers like "taking screenshots" and "reading DOM" create minor overlap risk with general browser-automation or screenshot skills.

4 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

sendbird/stave

Path

skills/lens-inspect/SKILL.md

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.