CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-workshop

Start, size, check, hand out, fix and stop a hands-on OpenWork workshop (one private Den + 1-99 Daytona desktops, fictional Outlook/Calendar/Drive/Jira/Confluence). Use when the user says "start the workshop", "give me N workshop desktops", "add seats", "send me the workshop links", "seat N is stuck", "reset the workshop" or "stop the workshop".

79

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 lean, fully executable runbook: every step is a concrete command with explicit validation gates, feedback loops, and guardrails on destructive operations. Content is appropriately split between the 49-line body and clearly signaled one-level-deep external files, with zero padding.

DimensionReasoningScore

Conciseness

Every line is operational — timing windows, per-wave durations, refusal handling, and link-safety rules — with no explanations of concepts Claude already knows; even exception notes ('Reset restores the fictional data only; sign-in and connections stay') state non-inferable facts, matching 'every token earns its place'.

5 / 5

Actionability

Commands are copy-paste ready with argument ranges and defaults ('start.sh <seats 1-99> <lifetime-minutes, default 360> <stage, default event> <budget-usd, default 200>'), concrete verification gates ('must both print PASS'), and a ready-to-paste links step, covering the common cases per anchor 5.

5 / 5

Workflow Clarity

The Start sequence has explicit checkpoints ('Read READY x/y'), a retry-once feedback loop with failure handling ('if it still fails, leave it out and say so'), and validation via PASS spot-checks; destructive and batch operations are guarded ('Only tear down stages you were asked to', budget-refusal before creating anything), so the missing-validation cap at 3 does not apply.

5 / 5

Progressive Disclosure

At 49 well-sectioned lines (Start / During / Stop), the body keeps only operational detail and clearly signals one-level-deep references for everything else ('details and the safety model are in worlds/WORKSHOP-FLEET.md'), with no nested references — matching the simple-skill pattern the rubric scores as 5.

5 / 5

Total

20

/

20

Passed

Description

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

An exemplary description: concise, third-person, and complete. It enumerates the full operational lifecycle with concrete parameters, then gives explicit 'Use when' guidance via seven verbatim user phrasings, all anchored to a highly distinctive domain.

DimensionReasoningScore

Specificity

Lists six concrete lifecycle actions ('Start, size, check, hand out, fix and stop') with concrete scope details ('one private Den + 1-99 Daytona desktops'), giving comprehensive coverage from launch to teardown; the anchor 4 'minor gaps in coverage' example does not apply.

5 / 5

Completeness

Explicitly answers both 'what' (first sentence enumerating the full lifecycle) and 'when' ('Use when the user says...' with concrete trigger phrases), exactly mirroring the anchor 5 pattern; a 'when' clause is present, so the completeness cap of 3 does not apply.

5 / 5

Trigger Term Quality

Seven verbatim, natural phrases users would actually say ('start the workshop', 'give me N workshop desktops', 'add seats', 'seat N is stuck', 'reset the workshop', 'stop the workshop'), matching the comprehensive synonym-level coverage of the anchor 5 example.

5 / 5

Distinctiveness Conflict Risk

A clear niche ('hands-on OpenWork workshop', 'Daytona desktops', 'Den') with distinct quoted triggers makes triggering for the wrong skill extremely unlikely, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

20

/

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: 5 missing, 4 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

different-ai/openwork

Path

.opencode/skills/launch-workshop/SKILL.md

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.