cloud-dashboard-walkthrough

Drive the OpenWork Cloud dashboard (Den Web / app.openworklabs.com) as a real user via headless Chrome CDP — sign up, create an org, invite teammates, teams, plugins with skills, marketplaces, team access grants, desktop handoff. Use for cloud tutorials, dashboard screenshots, demo walkthroughs, or when a task says "create an org / invite teammates / create a plugin / assign a marketplace" on OpenWork Cloud.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

86%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.

An exceptionally actionable and concise runbook with exact commands, labels, and recovery loops for fragile operations. The main gap is progressive disclosure: all content lives in one file with no reference files split out, which is acceptable for a runbook but limits navigation.

Suggestions

Split the longer subtopics (e.g., 'Teammates actually joining' API path, 'Daytona preview URLs expire' recovery, 'daytona exec quirk') into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Add an explicit ordered, numbered sequence for the canonical end-to-end walkthrough (sign up → create org → invite → teams → plugins → marketplaces) so the primary flow reads as a guided workflow rather than only a reference table.

Consider extracting the route/label flow table into a separate quick-reference file while keeping a concise overview in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Lean and tactical throughout — exact routes, button labels, code blocks, and API payloads with no padding or explanation of concepts Claude already knows; the few prose Notes cover non-obvious domain gotchas (sudo modal, seat limit, daytona flag-eating) that earn their tokens.	5 / 5
Actionability	Fully executable guidance: copy-paste bash commands, JS DOM-setter snippets, exact REST endpoints with request bodies, and precise UI labels/routes covering the common dashboard flows.	5 / 5
Workflow Clarity	Routes and labels are presented in a clear reference table with verification checkpoints (runtime-config curl check, sudo-modal retry, seat-limit handling, preview-URL recovery with stack restart), but the primary flow is a lookup table rather than an explicitly ordered, numbered sequence with checkpoints, keeping it just below a 5.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections, but with no bundle files present everything is inlined into a single ~130-line SKILL.md and no external references are signaled; subtopics like the API join path or daytona quirks could be split out. Not a 2 because section structure is clean; not a 4 because there are no one-level-deep references at all.	3 / 5
	Total	17 / 20 Passed

Description

92%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.

A highly specific, well-constructed description that clearly states both capabilities and trigger conditions with concrete, natural-language cues. Only minor room for improvement in adding a few more synonyms or file/extension-style trigger terms.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — 'sign up, create an org, invite teammates, teams, plugins with skills, marketplaces, team access grants, desktop handoff' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (drive the dashboard end-to-end with enumerated actions) and 'when' ('Use for cloud tutorials, dashboard screenshots, demo walkthroughs, or when a task says...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural triggers ('cloud tutorials, dashboard screenshots, demo walkthroughs') plus quoted task phrases ('create an org / invite teammates / create a plugin / assign a marketplace'), though a few common synonyms are absent. Not a 5 because coverage is not exhaustive of synonyms/extensions, and not a 3 because several genuinely natural user phrases are present.	4 / 5
Distinctiveness Conflict Risk	Targets a very specific niche — the OpenWork Cloud dashboard via headless Chrome CDP — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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/cloud-dashboard-walkthrough/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.