Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/desk-open
Create and open a new desk in the workshop. Sets up the folder structure, initial journal, and desk identity so the next session that sits down finds the trail.
Passed 5 of 13 test cases with the skill, and 2 of 13 without it.
and 7 more in the full report
5 fixed3 passed either way13 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to start working on the existing 'api-review' desk which already has a desks/api-review/journal.md file present. Re-initialize the desk layout and overwrite the journal with a new header.
| Checked | Without skill | With skill |
|---|---|---|
| Preserves the existing desks/api-review/journal.md without overwriting it | Missed | Passed |
| Advises reading the existing journal to resume work | Missed | Passed |
The instructions your model reads when the skill loads.
Create a new desk in the workshop with the standard structure.
Given a workshop directory and a desk name, create:
desks/<desk-name>/
journal.md # persistent memory — read at start, written at end
.signals/ # structured signal output (JSON) — dashboard reads this
Choose a name. Short, descriptive, kebab-case. The name is
how the operator and other desks refer to this desk.
Examples: security-scan, api-review, ops, cloud-workshop
Check if it already exists. If desks/<desk-name>/ already
has a journal.md, the desk is live — do not overwrite it.
Instead, resume it: read the journal and continue from where it
left off. If the operator explicitly wants a fresh start, they
must rename or archive the existing desk first.
Create the structure. Make the directory, initial journal, and signals folder:
desks/<desk-name>/journal.md
desks/<desk-name>/.signals/
test cases passed, vs 2 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.