agentleFS
Sign inStart free
sanztheosanztheo/claude-intercom/skill/SKILL.md

intercom

Skill2 starsChanged 8 months agoMITView on GitHub

Always active — coordinates with other Claude Code agents via intercom MCP. Automatically checks for messages, announces presence, and communicates to avoid conflicts. Triggers on ANY task start and periodically during work.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. alanalvestech/hitank★ 38same name
    2. Trac-Systems/intercom★ 21same name
    3. apideck-libraries/api-skills★ 4same name
    4. presmihaylov/skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before doing ANY work, run these two calls:

    line 14
  2. Distinctive:

    If other agents are active, consider sending a brief message about what you're about to work on.

    line 19
  3. Distinctive:

    When you receive a message:

    line 46
  4. Very specific:

    If it asks a question → mcp__intercom__reply(message_id, "your answer")

    line 47
  5. Very specific:

    If it's informational → mcp__intercom__ack(message_id) after reading

    line 48
  6. Distinctive:

    If it warns about a conflict → adjust your work accordingly, then reply

    line 49

“Common” is measured: kept by at least 6 in 10 of the 4 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

Intercom — Inter-Agent Communication

Purpose

Coordinate with other Claude Code instances working in parallel. Avoid file conflicts, duplicate work, and wasted effort by communicating proactively.

MANDATORY — On Every Task Start

Before doing ANY work, run these two calls:

  1. mcp__intercom__who() → discover who else is active on this project
  2. mcp__intercom__peek() → check if anyone sent you a message

If other agents are active, consider sending a brief message about what you're about to work on.

When to Communicate (Proactively)

Send a message (mcp__intercom__send) when:

SituationExample message
Starting work on a file"Je commence à modifier src/auth/middleware.ts"
About to create a PR or push"Je vais push sur feature/auth, heads up"
About to create a git worktree"Je crée un worktree pour feature/billing"
Finished a task that unblocks others"Auth middleware terminé et mergé, vous pouvez pull"
Found a bug or issue affecting others"Attention: la migration DB 042 est cassée, ne pas merger"
Need information from another agent"Qui gère le rate limiter ? J'ai besoin de contexte"

When to Check Messages

Call mcp__intercom__peek():

  • At task start (mandatory)
  • Before modifying shared files (package.json, schema, configs)
  • Before git operations (push, merge, rebase)
  • Periodically during long tasks (every ~10 tool calls)
  • Before claiming work is done

How to Reply

When you receive a message:

  • If it asks a question → mcp__intercom__reply(message_id, "your answer")
  • If it's informational → mcp__intercom__ack(message_id) after reading
  • If it warns about a conflict → adjust your work accordingly, then reply

Scope

  • who(scope="project") → agents on the same project (default)
  • who(scope="all") → all agents everywhere
  • send(to="all", ...) → broadcasts to same-project agents
  • send(to="x7k2", ...) → direct message to a specific agent (works cross-project)

Rules

  1. Always check messages before starting work — someone may have warned about a conflict
  2. Announce significant file changes — other agents can't see your edits in real-time
  3. Reply to questions — don't leave messages unacknowledged
  4. Be concise — messages are for coordination, not essays
  5. Don't spam — one announcement per major action, not per file edit

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