← ClaudeAtlas

inboxlisted

Receiving side of /xm:toss — list, take, resolve, or drop cross-project bug reports that landed in this project's .xm/inbox/. Use when the user asks to check the inbox, "받은 편지함 봐줘", "what did other projects toss at us", or wants to start/finish/dismiss a specific handed-off item.
x-mesh/xm · ★ 0 · Code & Development · score 73
Install: claude install-skill x-mesh/xm
# x-inbox — Cross-Project Inbox ## Overview The receiving side of `/xm:toss`: `.xm/inbox/<id>.json` holds bug reports other registered projects tossed at this one. `/xm:inbox` lists them, marks one as being worked on (`take`), marks verified work complete (`resolve`), or dismisses one that isn't relevant (`drop`). Every read opportunistically archives resolved items older than 30 days locally (no network) — neither this nor anything else in this CLI ever discards an unresolved item. **The CLI itself makes zero network calls.** It cannot query mem-mesh pin state and cannot recreate an expired pin — that requires an MCP session, which only you (the skill, running inside Claude Code) have. Re-notifying an item whose pin already expired is therefore something YOU do, using `mcp__mem-mesh__pin_get` / `mcp__mem-mesh__pin_add` plus `xm inbox record --scope inbox` — see step 5 below. ## When to Use - "받은 편지함 봐줘" / "what's in the inbox" / "show what other projects tossed at us" - Starting work and want to check for cross-project reports before diving in - "이거 처리할게" / "I'll work on this one" → `take <id>` (marks in-progress, returns the full repro/fix body to act on) - "수정 끝났어" / "done" → `resolve <id>` after implementation and verification - "이건 아니다" / "not relevant, drop it" → `drop <id>` ## Do NOT Use When - You want to SEND a report to another project — that is `/xm:toss`. - You want to turn a taken item into a tracked x-build task — `take` only returns the item's conten