daytona-electron-den

Electron and Den, desktop plus cloud, two-sandbox e2e, cloud auth, marketplace, org policy, worker proxy, provider sync, desktop handoff. Validate Electron against a Daytona Den server with unified proof.

Quality

51%

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-electron-den/SKILL.md

Quality

Content

92%

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 strong, concise, actionable playbook with a well-sequenced workflow and explicit validation checkpoints. The only gap is progressive disclosure: with no bundle/reference files present, content is fully inline and references are unverifiable.

Suggestions

Add a brief references section listing the actual referenced scripts/skills (e.g. .devcontainer/test-server-on-daytona.sh, .devcontainer/test-on-daytona.sh, the server skill, daytona-flow-validator) so links are real and discoverable.

Consider extracting the per-feature assertion checklist (marketplace, policy, provider sync, worker proxy) into a bundled reference file to keep the overview leaner and support one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean: it jumps straight into executable bash and JS snippets with minimal prose, assumes Claude knows the tooling, and avoids explaining what Electron/Daytona/Den are — every token earns its place.	3 / 3
Actionability	It provides copy-paste-ready, concrete commands (bash scripts with flag examples, curl health checks, a JS one-liner, daytona exec invocation) plus explicit expected assertions, so the guidance is fully executable.	3 / 3
Workflow Clarity	A clear multi-step sequence (start server → record values → start Electron → validate bootstrap → handoff → feature loop) with explicit validation checkpoints (health curls, bootstrap assertion, the 5-step daytona-flow-validator loop) and feedback expectations for recovery.	3 / 3
Progressive Disclosure	No bundle files exist and the body references external scripts (.devcontainer/*.sh) and another skill ('server skill', 'daytona-flow-validator') without in-repo references to verify, and the single SKILL.md is well-organized but carries all content inline with no split reference files.	2 / 3
	Total	11 / 12 Passed

Description

10%

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 richly specific about capabilities but lacks an explicit 'Use when...' trigger clause, which caps completeness at 2 and is the main weakness. It is concise and largely distinct, though trigger-term naturalness leans on product jargon.

Suggestions

Add an explicit trigger clause such as 'Use when validating Electron desktop behavior against a Daytona Den server, or when e2e cloud auth, marketplace, org policy, worker proxy, or provider sync must be verified across two Daytona sandboxes.'

Soften the product-jargon density by including a couple of natural user phrases (e.g. 'two-sandbox e2e test', 'desktop cloud auth') so users and Claude recognize the trigger more readily.

Dimension	Reasoning	Score
Specificity	The description lists numerous concrete actions: 'two-sandbox e2e', 'cloud auth', 'marketplace', 'org policy', 'worker proxy', 'provider sync', 'desktop handoff', 'Validate Electron against a Daytona Den server with unified proof' — far more than a bare domain name.	3 / 3
Completeness	It states what the skill does in detail but never gives an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should invoke it, which caps completeness at 2 per the guidelines.	1 / 3
Trigger Term Quality	Terms like 'Electron', 'Daytona', 'Den', 'cloud auth', 'marketplace', 'provider sync' are natural for this niche, but coverage is heavy on product jargon with no common user phrasing variations, so it is not fully comprehensive.	2 / 3
Distinctiveness Conflict Risk	The combination of Electron + Daytona Den + specific cloud features is fairly distinctive, but the dense jargon string could overlap with sibling Daytona/server skills, keeping it from a clearly niche-free 3.	2 / 3
	Total	8 / 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-electron-den/SKILL.md
Commit: bd5caef

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.