agentleFS
Sign inStart free
tonydzitonydzi/second-brain-starter-kit/skills/inbox/SKILL.md

inbox

Skill6 starsChanged 2 months agoMITView on GitHub

Read this machine's cross-machine mailbox, the messages another computer's agent left here over a file-synced bus folder, and send messages back the same way. A session-start hook shows new mail automatically; this is the on-demand mid-session re-check. Triggers: "/inbox", "check inbox", "messages from the other machine".

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tailor, tasks and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ledqSkill

    tailor

    Tailor the resume to one job posting. Give it a URL, paste the posting (or refer to one pasted earlier in this chat), or point at a saved application folder; it resolves the JD and runs the tailor-pipeline workflow end to end.

    Also in 3 projects that use this

  • genomewalkerSkill

    tasks

    Browse and resume tasks, threads, and background jobs across sessions

    Also in 3 projects that use this

  • AnthropicSkill

    onboarding

    Generate an onboarding checklist and first-week plan for a new hire. Use when someone has a start date coming up, building the pre-start task list (accounts, equipment, buddy), scheduling Day 1 and Week 1, or setting 30/60/90-day goals for a new team member.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 6 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not put secrets in the mailbox if third parties could see the file (across the owner's own machines it is fine).

    line 39

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/inbox — mail between my own machines

The "Claude on one machine → Claude on another" channel, over the synced _machine-bus folder (Syncthing, ~10s). It removes the human courier. Copy-paste by hand is an EMERGENCY channel only.

Check what arrived for me (the main use)

python "$USERPROFILE/.claude/scripts/machine_bus.py" read

Shows only what is NEW for THIS machine (matched by hostname) and marks it read. Then report to the operator what came in and act on it if needed.

  • At session start the SessionStart hook already does this automatically — /inbox is for when the operator says "check the inbox" mid-session (e.g. something new arrived over sync).
  • Re-check without marking as read: ... read --peek.

Send a message to Claude on ANOTHER machine

  1. List the available mailboxes:
    python "$USERPROFILE/.claude/scripts/machine_bus.py" list
  2. Send:
    python "$USERPROFILE/.claude/scripts/machine_bus.py" send <RECIPIENT-HOSTNAME> "message text"
    The message must be self-contained (Claude on that machine has none of this session's context — include the goal, the steps, the paths, the values). It arrives in ~10s and surfaces for the recipient at session start or via /inbox.

Which channel when

  • The automatic mailbox (this skill + the hook) — the norm for everything cross-machine.
  • A human courier (copy-paste) — ONLY if sync is down, the machines are off the shared network, or it is extremely urgent.

Boundaries

  • Do not put secrets in the mailbox if third parties could see the file (across the owner's own machines it is fine).
  • "Fresher beats older": edit conflicts are resolved by the operator (Syncthing leaves *.sync-conflict-* files).
  • Delivery is not instant: Claude is not a daemon; the letter waits until a session opens on that machine (or a routine fires).
<!--kit-footer-->

Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.

Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).

Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_

Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free