CtrlK
BlogDocsLog inGet started
Tessl Logo

daytona-chrome-cdp

Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

The canonical home for this skill is daytona-chrome-cdp in different-ai/openwork

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, fully-executable runbook with a clear sequenced workflow and built-in validation checkpoints. It assumes Claude's competence and wastes no tokens on background explanation.

DimensionReasoningScore

Conciseness

The body is lean and instructional throughout with no explaining of concepts Claude already knows; every section earns its tokens (launch command, CDP URL, verify step, flow calls, stop command).

3 / 3

Actionability

Provides fully executable, copy-paste-ready bash commands and concrete browser tool calls with real flags (e.g. --remote-debugging-port=9222, daytona preview-url), not pseudocode.

3 / 3

Workflow Clarity

A clear launch→connect→verify→drive→stop sequence with explicit validation checkpoints ("Verify It Is Not Electron" and "Do not assume navigation or sign-in worked until the post-action snapshot or URL proves it").

3 / 3

Progressive Disclosure

No bundle files exist and the body is under 50 lines with well-organized, clearly headed sections, so the simple-skill allowance applies and organization alone earns the top level.

3 / 3

Total

12

/

12

Passed

Description

100%

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 lean, third-person, and cleanly answers both what it does and when to use it, while explicitly disambiguating from a sibling Electron-CDP skill. It avoids fluff and over-claims throughout.

DimensionReasoningScore

Specificity

Names concrete actions ("Launch and control standalone Chrome ... via CDP") plus a specific runtime context, matching the anchor for multiple specific concrete actions rather than a single vague domain mention.

3 / 3

Completeness

Explicitly answers what ("Launch and control standalone Chrome in a Daytona sandbox via CDP") and when ("Use for web sign-in, OAuth ... or when the app should not be driven through Electron CDP"), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Covers natural use-case phrasings users would say ("web sign-in, OAuth, Den Web setup, browser-only flows"), giving good coverage of natural triggers for this niche rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

The closing clause "when the app should not be driven through Electron CDP" carves out a clear niche distinct from an Electron-CDP skill, making misfires unlikely.

3 / 3

Total

12

/

12

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.