daytona-recording-artifacts

screenshots, recording, presentation artifacts, validate visually. Supplementary Daytona screenshots and optional videos after testkit validation.

Quality

67%

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-recording-artifacts/SKILL.md

Quality

Content

81%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, executable commands and strong validation feedback loops throughout the workflow. Its main weakness is repetition of the http-server and preview-url command patterns across sections, and a long monolithic file that could benefit from splitting some material into references.

Suggestions

Consolidate the repeated 'python3 -m http.server 8090' and 'daytona preview-url ... -p 8090' patterns into one parameterized snippet referenced from each section to reduce redundancy.

Move the Volume layout, Before/After Flow, and Recording Standard sections into separate reference files linked from the overview to improve progressive disclosure.

Add a short ordered checklist at the top (capture -> verify non-zero -> get URL -> confirm 200 OK) so the end-to-end flow is scannable before the detailed sections.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the 'python3 -m http.server 8090' invocation and 'daytona preview-url ... -p 8090' pattern recur across the default, fallback, and URL-refresh sections and could be consolidated, fitting 'mostly efficient but could be tightened'.	3 / 5
Actionability	Commands are concrete and copy-paste ready with real flags (e.g. 'daytona exec ... python3 -m http.server 8090 --directory ...', 'ffprobe -v error -show_entries format=duration'), covering capture, serve, verify, and URL retrieval with only standard variable placeholders.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops: verify files are non-zero before sharing, ffprobe duration checks with 'not usable evidence' failure handling, 'curl -I returns 200 OK' before sharing refreshed URLs, and PNG inspection with recapture on mismatch.	5 / 5
Progressive Disclosure	A single well-sectioned file with clear headers and no nested references, but at ~230 lines some content (the volume layout, before/after flow, recording standard) could be split into one-level-deep reference files rather than inlined, leaving it at 'good structure; minor organization gaps'.	4 / 5
	Total	17 / 20 Passed

Description

53%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 clear purpose and domain but lacks an explicit 'Use when...' trigger clause, capping completeness, and its trigger-term coverage misses common synonyms and file extensions. It is reasonably distinct thanks to the Daytona branding.

Suggestions

Add an explicit trigger clause, e.g. 'Use when collecting supplementary screenshots or video clips of a Daytona UI journey for PR/eval presentation, after testkit validation.'

Broaden trigger terms with natural synonyms and extensions users actually say ('demo', 'capture', '.png', '.mp4', 'screen recording').

Lead with concrete verbs ('Capture', 'Serve', 'Publish') instead of noun lists to lift specificity above a 3.

Dimension	Reasoning	Score
Specificity	Names the domain ('screenshots, recording, presentation artifacts') and one concrete action ('validate visually'), but the items are artifact-nouns rather than a comprehensive list of actions, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	The 'what' is clear (supplementary Daytona screenshots and optional videos) but the 'when' is only weakly implied via 'after testkit validation' with no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user might say ('screenshots', 'recording', 'videos'), but misses common variations/synonyms like 'demo' or 'capture' and any file extensions (.png/.mp4), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Daytona' qualifier carves a clear niche for UI-journey presentation artifacts with only minor overlap risk against sibling daytona-* skills, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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-recording-artifacts/SKILL.md
Commit: ce5ef7d

Reviewed: 8 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.