CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

browser-automation

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

Quality

88%

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

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

An effective, disciplined router skill: crisp gated routing workflow, concrete tool identifiers and commands, delivery/evidence checklists, and an explicit anti-pattern table. Its two real weaknesses are dangling refs/*.md references (none of the four referenced files exist in the bundle) and noticeable triplication of the routing mapping across three sections.

Suggestions

Ship the four referenced files (refs/playwright-mcp.md, refs/playwriter.md, refs/agent-browser.md, refs/pinchtab.md) in the bundle — or point the refs table at the actual existing paths — so the skill's one-level-deep navigation resolves.

Merge the overlapping '路由矩阵' and '读取哪些 refs' tables into a single table (场景 | 后端 | MCP ID | 状态 | ref), since both encode the same mapping and one can carry the ref column.

Remove the verbatim repetition of questions 1–2 ('真的需要浏览器吗', '目标是 localhost 吗') between '执行前四问' and '默认路由顺序' by having the routing order reference the four questions instead of restating them.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no explanations of what browsers or MCP are — and states '而不是在这里重复厂商文档' / '厂商细节压到 refs/'. It falls short of 5 because routing information is presented three times (默认路由顺序 prose, 路由矩阵 table, 读取哪些 refs table) and the first two routing questions are repeated verbatim in both '执行前四问' and '默认路由顺序'.

4 / 5

Actionability

For an instruction-only router skill, guidance is fully concrete: specific MCP IDs ('playwright', 'pinchtab'), tool prefixes ('mcp__claude-in-chrome__*'), install commands ('npm i -g agent-browser', 'npx @playwright/mcp@latest'), exact ref paths, and a precise failure fix ('用 pinchtab_eval + window.location.href 导航'). Per the rubric's code-vs-instruction note, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

The '默认路由顺序' is a gated 7-step decision sequence with explicit conditions; '交付要求' is a delivery checklist including evidence and login-session accountability; 'Common Mistakes' provides error→consequence→fix recovery loops; and step 6 includes an explicit validation ('使用前先做本机验活'). This matches anchor 5's sequence + checkpoints + checklist + feedback loops; it is above anchor 4 because recovery and validation are explicit, not merely implied.

5 / 5

Progressive Disclosure

The structure is designed correctly — a lean overview with '读取哪些 refs' pointing one level deep to refs/playwright-mcp.md, refs/playwriter.md, refs/agent-browser.md, refs/pinchtab.md — but none of these files exist in the bundle (no refs/, references/, scripts/, or assets/ directories are present), so every deep link is dangling and navigation breaks in practice. It is above anchor 2 (structure and signaling are good, nothing monolithic) but below anchor 4 because referenced paths do not resolve to real files.

3 / 5

Total

17

/

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 well-formed router description: concrete capability statement, explicit Use-when/Not-for boundaries, and a defined output contract in third-person voice. The only soft spot is that natural-language trigger coverage inside the description itself is good but not exhaustive, relying partly on the separate triggers list.

DimensionReasoningScore

Specificity

The description names the domain ('浏览器工作流总路由') and several concrete functions — '为外部网站浏览、登录态流程、浏览器自动化、证据采集选择合适后端' — plus an explicit output contract ('选定浏览器后端 + 执行路径 + 证据/结果'). It stays slightly below anchor 5 because the concrete actions are variations of one routing act rather than multiple distinct comprehensive operations.

4 / 5

Completeness

It explicitly answers what ('选择合适后端' with an Output line), when ('Use when:' with concrete trigger conditions), and even when-not ('Not for:' with redirects to browser-preview and webapp-testing) — matching the anchor-5 example's structure of concrete what + explicit trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when' clause lists several natural trigger phrases ('需要操作外部网站、登录页、JS 重页面、没有 webfetch/VL 但需要浏览器、或需要在多种浏览器工具之间路由') that mirror what a user would actually say, and the Not-for clause adds contrast terms. Not 5: common variations like Playwright/headless/scraping synonyms are absent (they live in the separate triggers list, not the description itself). Not 3: coverage is broad and phrased in user-natural language rather than only technical jargon.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (external-website browser routing) and explicitly disambiguates against sibling skills ('Not for: localhost 页面预览(用 browser-preview)、本地 WebApp 确定性测试(用 webapp-testing)、简单网页抓取/搜索'), minimizing wrong-skill triggering.

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.