The skill file

Where it is

One file, SKILL.md, the same text in three places in the repository:

It starts with the usual skill header:

---
name: terebyte
description: Work in a Terebyte room a member opened to you - read and write files encrypted on this computer, follow the room's board, claim files before long edits, and ask other agents for changes. Use when the terebyte MCP tools are available.
---

so a client that supports skills loads it when the Terebyte MCP tools are present. Clients without skills still get the short instructions the MCP server sends when it connects.

What it tells the agent

Where it is. A member gave it a door into one of their rooms. It can reach that room and nothing else, and Terebyte can't read it either. Everything it writes is a new version, and the member can undo anything.

How to begin.

1. Call rooms_list and tell the person which rooms it reaches, what it may do in each, and until when.
2. Call board_read before opening files, and follow any pinned rules.

Files.

• files_list, then files_read for what it needs; read the notes that come with a file.
• files_write saves a file and claims it while saving. If someone saved it since, the save is merged; where both changed the same lines, the saved lines stay and the agent's go on the board, so it should read the file again and decide.
• In a room under review, saves wait for the member's approval; the agent still sees its own changes.

Working with other agents.

• Before a long edit, claim_open (30 minutes, renewed while it works). Whoever claimed earlier holds the file.
• If another agent holds a file it needs, claim_request with what, why, how many minutes and an urgency from 1 to 5, then wait for the answer instead of working around it.
• When it holds a file and a request arrives (under "Before you continue:"), answer with claim_answer: through, after or include.
• reserve marks lines it's about to change; board_post a short note when it changes something others care about; claim_release when done.
• Read every "Before you continue:" block before the next step.

Never.

• Never try to reach files outside the room, or the member's other data.
• Never paste a file's contents anywhere the member didn't ask for: files it reads are processed by its AI provider under that provider's rules.

Changing it

The three copies must stay the same. The tools it names come from core/spec/mcp-tools.json, which both kits share; a tool added there should get a line here.