Agent skill

Intercom Upgrade Migration

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

Upgrade the intercom-client SDK across major versions and handle Intercom API version changes safely.

MITAuto-check passedTesting & QA

Install Intercom Upgrade Migration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-upgrade-migration -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace intercom-upgrade-migration --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-upgrade-migration .claude/skills/intercom-upgrade-migration && 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-upgrade-migration
GitHub stars
2.8k
Token cost
~1.6k tokens
SKILL.md length
612 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Upgrade the intercom-client SDK across major versions and handle Intercom API version changes safely.

  • Works in 4 steps: Check current versions → Migrate the code (v5 → v6) → Pin the API version if needed → …
  • A project is pinned to an old intercom-client release
  • SKILL.md covers Overview, Prerequisites, Authentication and Instructions, plus 5 more sections
  • Calls npm, npx and curl; reaches api.intercom.io; needs INTERCOM_ACCESS_TOKEN and DEV_TOKEN

What it does

Intercom Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade the intercom-client SDK across major versions and handle Intercom API version changes safely. Use when a project is pinned to an old intercom-client release, when the v5 CommonJS API must move to the v6 TypeScript rewrite, or when detecting breaking changes in a new Intercom release before shipping. Trigger with phrases like "upgrade intercom", "intercom migration", "intercom breaking changes", "update intercom SDK", "intercom API version".

Its SKILL.md is about 1.6k 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/migration-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Testing & QA. It works with Intercom, TypeScript and npm. 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

  • A project is pinned to an old intercom-client release
  • The v5 CommonJS API must move to the v6 TypeScript rewrite
  • Detecting breaking changes in a new Intercom release before shipping
  • With phrases like upgrade intercom

Example prompts

  • “upgrade intercom”
  • “intercom migration”
  • “intercom breaking changes”
  • “/intercom-upgrade-migration”

