CtrlK
BlogDocsLog inGet started
Tessl Logo

daytona-cloud-instance

Daytona cloud instance, Den server, OpenWork Cloud, Marketplace onboarding, desktop plus cloud e2e, frame proof. Use when launching, validating, or recording Daytona cloud/Den flows.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/daytona-cloud-instance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced operational runbook with strong validation checkpoints and feedback loops; its main weakness is moderate length with everything inlined into one file rather than split across references.

DimensionReasoningScore

Conciseness

The body is dense with executable commands and mostly assumes Claude's competence; a few rationale paragraphs (e.g. why production Den Web is preferred over Next dev) are operationally relevant but could be trimmed slightly, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Numerous copy-paste ready bash, curl, and JS snippets with concrete ports, URLs, and credentials (e.g. 'daytona preview-url "$SERVER_SANDBOX" -p 3005', the localStorage injection block) fully cover the common cases.

5 / 5

Workflow Clarity

A clear sectioned sequence with explicit validation checkpoints ('Validate the server before driving UI', 'Then verify', the 10-step recording flow) plus error-recovery feedback loops (403 -> restart Den API, 503 vs direct, hang -> second status command) and a screenshot safety checklist.

5 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is organized into clear, well-labeled sections; content is appropriately inline for operational procedure, but at ~170 lines some sub-procedures (e.g. the recording checklist) could be split out, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

66%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 highly distinctive with an explicit 'Use when' trigger and three action verbs, but the 'what' is delivered as a noun-phrase component list and trigger terms are narrow product jargon without synonyms or variations.

Suggestions

Convert the opening noun list into verb-phrased capabilities, e.g. 'Launches and validates Daytona cloud/Den sandboxes, collects desktop and Marketplace sign-in URLs, and records cloud-to-desktop e2e proofs.'

Add natural user-facing variations and synonyms to the trigger clause (e.g. 'onboarding demos', 'cloud sandbox validation', 'Den server recording') beyond the product names.

Tighten the 'what' to name 3-5 concrete actions (launch sandbox, expose service ports, collect preview URLs, validate auth, record proof) rather than listing component nouns.

DimensionReasoningScore

Specificity

Phrases 'launching, validating, or recording Daytona cloud/Den flows' give three concrete actions, but the lead is a noun-phrase component list ('Daytona cloud instance, Den server, OpenWork Cloud, Marketplace onboarding') rather than verb-driven capabilities, so coverage is not comprehensive.

3 / 5

Completeness

Both 'what' (component list) and 'when' ('Use when launching, validating, or recording Daytona cloud/Den flows') are present, but the 'what' is a comma-separated noun list rather than crisp verb phrases, so it falls just short of the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Product-specific terms ('Daytona cloud', 'Den', 'OpenWork Cloud', 'Marketplace onboarding') are natural within this project but lack synonyms, file extensions, or common variations, matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Highly specific product terminology ('Daytona cloud', 'Den', 'OpenWork Cloud', 'Marketplace') carves a clear niche with distinct triggers and minimal risk of triggering for unrelated skills.

5 / 5

Total

15

/

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.