CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

browser-automation

浏览器工作流总路由:为外部网站浏览、登录态流程、浏览器自动化、证据采集选择合适后端。 Use when: 需要操作外部网站、登录页、JS 重页面、没有 webfetch/VL 但需要浏览器、或需要在多种浏览器工具之间路由。 Not for: localhost 页面预览(用 browser-preview)、本地 WebApp 确定性测试(用 webapp-testing)、简单网页抓取/搜索。 Output: 选定浏览器后端 + 执行路径 + 证据/结果。

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cat-cafe-skills/browser-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-designed router skill with genuinely concrete tool IDs, commands, pre-flight questions, and delivery requirements, and a correct keep-vendor-detail-in-refs architecture. Its two real weaknesses are section-level redundancy (the same routing decision restated six ways) and the fact that every referenced refs/*.md file is missing from the delivered bundle, which both weakens actionability and breaks progressive disclosure.

Suggestions

Collapse the redundant routing views: 默认路由顺序 already encodes the decisions in 先按目的选入口 (including the verbatim-repeated "真的需要浏览器吗" question), so merge 入口/路由矩阵/组合打法/读取哪些 refs/下一步 into the routing order or a single matrix.

Ship the four referenced refs/*.md files (playwright-mcp.md, playwriter.md, agent-browser.md, pinchtab.md) in the bundle, or inline the minimal per-backend usage notes, so routing decisions don't dead-end at missing files.

Add an explicit post-execution validation step to 交付要求, e.g. verify the evidence artifact (screenshot/text/log) exists and is non-empty before reporting completion.

DimensionReasoningScore

Conciseness

The body is mostly tight (tables, vendor detail pushed to refs), but the routing decision is restated across ~6 overlapping sections: "真的需要浏览器吗?…不要默认上浏览器" appears verbatim in both 执行前四问 and 默认路由顺序, and 路由矩阵/组合打法/refs 表/区别表/下一步 re-cover the same routing. This is more than minor trimming, so it sits at anchor 3 rather than 4, but there is no fluff or explanation of concepts Claude already knows, so not 2.

3 / 5

Actionability

Concrete, executable routing guidance: "npm i -g agent-browser", "MCP ID: playwright", "工具前缀 mcp__claude-in-chrome__*", and the PinchTab fix "用 pinchtab_eval + window.location.href 导航", plus a four-item delivery checklist. Not 5 because execution detail is deferred to refs/*.md files that are absent from the bundle, so the paths dead-end; well above anchor 3 since what is present is specific, not pseudocode.

4 / 5

Workflow Clarity

Clear sequenced workflow: 执行前四问 pre-flight checklist, numbered 默认路由顺序 decision sequence with explicit conditions, 交付要求 delivery checklist, and Common Mistakes failure→fix pairs. Anchor 4 rather than 5 because there is no explicit post-execution validation loop (e.g., confirming the promised screenshot/evidence artifact was actually captured before reporting).

4 / 5

Progressive Disclosure

References are well-signaled and one level deep (refs table lists refs/playwright-mcp.md, refs/playwriter.md, refs/agent-browser.md, refs/pinchtab.md with scenarios), but the bundle contains no refs/ directory — none of the four referenced files exist, so the disclosure chain is broken. That is a larger gap than anchor 4's "minor organization gaps", landing at 3; not 2 because the SKILL.md itself is well structured and nothing that belongs in refs is inlined.

3 / 5

Total

14

/

20

Passed

Description

87%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: it states a clear what, an explicit Use-when with concrete trigger conditions, a Not-for clause that fences off the two adjacent skills, and a defined output. The only soft spots are that the capability list is one meta-action applied to several scenarios and a few natural trigger synonyms are missing.

DimensionReasoningScore

Specificity

"为外部网站浏览、登录态流程、浏览器自动化、证据采集选择合适后端" plus "Output: 选定浏览器后端 + 执行路径 + 证据/结果" names several concrete functions and an explicit output spec. Anchor 4 rather than 5 because the listed capabilities are variants of one routing/selection meta-action rather than a broad set of distinct operations.

4 / 5

Completeness

Explicitly answers both questions with concrete triggers: what ("浏览器工作流总路由…选择合适后端"), when ("Use when: 需要操作外部网站、登录页、JS 重页面…"), and goes further with "Not for:" exclusions and an "Output:" spec. This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

"需要操作外部网站、登录页、JS 重页面、没有 webfetch/VL 但需要浏览器、或需要在多种浏览器工具之间路由" covers natural user phrasings (操作外部网站, 登录页, 路由). Anchor 4 rather than 5 because common synonyms users would say — 截图/抓取, 浏览器控制, English "browser automation" — are absent; well above anchor 3's partial keyword coverage.

4 / 5

Distinctiveness Conflict Risk

"Not for: localhost 页面预览(用 browser-preview)、本地 WebApp 确定性测试(用 webapp-testing)、简单网页抓取/搜索" draws explicit negative boundaries against the neighboring skills, and the niche (external-site browser backend routing) is distinct — minimal conflict risk, matching anchor 5.

5 / 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

zts212653/clowder-ai

Path

cat-cafe-skills/browser-automation/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.