Skip to content
Skills Library
Education · Automation

launch-workshop

/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".

Repository
openwork ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

start the workshopgive me N workshop desktopsadd seatssend me the workshop linksseat N is stuckreset the workshopstop the workshop
Original author description

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".

How it works

  1. Start ("start the workshop with N seats")
  2. During the workshop
  3. Stop
Original SKILL.md headings · 52 lines, 367 words
SKILL.md preview
---
name: launch-workshop
description: 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".
---

# Launch a workshop

Scripts live in `scripts/workshop/` (run from the repo root); details and the
safety model are in `worlds/WORKSHOP-FLEET.md`. Private output (attendee links,
member test logins) goes to `~/.openwork/workshops/<stage>/`. Never paste
viewer links anywhere except the facilitator's own conversation unless they ask:
each link controls one attendee's desktop.

## Start ("start the workshop with N seats")

1. Timing: 60–120 minutes before the session, never more than ~3 hours before
   (workplace OAuth approvals last about 8 hours).
2. Confirm the size and cost in one line, then run in the foreground (~2 minutes
   per wave of ten seats, plus ~2.5 minutes for the Den):
   ```sh
   scripts/workshop/start.sh <seats 1-99> <lifetime-minutes, default 360> <stage, default event> <budget-usd, default 200>
   ```
   It refuses (before creating anything) if the estimate exceeds the budget, the
   team quota can't fit the seats, or the app commit isn't merged into dev.
   Report that message; don't work around it. A different `<stage>` name gives
   an independent second launch (its own Den; seats can't share skills across
   launches).
3. Read `READY x/y`. For each `NOT READY` seat run
   `scripts/workshop/seat.sh attendeeNN prepare <stage>` once; if it still fails,
   leave it out and say so.
4. Spot-check: `seat.sh attendee01 status <stage>` and `seat.sh attendee01 task
   <stage>` must both print `PASS`; then `seat.sh attendee01 prepare <stage>` so
   the seat starts on a fresh task.
5. `scripts/workshop/links.sh <stage>` prints one ready-to-paste message per
   seat; give it to the facilitator verbatim.

## During the workshop

| Request | Command |
|---|---|
| Seat frozen / black screen | `seat.sh attendeeNN unlock <stage>` (attendee reloads the page) |
| Task stuck / running forever | `seat.sh attendeeNN stop <stage>` |
| "My data is a mess" | `seat.sh attendeeNN reset <stage>` |
| Model missing / no composer | `seat.sh attendeeNN prepare <stage>` |
| Is this seat OK? | `seat.sh attendeeNN status <stage>` |
| Resend a link | `seat.sh attendeeNN link <stage>` |
| More seats | a new launch: `start.sh <n> <minutes left> <new-stage>` |

Reset restores the fictional data only; sign-in and connections stay, chats
and desktop files remain.

## Stop

`scripts/workshop/stop.sh <stage>` for each stage the facilitator names. Only
tear down stages you were asked to.

Versions

The database has no other skills named launch-workshop.

Database snapshot: 13.11.2026 · package version a00a4f9c60be (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100workshop
    Workshop coach for the Research Desk (SEC agents) workshop. Use when the user types /workshop, asks for a workshop act or module ("act 2", "next act", "where am I"), wants a TODO(workshop-N) implemented or explained, or asks for help following WORKSHOP.md.
  • 100daytona-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.
  • 90workshop-style
    Hands-on workshop — the learner works through the course instead of watching it, with an exercise or a check every couple of pages, short slides that only set up the next task, guiding narration that asks more than it tells, and a closing page where the pieces come together in…
  • 100workshop-deployment
    Package code and assets, sync to S3, and push content to AWS Workshop Studio. Use when deploying workshop changes or when asked to update the workshop.
  • 100run-tests
    Run the tests, run one spec, run e2e locally or on Daytona, investigate a skipped spec. Use for executing @openwork/testkit agent-first verification.
  • 100daytona-chrome-cdp
    Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.