CtrlK
BlogDocsLog inGet started
Tessl Logo

daytona-seeded-cloud-demo

Daytona seeded cloud demo, demo credentials, Acme Robotics seed. Use when the user asks to spin up, keep running, seed, or prepare an OpenWork Cloud/Den Daytona demo instance.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

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.

A strong, execution-ready skill body: copy-paste commands throughout, explicit validation checkpoints with expected outputs, and genuine error-recovery guidance. Its only weaknesses are minor duplication between the seed summary and the response template and a length that flirts with needing a split into reference files.

DimensionReasoningScore

Conciseness

The body is lean and command-first with no explanations of concepts Claude already knows, but the seed summary is duplicated in the response template and a few advisory sentences (e.g. "This is the most relevant browser-facing path") could be trimmed.

4 / 5

Actionability

Every step is fully executable copy-paste bash: sandbox creation with fallback naming, the full seed command with all env vars, the keepalive loop, and both auth validation curls with expected responses and credentials.

5 / 5

Workflow Clarity

The sequence (create → capture URLs → seed → keepalive → validate → report) is explicit, each risky step has validation checkpoints with expected results ("redirect: false", a token, user Alex Chen), and troubleshooting supplies feedback loops for the destructive --reset seed and the 403 email-verification failure.

5 / 5

Progressive Disclosure

As a self-contained single-file skill with no bundle files, it is well organized into clear sections with nothing buried; it slightly exceeds the ideal inline length since the troubleshooting and response-template sections could live in a reference file, keeping it just short of a 5.

4 / 5

Total

18

/

20

Passed

Description

73%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 well-scoped description with an explicit trigger clause and a clearly distinct niche, weakened only by a noun-phrase "what" that undersells the concrete actions the skill performs (create sandbox, seed data, validate login, return credentials).

Suggestions

Rewrite the "what" as concrete third-person actions, e.g. "Creates a server-only Daytona sandbox, seeds Acme Robotics demo data, validates demo login, and returns shareable URLs and credentials."

Add natural trigger synonyms such as "launch", "stand up", or "demo environment" alongside "spin up" and "prepare" to broaden natural-language matching.

DimensionReasoningScore

Specificity

The description names the domain and concrete items ("seeded cloud demo", "demo credentials", "Acme Robotics seed") but presents them as noun phrases rather than multiple specific concrete actions like creating a sandbox, seeding the database, or validating login.

3 / 5

Completeness

Both what and when are present, with an explicit "Use when the user asks to..." clause; the "what" portion is a terse noun list and could be more explicit about the actions performed, keeping it below a 5.

4 / 5

Trigger Term Quality

Natural user phrases are well covered ("spin up", "keep running", "seed", "prepare", "OpenWork Cloud/Den Daytona demo instance"), though a few natural synonyms such as "launch" or "demo environment" are missing.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (OpenWork Cloud/Den Daytona seeded demo) with product-specific trigger terms, making it unlikely to fire for the wrong skill.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
different-ai/openwork
Reviewed

Table of Contents

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.