SkillAgentSearch skills...

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.

Install / Use

npx skills add github/awesome-copilot --skill desk-open

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Tags

Our assessment of desk-open

desk-open scores 93/100 on our quality scale, 590th of 4,698 Development & Engineering skills we index (top 13%).

Its SKILL.md is 3.0 KB long, well organised into 9 sections with 2 code examples: a solid amount of guidance for an agent.

With 39,348 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so desk-open is actively maintained.
  • Our last check on 2026-10-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

desk-open compared with similar skills

All 4 of these similar skills score higher than desk-open; compare them before choosing.

SkillScoreStarsUpdatedFormat
desk-open (this skill)by github9339.3k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install desk-open?
Run npx skills add github/awesome-copilot --skill desk-open. The install tabs above show the steps for each supported agent.
Which AI agents does desk-open work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is desk-open safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is desk-open still maintained?
The repository was last updated about 2 months ago, so desk-open is actively maintained.

name: desk-open description: '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.'

Open a Desk

Create a new desk in the workshop with the standard structure.

When to use

  • The operator wants to start a new workstream
  • Work arrives that doesn't belong to any existing desk
  • A topic needs its own frame (its own history, its own priors)

What it creates

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

How to use

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

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

  3. Create the structure. Make the directory, initial journal, and signals folder:

    desks/<desk-name>/journal.md
    desks/<desk-name>/.signals/
    
  4. Write the first journal entry. The journal starts with:

    • What this desk is for (its focus/purpose)
    • What repos or work it covers (if applicable)
    • Any initial context the first session needs
  5. Announce it. Tell the operator what was created and what the desk's focus is.

Session orientation

This skill initializes storage — it does not launch a session. A desk becomes active when a Copilot session references its directory. The session workflow:

  1. The operator (or TA) starts a session and says "sit at the <desk-name> desk"
  2. The session reads desks/<desk-name>/journal.md to load priors
  3. Work happens — the session uses signal-write to emit signals and desk-journal to persist state at the end
  4. The next session repeats from step 2

The desk identity comes from which journal is read, not from a persistent process. Desks are long-running in state (the journal carries forward), not in runtime (each session is independent).

Journal format

# <Desk Name> — Journal

## <date> — Desk opened
- **Purpose:** <what this desk focuses on>
- **Scope:** <repos, areas, or work this desk covers>
- **Next step:** <what the first session should do>

Principles

  • A desk is a peer, not a sub-agent. It has equal standing to disagree with other desks.
  • The journal is the memory. Without it, the next session starts blind. Write enough that someone starting from zero finds the way.
  • One desk, one focus. If the scope is too broad, open two desks. Each desk's value comes from its specific frame — dilute the frame and you lose the value.

Related Skills

View on GitHub
GitHub Stars39.3k
CategoryDevelopment
Updated1mo ago
Forks5.0k

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions