CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drive-desktop-cdp

Drive the running OpenWork app over CDP from the shell, headless by default (nothing opens on screen). Evaluate JS, take screenshots, open a new session, send a prompt with a chosen model, wait for the run to finish. Use when checking a UI change by hand in a world or pnpm dev, or when reproducing a chat state.

Quality

94%

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

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.

An exemplary lean operational skill: concrete commands with expected outputs, explicit safety warnings ("Anything you send is real"), and crisp routing guidance at the top. The sole weakness is the absence of failure-recovery steps in the workflow.

DimensionReasoningScore

Conciseness

Every line is a runnable command, a path, or an operative rule; there is zero explanation of concepts Claude already knows (no "what CDP is", no library introductions). The ~40-line body assumes competence and every token earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready guidance: the exact `pnpm world up`/`pnpm dev` commands with their printed outputs, `node $S new-session`/`send "Claude Opus 5.5" "Say hello"`/`wait-idle 180` invocations, a real JS eval snippet, and a complete sqlite3 query — the common cases are all covered with concrete examples.

5 / 5

Workflow Clarity

The sequence is clear and ordered (find app → set CDP_URL → new-session first → send → wait-idle → shot/eval → world down), with real checkpoints like "wait-idle 180 # until the Run task button is back" and "Reload after state-heavy changes". It falls short of level 5 because there is no error-recovery loop: no guidance for what to do when a command fails, the CDP URL is stale, or the warned-about mid-run session switch occurs.

4 / 5

Progressive Disclosure

An under-50-line single-purpose skill with clean sections (Find the app / Commands / Rules); everything needed is inline and the one bundle file (scripts/cdp.mjs, invoked via the S= variable) is appropriately factored out as an executable rather than inlined. No external reference docs are needed, matching the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

92%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 names the domain, enumerates concrete capabilities, and gives an explicit 'Use when...' clause with natural trigger scenarios. The only gap is modest synonym coverage around the CDP/browser-automation vocabulary.

DimensionReasoningScore

Specificity

The description lists five concrete actions — "Evaluate JS, take screenshots, open a new session, send a prompt with a chosen model, wait for the run to finish" — which comprehensively cover the skill's command surface (eval, shot, new-session, send, wait-idle) with no generic filler.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' is the concrete action list ("Drive the running OpenWork app over CDP... Evaluate JS, take screenshots...") and the 'when' is explicit with concrete trigger phrases ("Use when checking a UI change by hand in a world or pnpm dev, or when reproducing a chat state").

5 / 5

Trigger Term Quality

Natural trigger terms like "screenshots", "UI change", "chat state", "pnpm dev", and "CDP" match what a user would say, but coverage is not comprehensive: synonyms such as "Chrome DevTools Protocol", "browser automation", or "devtools" are absent. Fits the 'good keyword coverage; a few natural terms missing' anchor rather than the level-5 synonym/extension-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"Drive the running OpenWork app over CDP" carves out a clear niche (one specific app, one specific mechanism) with distinct triggers like "reproducing a chat state"; minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

different-ai/openwork

Path

.opencode/skills/drive-desktop-cdp/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.