Requirements

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

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Check current versions
  2. Migrate the code (v5 → v6)
  3. Pin the API version if needed
  4. Run the type-checked upgrade on a branch

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. 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(git:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • npx
    • curl
    • git

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.intercom.io

    Also links to:

    • github.com
    • developers.intercom.com
    • npmjs.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
    • DEV_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 Upgrade Migration loads about 1.6k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 120 tokens; SKILL.md has 612 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 cfae287, republished under its MIT licence (© jeremylongshore). 612 words, ~1,637 tokens.

Download SKILL.mdSave it as .claude/skills/intercom-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
intercom-upgrade-migration
description
Upgrade the intercom-client SDK across major versions and handle Intercom API version changes safely. Use when a project is pinned to an old intercom-client release, when the v5 CommonJS API must move to the v6 TypeScript rewrite, or when detecting breaking changes in a new Intercom release before shipping. Trigger with phrases like "upgrade intercom", "intercom migration", "intercom breaking changes", "update intercom SDK", "intercom API version".
allowed-tools
Read, Write, Edit, Bash(npm:*), Bash(git:*)
compatibility
Designed for Claude Code
version
1.6.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
argument-hint
[current-version] [target-version]
tags
saas, support, messaging, intercom

Intercom Upgrade & Migration

Overview

Upgrade the intercom-client npm package and handle Intercom API version changes without breaking production traffic. The v6 TypeScript rewrite changed the API surface — most notably unifying users/leads into a single contacts API — so this skill drives a branch-based, type-checked upgrade that surfaces every breaking change through the compiler and test suite before merge.

Deep material lives in references/ so this file stays scannable:

  • Full v5 → v6 migration guide — every changed operation with before/after code, API-version pinning, the upgrade procedure, type-import changes, and the method cheat sheet.
  • Worked examples — three end-to-end runs from version detection through a committed upgrade branch.

Prerequisites

  • A project with intercom-client already installed (npm list intercom-client shows the current version).
  • Git available for branch-based upgrades and reviewable diffs.
  • A working test suite, ideally including an integration suite that can run against a dev Intercom workspace.
  • TypeScript (tsc) configured if migrating to v6+, since the compiler is the primary breaking-change detector.

Authentication

Intercom API calls authenticate with a workspace access token passed as a Bearer token. Read it from the INTERCOM_ACCESS_TOKEN environment variable — never hardcode it. Version-detection curls and the integration test step both consume this variable:

bash
export INTERCOM_ACCESS_TOKEN="<workspace-access-token>"   # from Intercom > Developer Hub

Use a separate dev-workspace token ($DEV_TOKEN) for the integration test step so the upgrade is validated without touching production data.

Instructions

Follow the workflow at a high level here; drill into the migration guide for the exact code diffs.

Step 1: Check current versions

Read (with the Read tool or npm list) the installed version, the latest published version, and the live API version to size the upgrade:

bash
npm list intercom-client                  # installed SDK version
npm view intercom-client version          # latest available
curl -s -D - -o /dev/null \
  -H "Authorization: Bearer $INTERCOM_ACCESS_TOKEN" \
  https://api.intercom.io/me 2>/dev/null | grep -i intercom-version

If the installed major is < 6 and the target is ≥ 6, expect the TypeScript-rewrite breaking changes.

Step 2: Migrate the code (v5 → v6)

For a major crossing, apply the breaking-change diffs with the Edit/Write tools: swap new Intercom.Client() for new IntercomClient(), move users/leads calls to the unified contacts API, rename positional params (id → contactId/conversationId), and update error handling to the IntercomError instance check. The full before/after set and a one-line-per-method cheat sheet are in the migration guide.

Step 3: Pin the API version if needed

The SDK sends a compatible Intercom-Version header automatically. Pin it explicitly only when using raw fetch requests or when a response shape must be frozen — see the API-version-pinning section of the migration guide.

Show full SKILL.md (233 more words)Show less
Step 4: Run the type-checked upgrade on a branch

Do the whole upgrade on a dedicated branch so TypeScript and the tests gate it:

bash
git checkout -b upgrade/intercom-client-v6
npm install intercom-client@latest
npx tsc --noEmit 2>&1 | grep "intercom"    # surfaces every breaking change
npm test

Fix each error the compiler reports, re-run until clean, then validate against a dev workspace and commit. The complete procedure is in the migration guide.

Output

Running this skill produces:

  • A dedicated upgrade branch (e.g. upgrade/intercom-client-v6) with intercom-client bumped in package.json / lockfile.
  • Source edits that migrate every v5 call site to the v6 API surface.
  • A clean npx tsc --noEmit run (no remaining intercom-client type errors) and a green npm test / integration run against a dev workspace.
  • A commit ready for PR, e.g. chore: upgrade intercom-client to v6.

Error Handling

IssueDetectionSolution
Cannot find module 'intercom-client'Import failsnpm install intercom-client
Property 'users' does not existTypeScript errorMigrate users/leads to contacts
Property 'id' does not existChanged param namesUse contactId, conversationId
Response shape changedRuntime errorsCheck API version headers, pin Intercom-Version
401 Unauthorizedcurl/test failsVerify INTERCOM_ACCESS_TOKEN is set and valid

Examples

Quick skeleton — detect, then migrate one call:

bash
npm list intercom-client        # e.g. 5.4.0
npm view intercom-client version # e.g. 6.4.0 → major upgrade
typescript
// v5  → migrate to →  v6
// await client.users.create({ email });
await client.contacts.create({ role: "user", email });

Three full end-to-end runs — version detection, a single-call migration, and a complete branch upgrade — are in references/examples.md.

Resources

Next Steps

After the upgrade branch is green, wire the version bump into CI so future regressions are caught automatically — see the intercom-ci-integration skill for the pipeline configuration.

© 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-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/examples.md
  • references/migration-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Intercom Upgrade Migration 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 Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Intercom Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.6kAutomated safety check: PassMIT
Interactive CLI Testing With tui-testslopus/happy24k—~603Automated safety check: PassMIT
Sage Wiki Integratexoai/sage-wiki623—~861Automated safety check: PassMIT
Bungalfrevn/apollo237—~2kAutomated safety check: NotesMIT
Trust Remote BuilderjohannesPettersson80/trust-platform222—~2kAutomated safety check: PassApache-2.0
Bunbastani-inc/atomic855—~2.8kAutomated safety check: PassCustom licence

Similar skills

  • Tests interactive CLI and TUI programs with Microsoft's tui-test, driving prompts, arrow keys and screen output in a real pseudo-terminal.

    24k GitHub stars~603 tokensUpdated today
    Testing & QAAuto-check passed
  • Sage Wiki Integrate

    xoai/sage-wiki

    Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports.

    623 GitHub stars~861 tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • Bun

    galfrevn/apollo

    A skill your agent uses when building, running, testing, or bundling JavaScript/TypeScript applications.

    237 GitHub stars~2k tokensUpdated 1 mo ago
    Testing & QAAuto-check: notes
  • Trust Remote Builder

    johannesPettersson80/trust-platform

    Runs truST builds and tests on the shared trust-builder machine.

    222 GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check passed
  • Bun

    bastani-inc/atomic

    A skill your agent uses when building, testing, and deploying JavaScript/TypeScript applications.

    855 GitHub stars~2.8k tokensUpdated today
    Testing & QAAuto-check passed
  • ClickUp CLI Testing

    krodak/clickup-cli

    Explains how to run and extend the clickup-cli tests: unit tests with a mocked client, e2e tests against a real ClickUp workspace, and the fixture data they rely on.

    123 GitHub stars~1.4k tokensUpdated 3 days ago
    Testing & QAAuto-check: notes

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
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Intercom Upgrade Migration

What does Intercom Upgrade Migration do?

Upgrade the intercom-client SDK across major versions and handle Intercom API version changes safely. Intercom Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade the intercom-client SDK across major versions and handle Intercom API version changes safely.

When should I use Intercom Upgrade Migration?

Intercom Upgrade Migration fits situations like: A project is pinned to an old intercom-client release; the v5 CommonJS API must move to the v6 TypeScript rewrite; detecting breaking changes in a new Intercom release before shipping; with phrases like upgrade intercom.

How do I install Intercom Upgrade Migration in Claude Code?

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

How do I install Intercom Upgrade Migration in Codex?

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

Can I use Intercom Upgrade Migration 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-upgrade-migration -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-upgrade-migration, .gemini/skills/intercom-upgrade-migration, .github/skills/intercom-upgrade-migration and .opencode/skills/intercom-upgrade-migration in your project.

What does Intercom Upgrade Migration need to run?

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

Does Intercom Upgrade Migration access the network?

SKILL.md names 4 domains. In commands or code: api.intercom.io; the agent is likely to contact it when it follows the instructions. As links in the text: github.com, developers.intercom.com and npmjs.com. This is read from the text; nothing was executed.

Is Intercom Upgrade Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Intercom Upgrade Migration use?

Intercom Upgrade Migration 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 Upgrade Migration use?

About 1.6k tokens (SKILL.md is roughly 6.5k 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.6k tokens, read only when the agent opens those files.

What are the alternatives to Intercom Upgrade Migration?

Skills that share tags, products or a category with Intercom Upgrade Migration: Interactive CLI Testing With tui-test (slopus/happy, 24k stars), Sage Wiki Integrate (xoai/sage-wiki, 623 stars), Bun (galfrevn/apollo, 237 stars) and Trust Remote Builder (johannesPettersson80/trust-platform, 222 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intercom Upgrade Migration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 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.