Source profileQuality 81/100

github/awesome-copilot/skills/desk-open/SKILL.md

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.

Source repository stars
37,126
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

  • 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)

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/github/awesome-copilot --skill "skills/desk-open"
Safe inspection promptEditorial

Inspect the Agent Skill "desk-open" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/desk-open/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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

    Choose a name. Short, descriptive, kebab-case. The name isCheck if it already exists. If desks// alreadyCreate the structure. Make the directory, initial journal,
  2. 02

    When to use

    The operator wants to start a new workstream

    The operator wants to start a new workstreamWork arrives that doesn't belong to any existing deskA topic needs its own frame (its own history, its own priors)
  3. 03

    What it creates

    Given a workshop directory and a desk name, create:

    Given a workshop directory and a desk name, create:
  4. 04

    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:

    The operator (or TA) starts a session and says "sit at theThe session reads desks//journal.md to load priorsWork happens — the session uses signal-write to emit signals

Permission review

Static risk signals and limitations

Writes files

medium · line 33

The documentation asks the agent to create, modify, or delete local files.

**Create the structure.** Make the directory, initial journal,

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score81/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars37,126SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
github/awesome-copilot
Skill path
skills/desk-open/SKILL.md
Commit
9933dcad5be5caeb288cebcd370eeeb2fc2f1685
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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.