daytona-dev

Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/daytona-dev/SKILL.md

Quality

Content

76%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 body is highly actionable and reasonably concise, with good section structure and clear pointers to focused skills. Its main weakness is workflow clarity: destructive and risky operations lack explicit validation/verification checkpoints and the step numbering has a gap.

Suggestions

Add explicit verification steps after sandbox creation/start (e.g. confirm noVNC URL loads, check /tmp/electron.log for a ready signal) before proceeding.

Insert a confirmation/validation gate before destructive commands like `daytona delete ipollowork-dev` (e.g. verify artifacts are captured, prompt to confirm).

Fix the Quick Start numbering (it jumps from "2. Get the noVNC URL" to "4. Get other URLs", missing step 3).

Dimension	Reasoning	Score
Conciseness	The body is mostly commands, tables, and concrete fixes with little padding or explanation of concepts Claude already knows; a few prose passages (e.g. the Den options) could be trimmed slightly.	4 / 5
Actionability	It is full of copy-paste-ready, executable commands (daytona preview-url, daytona exec, daytona ssh, helper scripts) plus a port table, covering the common setup and debugging cases concretely.	5 / 5
Workflow Clarity	Quick Start lists numbered steps with concrete commands, but there are no validation/verification checkpoints and destructive operations ("daytona delete ... destroys everything") lack confirmation steps; the numbered list also skips step 3, so the destructive-operations cap applies.	3 / 5
Progressive Disclosure	Content is well organized into clear sections (Prerequisites, Quick Start, What's Running, Common Commands, Troubleshooting) with signaled references to focused skills and helper scripts; no bundle files exist, so structure is judged on the single file, which is appropriately sectioned with minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

68%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 has strong, explicit trigger guidance and high distinctiveness, but its "what" statement is a generic "overview" rather than concrete capabilities. Tightening the capability statement would lift specificity and completeness.

Suggestions

Replace "development environment overview" with concrete actions, e.g. "Launch, debug, and inspect the iPolloWork Electron app in a Daytona cloud sandbox."

Lead with the capability clause before the "Use when" list so the "what" is as concrete as the "when".

Dimension	Reasoning	Score
Specificity	The phrase "Daytona development environment overview" names the domain but the only stated action is "overview," which is generic and minimal rather than concrete actions like launch, configure, or debug.	2 / 5
Completeness	Both "what" (development environment overview) and "when" (an explicit "Use when the user asks about..." clause with many triggers) are present; the "what" is somewhat weak ("overview") which keeps it just below a 5.	4 / 5
Trigger Term Quality	The "Use when" clause lists many natural terms (Daytona setup, dev environment, noVNC, CDP, secrets volume, standalone Chrome, validation, artifacts volume) with good synonym coverage, though a few natural phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	The trigger set is tightly scoped to Daytona/iPolloWork-specific concepts (noVNC, CDP, Electron sandbox, secrets volume), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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: Devin-AXIS/iPolloWork
Path: .opencode/skills/daytona-dev/SKILL.md
Commit: 98deb63

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.