CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-automation

Local OpenWork 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.

65

Quality

78%

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 ./.opencode/skills/browser-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 tight, highly actionable skill body with executable commands and a complete eval example. Workflow sequencing is clear but would benefit from an explicit response-confirmation checkpoint, and one inline script could be externalized.

Suggestions

Add an explicit validation step in the Browser Tool Flow, e.g. 'Confirm response: re-check document.body.innerText and fail loudly if the expected reply is missing'.

Move the full Send A Session eval script into a references/ file and link to it, keeping only the selector and button summary inline.

DimensionReasoningScore

Conciseness

Mostly lean with executable snippets and tight sections; the 'What I Do' bullets and a few prose lines slightly restate what the code already shows.

4 / 5

Actionability

Fully executable: copy-paste shell commands, a complete browser_eval script, and specific selectors/buttons covering the common send-a-session case.

5 / 5

Workflow Clarity

The numbered Browser Tool Flow and background-launch wait-check are clearly sequenced with a readiness check (lsof), but it lacks an explicit validation/feedback loop confirming the response actually arrived.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and no nested references; a small amount of inline reference-style detail (the full eval script) could live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

75%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 specific, well-triggered description that names concrete tools and an explicit use-when clause. It is slightly technical in its trigger phrasing and could be sharpened with more natural synonyms.

Suggestions

Add casual synonyms users might say (e.g. 'automate the OpenWork UI', 'click through the Electron app') alongside the tool names.

Lead with a single sharp 'Use when...' clause rather than a comma-separated list to make the trigger more scannable.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('browser_list, browser_snapshot, browser_eval, composer automation, local UI smoke tests') with minor coverage gaps around read/inspection actions.

4 / 5

Completeness

Explicit 'what' (CDP browser automation) and explicit 'when' ('Use when driving a local Electron dev app...'), with the 'when' slightly list-like rather than a single sharp trigger phrase.

4 / 5

Trigger Term Quality

Good natural triggers ('driving a local Electron dev app', 'composer automation', 'local UI smoke tests') though it leans slightly technical and omits some casual synonyms.

4 / 5

Distinctiveness Conflict Risk

The OpenWork/Electron/CDP niche is specific and unlikely to clash with general browser skills, with only minor overlap risk against generic browser-automation skills.

4 / 5

Total

16

/

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
different-ai/openwork
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.