book-desk
Skill2 starsChanged 5 months agoMITView on GitHub
Book office desks via OfficeSpace API for configured days of the week (default Mon/Tue/Wed). Use when the user asks to book desks, book their desk, or run the desk booker.
In this repository37 other files it gives its agents.
- commercial-insightSkill
- data-requestSkill
- scenario-modelSkill
- duckdbSkill
- intelligence-internal-commsSkill
- market-intelSkill
- sql-reviewSkill
- xlsxSkill
- docxSkill
- pdfSkill
- pptxSkill
- theme-factorySkill
- utility-markitdownSkill
- thinkcellSkill
- clevel-reviewSkill
- exec-commsSkill
- partner-reviewSkill
- working-constructSkill
- route-taskSkill
- pm-customer-journeySkill
- pm-exec-onboardingSkill
- pm-problem-statementSkill
- pm-proto-personaSkill
- pm-storyboardSkill
- pm-user-storySkill
- kanban-curateSkill
- epic-builderSkill
- exec-summarySkill
- steerco-packSkill
- program-trackerSkill
- weekly-reviewSkill
- draw-excalidraw-diagramSkill
- mcp-builderSkill
- notion-workboardSkill
- smartsheetSkill
- utility-transcribeSkill
- writing-humanizerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
No session (first run or expired) — run headed for SSO login:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Desk Booker
Books the configured desk (or a fallback from the configured zone/floor) for Mon/Tue/Wed of next week via the OfficeSpace GraphQL API.
Configure your desk ID and tenant URL via environment variables before running (see README.md).
Step 1: Check session
ls ~/.claude/skills/desk-booker/.session.json 2>/dev/null && echo "Session found" || echo "No session"Step 2: Run
Session exists — run headless:
cd ~/.claude/skills/desk-booker && node book-desk.js --headlessNo session (first run or expired) — run headed for SSO login:
cd ~/.claude/skills/desk-booker && node book-desk.jsStep 3: Report
Summarise which desks were booked per day, any failures, and whether the configured target desk or a fallback was used.
Troubleshooting
Session expired:
rm ~/.claude/skills/desk-booker/.session.json && cd ~/.claude/skills/desk-booker && node book-desk.jsDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.