agentsclimarketplace

M AI l

Skill playtosor/m_AI_l

Asynchronous messaging system for multi-thread Claude projects. Enables Claude threads to communicate via Markdown mailboxes — no server, no database, no code required. Triggers: MAIL!, SEND!, RENEW!, PRUNE!, INVITE WRITE, INVITE READ.From its SKILL.md

Install
npx -y skills add playtosor/m_AI_l

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 278 tokens by cl100k_base, as published. Nobody here has run it

m_AI_l — Asynchronous messaging for Claude projects

Keep your Claude threads in sync — built entirely in Markdown.

Each Claude thread gets a mailbox. Threads deposit messages, read them with MAIL!, and archive silently. When a thread saturates, it hands off cleanly to its successor. Nothing gets dropped.

No server. No database. No code. Just Markdown files.


For humans — getting started

→ Full setup guide: setup.md → Documentation & install: github.com/playtosor/m_AI_l

Requirements: Claude Desktop + Node.js (for filesystem MCP access). Run ARO — the one-shot setup agent — and you're ready in five minutes.


For agents — quick reference

Install by reading skills/commun.md from your m_AI_l folder at session start.

Key skills

  • mailbox_read.md — read, interpret, archive (trigger: MAIL!)
  • mailbox_write.md — deposit messages (trigger: SEND!)
  • renew.md — thread replacement with handover (trigger: RENEW!)
  • onboarding.md — integrate a new thread into the team
  • aro.md — one-shot setup agent for new installations
<!-- END -->

What ships with it: 21 files

77.8 KB alongside SKILL.md, 1 of them executable

Gives 0 of the 12 instructions most docs writing skills give in 278 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07

  • Announce the skill at startin 54 of 1637, across 26 files
  • Convert legacy doc files before editingin 45 of 1637, across 7 files
  • Predict questions readers might askin 42 of 1637, across 4 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test the document with a fresh context-less instancein 42 of 1637, across 3 files
  • Include exact file paths in every taskin 42 of 1637, across 15 files
  • Ask interview questions one at a timein 42 of 1637, across 27 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 2 files

Said here and by no other author read

  • read the mailbox at session start
  • deposit messages for other threads
  • archive messages silently after reading
  • hand off cleanly on thread saturation
  • read the setup guide for installation
  • run the setup agent for new installations

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.