Desk
Start, watch and answer bork `do` runs from a coordinating Claude session (in a herdr tab or over Remote Control); a Codex session inside its sandbox can only wait, show, ack and sometimes answer. Use to start a do run in a repo, wait for runs without polling, see which are done, in progress, blocked or need the user, and relay and answer their needs-me questions. Not for the backlog or Crew; matt:orchestrator owns those.
Install
/plugin marketplace add borkweb/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borkweb/skills --skill deskgit clone --depth 1 https://github.com/borkweb/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/core/desk ~/.claude/skills/deskPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Run desk for bork `do` runs
A run is a directory under `${AGENT_HANDOFFS_DIR:-~/.agent-handoffs}/runs/` holding `run.json`. The file is the center: any session that can run `runs.mjs` can coordinate. A Claude session (in a herdr tab or over Remote Control) can do the whole loop; `start` needs herdr reachable, and nothing here is headless. A Codex session inside its sandbox can `wait`, `show` and `ack`, and can `answer` only where it can write the runs home. It cannot `start` runs, and its `answer` cannot send the architect its pane line, so tell the user to continue in the architect's tab.
`runs.mjs` lives beside this `SKILL.md`. Resolve it from the path this skill was loaded from and call `node <skill dir>/runs.mjs <command>`. Pane lines never carry a path.
`matt:orchestrator` owns the backlog and Crew. This skill never reads or writes either. A backlog task may link a run id; that is recorded, nothing more.
`orchestrator.json` is machine-local state in `ORCHESTRATOR_HOME` (a git repo); never commit it.
## Scope
The coordinator relays; the `do` run does the work.
- Start a run only when the user asks for one. Never start a run for work you were not given, and never start a follow-up run on your own judgment.
- Pass the user's goal to `--goal` unchanged, and the user's words to `tell` unchanged. Do not rewrite, expand or narrow either.Details
- Skill name
desk- Repository
- borkweb/skills
- Path
skills/core/desk/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Desk skill do?
Start, watch and answer bork `do` runs from a coordinating Claude session (in a herdr tab or over Remote Control); a Codex session inside its sandbox can only wait, show, ack and sometimes answer. Use to start a do run in a repo, wait for runs without polling, see which are done, in progress, blocked or need the user, and relay and answer their needs-me questions. Not for the backlog or Crew; matt:orchestrator owns those.
How do I install the Desk skill?
Claude Code plugin: /plugin marketplace add borkweb/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Desk popular?
It lives in borkweb/skills, which has 9 GitHub stars and 0 forks.
Related skills
Prototype
9borkweb/skills
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
Agents Md Lint
9borkweb/skills
Audit and trim AI agent instruction files (AGENTS.md, CLAUDE.md, CONVENTIONS.md, .cursorrules, etc.) by testing which facts an AI agent can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim any agent instruction file in a repository. Removes redundant documentation that wastes context tokens. Supports a dry-run mode that reports findings without modifying files.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
Session Budget
9borkweb/skills
Assess whether compacting or clearing the current session is worth it right now, and whether a reinit-ready handoff that survives /clear would carry real value. Not a threshold nag — it X-rays context composition (how much is stale vs. still load-bearing), which only the agent can see. Use when the user says "session budget", "should I compact", "should I clear", "is this session getting heavy", "token budget", invokes /session-budget, or when the budget hook requests a proactive assessment.
Cmd Skills Review
9Olshansk/agent-skills
Audit personal skills for redundancy, verbosity, weak triggers, and overlap. Runs a Claude→Codex review loop, presents per-item approval checkboxes, then applies approved edits and updates README and agent metadata. Use when asked to "review my skills", "audit my skills", "revisit my skills", or "clean up my skills". Accepts an optional skill name to scope the review to a single skill.
Agent Framework Azure AI Py
9huytran1120/vietnam-agentic-skills
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.