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

81%

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

Quality

Content

80%

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

The content is highly actionable and token-efficient, packed with concrete executable commands, but workflow sequencing has a numbering gap and lacks validation checkpoints for destructive operations, and all material is inline with no progressive file structure.

Suggestions

Fix the Quick Start numbering gap (section 2 jumps to section 4) so the sequence is unbroken.

Add an explicit validate/confirm checkpoint before the destructive 'daytona delete' command, e.g. a 'confirm no unsaved state' step.

Move the longer troubleshooting and 'Running with Den' material into reference files referenced from SKILL.md to establish a one-level-deep progressive disclosure structure.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven — tables of ports, copy-paste daytona CLI snippets, and short troubleshooting bullets — with almost no explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	It provides fully executable commands with exact arguments and ports (e.g. 'daytona preview-url ipollowork-dev -p 6080', screenshot capture scripts, restart commands), making the guidance copy-paste ready.	3 / 3
Workflow Clarity	The Quick Start is sequenced but skips from section 2 to section 4 (no section 3), and destructive operations like 'daytona delete' lack an explicit validate-then-proceed checkpoint or feedback loop, which the rubric caps at 2.	2 / 3
Progressive Disclosure	There are no bundle files; all ~166 lines live inline in SKILL.md with content that could be split out (full-stack Den options, troubleshooting), and the only references are to sibling skills rather than to a navigable file structure.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 a strong explicit 'Use when...' trigger clause with good keyword coverage and answers both what and when, but the capability statement is a vague 'overview' rather than concrete actions, and broad terms plus overlap with sibling skills raise distinctiveness risk.

Suggestions

Replace 'development environment overview' with concrete actions the skill performs (e.g. 'Launch, control, and troubleshoot the iPolloWork Electron app in a Daytona sandbox').

Narrow the broadest trigger terms ('dev environment', 'validation') or scope them to the Daytona context to reduce overlap with the focused sibling skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Daytona development environment overview' names the domain clearly but the only action verb is 'overview', which is vague rather than a list of concrete actions like the score-3 anchor requires.	2 / 3
Completeness	It states what the skill is ('Daytona development environment overview') and gives an explicit 'Use when the user asks about...' trigger clause, satisfying both the what and the when.	3 / 3
Trigger Term Quality	The 'Use when...' clause lists many natural terms a user would actually say — 'Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume' — giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Triggers are mostly Daytona-specific but broad umbrella terms ('dev environment', 'validation') plus shared terminology with sibling focused skills (CDP, Electron sandbox, standalone Chrome) create overlap risk where the wrong skill could trigger.	2 / 3
	Total	10 / 12 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: bd5caef

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