inbox

Read, send, and mark done file-based messages in a .claude/inbox directory.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill inbox-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inbox
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/inbox
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill inbox-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-dev teams need a lightweight, decentralized way to exchange notes and capture personal thoughts without interrupting workflow. The inbox provides a flat-file, git-friendly messaging surface that archives messages to recipient-specific files and surfaces unread items on demand.

Core Features & Use Cases

  • Flat-file inbox: .claude/inbox/<recipient>.md stores all messages per recipient with append-only history.
  • One recipient per file: Each teammate or self-note has a dedicated file; identity is derived from git config user.name.
  • Modes for read/write/self-write: Read pending messages, write new messages to teammates, or capture quick self-notes for future you.
  • Status tracking: Messages track unread vs. read; done state never deletes history.
  • Git-friendly delivery: No automatic commits; messages land in the working tree for the user to review and commit.

Quick Start

Start by running /inbox to view your messages, and send messages with /inbox to <name>: <message>.

Frequently Asked Questions about inbox

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

FAQPage Schema
How do I leave asynchronous notes for teammates in a git repository?

Asynchronous notes for teammates are written to a .claude/inbox directory. Each recipient gets a dedicated markdown file where messages are appended, allowing developers to read pending updates without interrupting their workflow.

What is the best way to capture personal scratchpad notes in a multi-developer codebase?

Personal scratchpad notes are captured using a self-write mode that appends messages to your own inbox file. Sender identity is derived automatically from your git-configured user.name to route the note correctly.

How does file-based team messaging work without a dedicated chat server?

File-based team messaging works by depositing flat files into the working tree of a git repository. Messages land as untracked or modified files for the user to review and commit manually, requiring no automatic commits or external server.

Can I use this inbox system if my git user.name is not configured?

This inbox system requires a configured git user.name to function. Sender identity and recipient routing are derived directly from this git config value, so the messaging modes cannot operate without it.

Are deleted messages removed from the .claude/inbox history?

Messages marked as done are never deleted from the .claude/inbox history. The system enforces an append-only design that tracks unread versus read status, preserving the full messaging archive within the file.

Does this asynchronous messaging tool automatically commit notes to the repository?

This asynchronous messaging tool does not automatically commit notes to the repository. Messages are delivered only to the working tree, leaving the user responsible for reviewing and committing the changes via git.