メニュー
Durable asynchronous messaging channel for inter-agent communication. Implements write-once read-many filesystem mail using atomic writes and directory-based mailboxes.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill mail-asyncコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.
Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.
Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.
| name | mail-async |
| description | Durable asynchronous messaging channel for inter-agent communication. Implements write-once read-many filesystem mail using atomic writes and directory-based mailboxes. |
| type | skill |
| category | state |
| status | stable |
| origin | tibsfox |
| modified | false |
| first_seen | "2026-03-06T00:00:00.000Z" |
| first_path | .claude/skills/mail-async/SKILL.md |
| superseded_by | null |
Filesystem-backed durable messaging for multi-agent orchestration. Every message is a JSON file written atomically into a per-agent mailbox directory. Messages are never lost -- the write-then-rename pattern guarantees that a reader sees either a complete message or no message, never a partial write.
Mail is the high-bandwidth, durable communication channel in the Gastown chipset -- the PCIe equivalent. It carries work assignments from the mayor, completion reports from polecats, merge notifications from the refinery, and coordination messages between any pair of agents. Because messages persist on disk, they survive process crashes, agent restarts, and network disconnections.
.chipset/state/mail/{agent-id}/{timestamp}-{from-agent}.json
Each agent has a dedicated mailbox directory. Incoming messages are named with the creation timestamp and sender ID, guaranteeing unique filenames and natural chronological ordering when listing the directory.
Example paths:
.chipset/state/mail/polecat-alpha/2026-03-05T10-30-00Z-mayor-a1b2c.json
.chipset/state/mail/polecat-alpha/2026-03-05T10-31-00Z-witness-d3e4f.json
.chipset/state/mail/mayor-a1b2c/2026-03-05T10-32-00Z-polecat-alpha.json
{
"from": "mayor-a1b2c",
"to": "polecat-alpha",
"type": "work_assignment",
"subject": "Bead gt-abc12 assigned to your rig",
"body": "Implement the auth middleware as specified in the convoy plan. Priority P1.",
"timestamp": "2026-03-05T10:30:00Z",
"read":
| Field | Type | Required | Description |
|---|---|---|---|
from | string | yes | Sender agent ID |
to | string | yes | Recipient agent ID |
type | string | yes | Message type (see Message Types below) |
subject | string | yes | Short summary for logs and listings |
body | string | yes | Full message content |
timestamp | string | yes | ISO 8601 creation timestamp |
read | boolean | yes | Whether recipient has processed this message |
priority | string | yes | urgent, normal, or low |
| Type | Sender | Recipient | Purpose |
|---|---|---|---|
work_assignment | mayor | polecat | New bead assigned via hook |
completion_report | polecat | mayor | Bead work completed |
merge_notification | refinery | mayor | Merge result (success or conflict) |
health_escalation | witness | mayor | Agent stall detected |
coordination | any | any | General-purpose coordination |
The send protocol uses atomic writes to guarantee durability.
{ISO-timestamp}-{from-agent}.json (replace colons with dashes in timestamp for filesystem compatibility).chipset/state/mail/{to}/.msg.tmpasync function sendMail(message: MailMessage): Promise<void> {
const mailDir = join(stateDir, 'mail', message.to);
await mkdir(mailDir, { recursive: true });
const safestamp = message.timestamp.replace(/:/g, '-');
const filename = `${safestamp}-${message.from}.json`;
const filePath = join(mailDir, filename);
const content = serializeSorted(message);
const tmpPath = join(mailDir, '.msg.tmp');
const fd = await open(tmpPath, 'w');
try {
await fd.writeFile(content, 'utf-8');
await fd.sync();
} finally {
await fd.close();
}
await rename(tmpPath, filePath);
}
Agents poll their mailbox directory on each state cycle. Polling returns all JSON files sorted by filename (which is sorted by timestamp due to the naming convention).
async function checkMail(agentId: string): Promise<MailMessage[]> {
const mailDir = join(stateDir, 'mail', agentId);
let files: string[];
try {
files = (await readdir(mailDir)).filter(f => f.endsWith('.json')).sort();
} catch {
return []; // No mailbox yet
}
const messages: MailMessage[] = [];
for (const file of files) {
const msg = await readJson<MailMessage>(join(mailDir, file));
if (msg) messages.push(msg);
}
return messages;
}
Filter by read === false to get only unprocessed messages:
const unread = (await checkMail(agentId)).filter(m => !m.read);
Update the read field atomically by rewriting the message file:
async function markRead(agentId: string, filename: string): Promise<void> {
const filePath = join(stateDir, 'mail', agentId, filename);
const msg = await readJson<MailMessage>(filePath);
if (!msg || msg.read) return;
msg.read = true;
await atomicWrite(filePath, serializeSorted(msg));
}
Messages older than 24 hours are moved to an archive subdirectory to keep the active mailbox small and fast to scan.
.chipset/state/mail/{agent-id}/archive/{filename}
archive/async function archiveOldMail(agentId: string): Promise<number> {
const mailDir = join(stateDir, 'mail', agentId);
const archiveDir = join(mailDir, 'archive');
const cutoff = Date.now() - 24 * 60 * 60 * 1000;
let archived = 0;
const files = (await readdir(mailDir)).filter(f => f.endsWith('.json'));
for (const file of files) {
const tsStr = file.split('-').slice(0, 3).join('-').replace(/T/, 'T');
const fileTime = new Date(tsStr).getTime();
if (fileTime < cutoff) {
await mkdir(archiveDir, { recursive: true });
await rename(join(mailDir, file), join(archiveDir, file));
archived++;
}
}
return archived;
}
Mail integrates with other communication channels in a defined flow:
work_assignment message with detailscompletion_report to mayorIf an agent stalls during step 4, the witness detects via nudge (nudge-sync) and escalates to the mayor via health_escalation mail.
| Condition | Behavior |
|---|---|
| Recipient mailbox doesn't exist | Created automatically on first send |
| Corrupt JSON in mailbox | Logged as warning, skipped during polling |
| Disk full during write | OS error propagated, temp file left for cleanup |
| Concurrent writes to same mailbox | Safe -- each message has a unique filename |
| Agent terminated with unread mail | Mail persists; available if agent restarts |
read field changes