daytona-flow-validator

do e2e tests, validate feature, prove it works, pass/fail, testkit tape, screenshots, CDP assertions. Daytona validation loop for real app behavior with repair before declaring success.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/daytona-flow-validator/SKILL.md

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 body is a high-quality, actionable validation playbook with executable commands, explicit validation/repair feedback loops, and clear sequencing. Its main weakness is the absence of bundle files to offload the longer command catalogs, leaving a fairly long single document.

Dimension	Reasoning	Score
Conciseness	The body is operational and command-dense, assuming Claude's competence, but sections like Screenshots and Human-Visible Demo Standard carry prose rules that could be trimmed.	4 / 5
Actionability	Copy-paste ready bash snippets, a runnable synthetic-paste JS function, and concrete browser_screenshot/daytona exec commands cover the common cases fully.	5 / 5
Workflow Clarity	Explicit 5-step Observe-Act-Observe-Assert-Capture and Repair loops with validation checkpoints, plus failure-handling feedback loops and a Final Verdict checklist, sequence the work clearly.	5 / 5
Progressive Disclosure	No bundle files exist, but the single file is well-sectioned with clearly signaled cross-skill references (prove-a-pr, write-a-spec, run-tests, daytona-recording-artifacts); some inline command catalogs could move to reference files.	4 / 5
	Total	18 / 20 Passed

Description

58%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 conveys a concrete, distinctive Daytona validation capability but omits any explicit 'when to use' trigger guidance and leans on technical jargon over natural user phrasing. Tightening the vague filler and adding a 'Use when...' clause would lift completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when validating a Daytona Electron or browser flow end to end before declaring a feature works.'

Replace jargon-heavy phrases ('CDP assertions', 'Daytona validation loop', 'testkit tape') with natural terms a user would say, keeping the technical detail for the body.

Cut vague filler like 'prove it works' so every phrase names a concrete action.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('testkit tape, screenshots, CDP assertions', 'repair before declaring success') alongside a Daytona validation loop, but pads them with vague filler like 'prove it works'.	4 / 5
Completeness	The 'what' is clear (validate Daytona flows end to end) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	Some natural terms appear ('e2e tests', 'pass/fail', 'screenshots') but they sit alongside heavy jargon ('CDP assertions', 'Daytona validation loop', 'testkit tape') and lack common synonyms users would actually say.	3 / 5
Distinctiveness Conflict Risk	The Daytona-specific validation niche is mostly distinct with minimal conflict risk, though the broad opening ('do e2e tests, validate feature') leaves minor overlap with generic testing skills.	4 / 5
	Total	14 / 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: different-ai/openwork
Path: .opencode/skills/daytona-flow-validator/SKILL.md
Commit: 7b76a2b

Reviewed: 3 days 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.