CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-automation

Local iPolloWork Electron browser automation with CDP. Use when driving a local Electron dev app, browser_list, browser_snapshot, browser_eval, composer automation, or local UI smoke tests.

73

Quality

90%

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

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

The content is a tight, fully-executable guide for a single-purpose local dev tooling task with copy-paste commands and a complete code snippet. The only gap is an explicit inline validation checkpoint within the main Browser Tool Flow, which currently relies on Notes for the expected-response check.

Suggestions

Add an explicit validation step inside the Browser Tool Flow (e.g., step 0: confirm `lsof -nP -iTCP:9823 -sTCP:LISTEN` shows the port before calling browser_list, and a final step: assert `document.body.innerText` contains the expected response).

Make the success/verification criterion part of the flow rather than only the Notes section, so the feedback loop is visible inline where it is executed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: each section (setup, background launch, tool flow, send-a-session) earns its place with no padding or explanation of concepts Claude already knows, satisfying the lean/efficient anchor.

5 / 5

Actionability

It provides copy-paste-ready shell commands and a complete, executable browser_eval JS snippet that handles the common case (fill composer, click Run task, return status), matching the fully-executable anchor.

5 / 5

Workflow Clarity

A clear numbered Browser Tool Flow exists and Background Launch includes a wait-on-port checkpoint, with the Notes section giving an expected-response verification signal; however the main flow itself has no explicit inline validate/confirm checkpoint between attaching and asserting success, leaving a minor validation gap versus the anchor requiring explicit validation steps.

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with well-organized sections and no need for external references, so the simple-skill exception lets progressive disclosure score 5 on well-organized sections alone.

5 / 5

Total

19

/

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.

The description is concrete, scoped to a distinct niche, and explicitly pairs a clear what with a Use-when trigger. It is slightly held back from full marks on specificity and trigger-term breadth by leaning on tool names rather than a fuller set of natural synonyms.

DimensionReasoningScore

Specificity

"browser automation with CDP" plus a list of concrete tools and tasks (browser_list, browser_snapshot, browser_eval, composer automation, UI smoke tests) gives several specific actions, though several items are tool names rather than distinct capabilities, so it stops short of comprehensive coverage at 5.

4 / 5

Completeness

It states the what ("Local iPolloWork Electron browser automation with CDP") and an explicit "Use when..." clause with concrete trigger conditions, matching the anchor that requires both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger phrases like "Electron dev app", "composer automation", "local UI smoke tests", and the OpenCode tool names (browser_list, browser_snapshot, browser_eval) cover what a user would say, but a few common synonyms (e.g. "debug", "DevTools", "CDP port") are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a named app (iPolloWork Electron) and a specific dev-tooling niche with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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.