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

76%

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 with concrete commands and good section structure, but the Quick Start workflow has a numbering error and lacks explicit validation checkpoints after sandbox creation. Fixing the step sequence and adding a verify step would notably improve workflow clarity.

Suggestions

Fix the Quick Start numbering (1, 2, 4 → 1, 2, 3) and add an explicit validation checkpoint such as 'Verify the sandbox is running: `daytona list` shows ipollowork-dev as started' before opening the noVNC URL.

Convert the focused-skill bullets into markdown links or a clearer 'See also' navigation block so the one-level-deep references are unmistakable.

Consider moving the long Common Commands and Troubleshooting blocks into a reference file to keep SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and tables with little padding of concepts Claude already knows; only the 'Running with Den (full stack)' MySQL/Docker context drifts into explanation that could be trimmed, placing it just below the fully-lean anchor.	4 / 5
Actionability	It provides copy-paste-ready commands throughout — `bash .devcontainer/test-on-daytona.sh`, `daytona preview-url ipollowork-dev -p 6080`, the Common Commands block, and specific troubleshooting commands — fully executable and covering the common cases.	5 / 5
Workflow Clarity	The Quick Start steps are sequenced but numbering is broken (jumps 1, 2, 4 with no step 3) and there are no explicit validation checkpoints verifying the sandbox/URL came up; checkpoints are only implicit, matching the 'steps listed but validation gaps' anchor.	3 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Prerequisites, Quick Start, What's Running, Common Commands, Troubleshooting) and points to focused sibling skills, but no bundle files exist and the sibling-skill references are plain bullets rather than navigable links, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

76%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 trigger-term coverage and a clear 'Use when' clause, but its 'what' statement is a vague 'overview' rather than concrete capabilities. Tightening the opening to name specific actions would lift specificity and completeness.

Suggestions

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

Keep the strong trigger-term list but consider adding the file/protocol extensions users mention (e.g. .sh helper scripts, port 6080/9825) to make triggers even more natural.

Dimension	Reasoning	Score
Specificity	The phrase 'Daytona development environment overview' names the domain but the only 'action' is the vague noun 'overview' — it does not list concrete actions like launch, start, inspect, or connect, matching the anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	It has both a 'what' ('Daytona development environment overview') and an explicit 'when' ('Use when the user asks about...'), but the 'what' is a weak overview statement rather than concrete capabilities, so it sits at the anchor where both are present yet the 'what' could be more specific.	4 / 5
Trigger Term Quality	It lists a comprehensive set of natural trigger terms users would say in this domain — 'Daytona setup', 'Daytona toolbox', 'dev environment', 'noVNC', 'CDP', 'server sandbox', 'secrets volume', 'Electron sandbox', 'standalone Chrome', 'validation', 'artifacts volume' — including multiple synonyms, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The niche Daytona-specific terms (noVNC, CDP, Electron sandbox, Daytona toolbox, secrets/artifacts volume) carve a clear trigger niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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: 52934c1

Reviewed: about 14 hours 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.