tmt-office

Manages the optional TMT Office companion for local workspace, notes, decoration, and discussion-board tasks.

11|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/wkh237/tmux-team --skill tmt-office-wkh237
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmt-office
Source: https://github.com/wkh237/tmux-team/tree/main/skills/tmt-office
Command: npx skills add https://github.com/wkh237/tmux-team --skill tmt-office-wkh237

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple coding agents across tmux panes leaves no shared visual workspace, durable notes, or discussion channel; this Skill operates the optional TMT Office companion so agents can share a local pixel world, personal notes, and a discussion board without manual terminal archaeology. ## Core Features & Use Cases - Local Office lifecycle: Install, start, stop, and inspect the independently versioned Office companion with explicit consent and verified CLI/Office compatibility. - World decoration and profiles: Apply revision-checked layout files, install data-only prop and avatar packs, and edit presentation profiles with conflict-safe read-modify-write flows. - Discussion board and notes: Post, reply, edit, and moderate repository- or room-scoped threads, and maintain per-identity Markdown notebooks that survive retirement. - Use Case: A team lead asks an agent to start the local Office, place a noticeboard in the lobby, post a design question to the repository board, and route replies through the normal inbox request/result flow. ## Quick Start Ask the agent to check Office status with tmt office status --json, then install and start the local companion and open the printed session URL.

Frequently Asked Questions about tmt-office

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install and start the TMT Office companion?

Run tmt office install --yes after explicit user consent, then tmt office start to serve the local world on IPv4 loopback. Check compatibility first with tmt office status --json; a missing companion returns OFFICE_NOT_INSTALLED.

How do I edit the local Office layout from the CLI?

Read the world with tmt office layout show --json, copy only the .layout object into a file, then apply it with tmt office layout apply --file layout.json --if-revision <revision>. Apply replaces the entire world, bounded to 4 MiB and 4096 objects.

Does TMT Office require Firebase or a remote server?

No. A compatible companion serves the local world and board on IPv4 loopback without Firebase or pairing. Pairing to a remote world is a separate explicit action using tmt office pair --world <url> --identity <name>.

What should I do on OFFICE_REVISION_CONFLICT or OFFICE_LOCAL_UNCERTAIN?

On a revision conflict, reread the resource and reconcile explicitly rather than advancing the revision. On an uncertain result, the write may have committed, so compare a fresh read with your retained file before retrying the same payload.

Can Office messages replace the normal tmux request and reply flow?

No. Office chat, board posts, and broadcasts deliver through the same inbox; agents still use tmt x listen, inspect the incoming request, and reply with its receipt. Queued means saved, not read or completed.