agentleFS
Sign inStart free
intercomintercom/claude-plugin-external/CLAUDE.md

claude-plugin-external

CLAUDE.md3 starsChanged 8 months agoMITView on GitHub

Intercom plugin for Claude Code and Google Antigravity — a skill-based integration (not compiled code). Skills are pure Markdown files the agent reads at runtime to interact with Intercom workspaces via a remote MCP server. Both platforms load the same skills/ directory. Three skills live under skills/, each in its own directory: Each skill directory contains:

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep version in both manifests in step, and bump it on every published change so installed clients pick up the update.

    line 19
  2. Very specific:

    Progressive disclosure: Keep SKILL.md focused on workflow logic.

    line 48
  3. Very specific:

    Test by running skills in Claude Code CLI (e.g., /intercom:install-messenger react)

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “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
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

What This Is

Intercom plugin for Claude Code and Google Antigravity — a skill-based integration (not compiled code). Skills are pure Markdown files the agent reads at runtime to interact with Intercom workspaces via a remote MCP server. Both platforms load the same skills/ directory.

Architecture

User → Claude Code CLI → Skill (SKILL.md) → MCP Server (https://mcp.intercom.com/mcp) → Intercom API
  • No build step, no dependencies, no tests. The plugin is entirely declarative.
  • .claude-plugin/plugin.json declares the intercom MCP server inline. Don't add a .mcp.json: Antigravity never loads it, and agy plugin validate --strict fails on it.
  • .claude-plugin/plugin.json is the plugin manifest for Claude Code's plugin registry.
  • .antigravity-plugin/plugin.json is the Antigravity Plugin Marketplace manifest. Antigravity reads MCP servers from mcp_config.json and the card logo from assets/logo.svg, both at the repo root.
  • Keep version in both manifests in step, and bump it on every published change so installed clients pick up the update.
  • The company is Fin and Intercom is its helpdesk product: use Fin for the publisher (author) and Intercom for the product and its features.
  • .claude/settings.local.json manages local permissions (currently allows WebFetch from raw.githubusercontent.com).

Skills

Three skills live under skills/, each in its own directory:

SkillTriggerKey Files
install-messengerExplicit: /intercom:install-messenger [framework]SKILL.md, references/framework-guides.md
intercom-analysisAuto-triggered by keywordsSKILL.md, references/mcp-tools.md
customer-360Explicit: /intercom:customer-360 [email or company name]SKILL.md

Skill File Structure

Each skill directory contains:

  • SKILL.md — Main skill file with YAML frontmatter (name, description, optional disable-model-invocation, argument-hint) followed by Markdown instructions Claude reads at runtime.
  • references/ — Supplementary docs loaded on demand for progressive disclosure (keeps SKILL.md concise).

Invocation Modes

  • Auto-triggered: No disable-model-invocation in frontmatter. Claude activates the skill when the user's intent matches the description field.
  • Explicit: disable-model-invocation: true in frontmatter. Only invoked via /intercom:<skill-name>.

Key Conventions

  • Security-first: install-messenger defaults to JWT-based identity verification (HS256). Insecure mode requires explicit user opt-in. Never default to insecure installation.
  • Progressive disclosure: Keep SKILL.md focused on workflow logic. Move API references, framework-specific code, and tool documentation into references/ subdirectories.
  • Read-only access: The MCP server only supports search and retrieval operations — no create, update, or delete.
  • Regional awareness: Intercom supports US, EU (Ireland), and Australia data residency. Currently US-only; EU/AU planned.

Development Workflow

  1. Edit SKILL.md files or reference documents
  2. Test by running skills in Claude Code CLI (e.g., /intercom:install-messenger react)
  3. For auto-triggered skills, test by typing natural language that matches the skill's description field
  4. Push to GitHub — the plugin registry picks up changes from the repository

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