Agent skill

Intercom Local Dev Loop

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Configure Intercom local development with testing, mocking, and hot reload.

MITAuto-check: notesDevelopment

Install Intercom Local Dev Loop

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-local-dev-loop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace intercom-local-dev-loop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/intercom-local-dev-loop .claude/skills/intercom-local-dev-loop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
intercom-local-dev-loop
GitHub stars
2.8k
Token cost
~1.5k tokens
SKILL.md length
530 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure Intercom local development with testing, mocking, and hot reload.

  • Works in 7 steps: Scaffold the project structure — an… → Configure environments — commit… → Write an environment-aware client… → …
  • Setting up a development environment
  • SKILL.md covers Overview, Prerequisites, Authentication and Instructions, plus 4 more sections
  • Calls npm and ngrok; needs INTERCOM_ACCESS_TOKEN

What it does

Intercom Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Intercom local development with testing, mocking, and hot reload. Use when setting up a development environment, writing tests against the Intercom API, or establishing a fast iteration cycle against a dev workspace. Trigger with phrases like "intercom dev setup", "intercom local development", "intercom dev environment", "develop with intercom", "test intercom locally".

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/examples.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code

It sits in Development. It works with Intercom and Git. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Setting up a development environment
  • Writing tests against the Intercom API
  • Establishing a fast iteration cycle against a dev workspace
  • With phrases like intercom dev setup

Example prompts

  • “intercom dev setup”
  • “intercom local development”
  • “intercom dev environment”
  • “/intercom-local-dev-loop”

