Intercom Data Handling

What it does

When your agent uses it

• Handling sensitive Intercom contact data
• Fulfilling a data subject access
• Deletion request
• Redacting PII in logs

Example prompts

• “intercom data”
• “intercom PII”
• “intercom GDPR”
• “/intercom-data-handling”

Requirements

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

Workflow steps

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

1. 1DSAR export — exportContactData(contactId) gathers the contact profile,
2. 2Right to deletion (Article 17) — deleteContactData(contactId) exports for
3. 3Bulk data export — bulkExportMessages(start, end) kicks off the async
4. 4PII redaction in logs — redactIntercomData(data) masks a fixed
5. 5Retention enforcement — enforceRetention() sweeps cached records past

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. 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

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

  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):

  • developers.intercom.com
  • intercom.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 Data Handling loads about 1.6k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 121 tokens; SKILL.md has 568 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~121

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.9k

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

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 80f86df, republished under its MIT licence (© jeremylongshore). 568 words, ~1,592 tokens.

name

intercom-data-handling

description

Implement Intercom data handling for GDPR, contact export, data retention, and PII. Use when handling sensitive Intercom contact data, fulfilling a data subject access or deletion request, redacting PII in logs, or setting retention policy for cached Intercom records. Trigger with phrases like "intercom data", "intercom PII", "intercom GDPR", "intercom data retention", "intercom privacy", "intercom CCPA", "intercom data export", "intercom delete contact".

allowed-tools

Read, Write, Edit

compatibility

Designed for Claude Code

version

1.6.0

license

MIT

author

Jeremy Longshore <jeremy@intentsolutions.io>

tags

saas, support, messaging, intercom

import { IntercomClient } from "intercom-client";

const client = new IntercomClient({
  token: process.env.INTERCOM_ACCESS_TOKEN!,
});
// Raw REST calls use: Authorization: `Bearer ${process.env.INTERCOM_ACCESS_TOKEN}`

const contact = await client.contacts.find({ contactId });
const convList = await client.conversations.search({
  query: { field: "contact_ids", operator: "=", value: contactId },
});
// ...gather tags, segments, events → return one bundle

// A user asks for all their data — export the whole bundle to JSON.
const bundle = await exportContactData("5f3c9b2e8a1d4e0012ab34cd");
await fs.writeFile(`dsar/${bundle.contact.id}.json`, JSON.stringify(bundle, null, 2));

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

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

Open the folder on GitHubat commit 80f86df