Requirements

  • Node.js
  • A credential in INTERCOM_ACCESS_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Bash(npx:*)

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Scaffold the project structure — an src/intercom/ module (singleton
  2. Configure environments — commit .env.example as the template and keep
  3. Write an environment-aware client singleton that reads the token, throws a
  4. Build a mock client factory (tests/mocks/intercom.ts) covering contacts,
  5. Write mocked unit tests against the factory, asserting call arguments and
  6. Tunnel webhooks with ngrok — run the local server, ngrok http 3000, and
  7. Wire package scripts (dev, test, test:watch, test:integration,

What it can do on your machine

Read from SKILL.md and the folder at commit 23ea8d4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(npm:*)
    • Bash(npx:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • ngrok

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • npmjs.com
    • vitest.dev
    • ngrok.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • INTERCOM_ACCESS_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Intercom Local Dev Loop loads about 1.5k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 530 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:40
    _ACCESS_TOKEN` (loaded from git-ignored `.env.development`);
  • NoteMentions a .env fileSKILL.md:42
    kspace is only a matter of swapping the `.env.development`
  • NoteMentions a .env fileSKILL.md:53
    `.env.development` and `.env.test` git-ignored). Use **Write** to create each
  • NoteMentions a .env fileSKILL.md:57
    real tokens in the git-ignored `.env.development`. See
  • NoteMentions a .env fileSKILL.md:75
    CESS_TOKEN not set. Copy .env.example to .env.development"
  • NoteMentions a .env fileSKILL.md:111
    `.env.development` / `.env.test`.
  • NoteMentions a .env fileSKILL.md:122
    INTERCOM_ACCESS_TOKEN not set` | Missing .env file | Copy `.env.example` to `.env.development` |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 23ea8d4, republished under its MIT licence (© jeremylongshore). 530 words, ~1,544 tokens.

Download SKILL.mdSave it as .claude/skills/intercom-local-dev-loop/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
intercom-local-dev-loop
description
Configure Intercom local development with testing, mocking, and hot reload. Use when setting up a development environment, writing tests against the Intercom API, or establishing a fast iteration cycle against a dev workspace. Trigger with phrases like "intercom dev setup", "intercom local development", "intercom dev environment", "develop with intercom", "test intercom locally".
allowed-tools
Read, Write, Edit, Bash(npm:*), Bash(npx:*)
compatibility
Designed for Claude Code
version
1.6.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, support, messaging, intercom

Intercom Local Dev Loop

Overview

Set up a fast local development workflow for Intercom integrations with proper test isolation, mocking strategies, and webhook tunneling. The loop has two lanes: a mocked unit lane that runs offline with no token, and an integration lane that talks to a real dev workspace and is skipped automatically when no token is present.

Prerequisites

  • Completed intercom-install-auth setup
  • Node.js 18+ with npm/pnpm
  • A test/development Intercom workspace (separate from production)

Authentication

The client authenticates with a single Intercom bearer access token, issued per workspace by the intercom-install-auth step. Read it from process.env.INTERCOM_ACCESS_TOKEN (loaded from git-ignored .env.development); never hardcode it. The mocked unit lane needs no token at all — pointing the loop at a different dev workspace is only a matter of swapping the .env.development value.

Instructions

Work through these steps to stand up the loop. The full, copy-paste-ready code for every step lives in the implementation walkthrough.

  1. Scaffold the project structure — an src/intercom/ module (singleton client.ts, plus contacts.ts / conversations.ts / types.ts), a tests/ tree with a mocks/ factory, and three env files (.env.example committed, .env.development and .env.test git-ignored). Use Write to create each file. See implementation.md.

  2. Configure environments — commit .env.example as the template and keep real tokens in the git-ignored .env.development. See implementation.md.

  3. Write an environment-aware client singleton that reads the token, throws a clear error when it is missing, and exposes a resetClient() for tests. The skeleton:

    typescript
    // src/intercom/client.ts
    import { IntercomClient } from "intercom-client";
    
    let instance: IntercomClient | null = null;
    
    export function getClient(): IntercomClient {
      if (!instance) {
        const token = process.env.INTERCOM_ACCESS_TOKEN;
        if (!token) {
          throw new Error(
            "INTERCOM_ACCESS_TOKEN not set. Copy .env.example to .env.development"
          );
        }
        instance = new IntercomClient({ token });
      }
      return instance;
    }
    
    export function resetClient(): void {
      instance = null;
    }
  4. Build a mock client factory (tests/mocks/intercom.ts) covering contacts, conversations, messages, admins, and tags with vi.fn() resolved values, so the unit lane never touches the network. Full factory in implementation.md.

  5. Write mocked unit tests against the factory, asserting call arguments and returned shapes. See implementation.md.

  6. Tunnel webhooks with ngrok — run the local server, ngrok http 3000, and register the HTTPS URL in Intercom Developer Hub. Use Bash(npx:*) for ngrok. See implementation.md.

  7. Wire package scripts (dev, test, test:watch, test:integration, typecheck) — use Edit to add them to package.json, then drive the loop with Bash(npm:*). See implementation.md.

Show full SKILL.md (199 more words)Show less

Output

Following this skill produces a working local Intercom development loop:

  • A scaffolded src/intercom/ client module and tests/ tree with a reusable mock factory.
  • Three environment files — a committed .env.example template plus git-ignored .env.development / .env.test.
  • An offline mocked unit test lane (npm run test / test:watch) that runs with no token and no network.
  • A token-gated integration lane (npm run test:integration) that is skipped automatically when INTERCOM_ACCESS_TOKEN is absent.
  • An ngrok webhook tunnel exposing the local server to Intercom's Developer Hub.

Error Handling

ErrorCauseSolution
INTERCOM_ACCESS_TOKEN not setMissing .env fileCopy .env.example to .env.development
Port 3000 in useAnother processlsof -i :3000 and kill, or change port
ngrok tunnel expiredFree tier 2h limitRestart ngrok or use paid plan
Mock type mismatchSDK updatedRegenerate mocks from SDK types
rate_limit_exceeded in devDev workspace limitsAdd delays between integration tests

Examples

A minimal mocked unit test (from implementation.md):

typescript
it("should create a user contact", async () => {
  const contact = await mockClient.contacts.create({
    role: "user",
    externalId: "user-123",
    email: "test@example.com",
  });

  expect(contact.id).toBe("mock-contact-id");
  expect(mockClient.contacts.create).toHaveBeenCalledOnce();
});

For the token-gated integration test pattern (describe.skipIf, live create + cleanup) and the commands that drive each lane, see the examples reference.

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/intercom-local-dev-loop of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/examples.md
  • references/implementation.md

Open the folder on GitHubat commit 23ea8d4

Compare with similar skills

Intercom Local Dev Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Intercom Local Dev Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Intercom Local Dev Loop this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.5kAutomated safety check: NotesMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything86k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    86k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    86k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Analyzing Text With NLP

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to perform natural language processing and text analysis using the nlp-text-analyzer plugin.

    2.8k GitHub starsUsed in 1 repo~819 tokens
    Auto-check passed
  • Building Neural Networks

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill allows AI assistant to construct and configure neural network architectures using the neural-network-builder plugin.

    2.8k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Detecting Data Anomalies

    jeremylongshore/tons-of-skills-marketplace

    Process identify anomalies and outliers in datasets using machine learning algorithms.

    2.8k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Explaining Machine Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill enables AI assistant to provide interpretability and explainability for machine learning models.

    2.8k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Optimizing Prompts

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill optimizes prompts for large language models (llms) to reduce token usage, lower costs, and improve performance.

    2.8k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

Works with

Categories

Questions about Intercom Local Dev Loop

What does Intercom Local Dev Loop do?

Configure Intercom local development with testing, mocking, and hot reload. Intercom Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Intercom local development with testing, mocking, and hot reload.

When should I use Intercom Local Dev Loop?

Intercom Local Dev Loop fits situations like: setting up a development environment; writing tests against the Intercom API; establishing a fast iteration cycle against a dev workspace; with phrases like intercom dev setup.

How do I install Intercom Local Dev Loop in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-local-dev-loop -a claude-code`. Or copy the skill folder (skills/.curated/intercom-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/intercom-local-dev-loop in your project. Claude Code loads it when a task matches its description.

How do I install Intercom Local Dev Loop in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-local-dev-loop -a codex`. Or copy the skill folder (skills/.curated/intercom-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/intercom-local-dev-loop in your project. Codex loads it when a task matches its description.

Can I use Intercom Local Dev Loop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-local-dev-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/intercom-local-dev-loop, .gemini/skills/intercom-local-dev-loop, .github/skills/intercom-local-dev-loop and .opencode/skills/intercom-local-dev-loop in your project.

What does Intercom Local Dev Loop need to run?

Going by SKILL.md and its folder, Intercom Local Dev Loop needs the command-line tools its instructions call (npm and ngrok) and credentials named INTERCOM_ACCESS_TOKEN. Our summary lists: Node.js; A credential in INTERCOM_ACCESS_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*), Bash(npx:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Intercom Local Dev Loop access the network?

SKILL.md names 3 domains. As links in the text: npmjs.com, vitest.dev and ngrok.com. This is read from the text; nothing was executed.

Is Intercom Local Dev Loop safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Intercom Local Dev Loop use?

Intercom Local Dev Loop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Intercom Local Dev Loop use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Intercom Local Dev Loop?

Skills that share tags, products or a category with Intercom Local Dev Loop: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intercom Local Dev Loop?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,821 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 8, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.