{"id":"42cf1a98-2248-4f95-ba7d-2beedf9ea304","entityType":"agent","slug":"clawhub-oomol-oo-intercom","name":"Intercom","canonicalUrl":"https://www.xpersona.co/agent/clawhub-oomol-oo-intercom","canonicalPath":"/agent/clawhub-oomol-oo-intercom","generatedAt":"2026-10-11T10:49:45.997Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:43:10.936Z","emptyReason":null},"description":"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-intercom","sourceUrl":"https://clawhub.ai/oomol/oo-intercom","homepage":"https://clawhub.ai/oomol/skills/oo-intercom","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/oomol/oo-intercom","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/oomol/skills/oo-intercom","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Intercom technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:43:10.936Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:43:10.936Z","emptyReason":null},"stars":null,"forks":null,"downloads":1109,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:43:10.870Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T08:43:10.936Z","lastCrawledAt":"2026-10-11T08:43:10.870Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T08:43:10.870Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-09-23T10:53:02.749Z","changelog":"- Provides OOMOL-connected Intercom access through the `oo` CLI without handling raw API tokens. - Supports reading workspace data such as admins, contacts, companies, conversations, tickets, articles, tags, events, counts, and job statuses. - Adds contact and ticket search using Intercom’s official search DSL. - Enables controlled write actions for creating/updating contacts and replying to or reopening conversations. - Marks destructive actions, such as closing conversations, with explicit safety guidance and approval requirements. Source: `oomol-lab/skills@e4c868f`","fileCount":3,"zipByteSize":3590},{"version":"1.0.5","createdAt":"2026-09-20T03:33:52.008Z","changelog":"- Operates Intercom through an OOMOL-connected account using the `oo` CLI, without exposing raw credentials. - Supports contact, company, admin, article, ticket, conversation, tag, event, count, and job-status lookups. - Adds list and search workflows for contacts, companies, conversations, articles, admins, tickets, tags, and events. - Provides write actions for creating/updating contacts and replying to or reopening conversations. - Marks destructive or state-changing actions clearly, including conversation close safeguards. Source: `oomol-lab/skills@792ad44`","fileCount":3,"zipByteSize":3603},{"version":"1.0.4","createdAt":"2026-09-15T03:56:31.855Z","changelog":"- Operates Intercom through an OOMOL-connected account using the `oo` CLI, with credentials injected server-side. - Provides read actions for admins, articles, companies, contacts, conversations, counts, jobs, tickets, events, and tags. - Supports cursor-based listing and official DSL search for contacts and tickets. - Includes write actions to create or update contacts and close, reopen, or reply to conversations. - Requires live schema inspection before action payloads and explicit confirmation before state-changing operations. Source: `oomol-lab/skills@75bac03`","fileCount":3,"zipByteSize":3569},{"version":"1.0.2","createdAt":"2026-07-12T16:07:41.584Z","changelog":"- Operates Intercom through an OOMOL-connected account using the `oo` CLI, with credentials injected server-side. - Supports reading workspace data including admins, contacts, companies, conversations, tickets, articles, tags, counts, events, and job status. - Adds search workflows for contacts and tickets using Intercom’s official search DSL. - Provides write actions for creating and updating contacts plus replying to, closing, and reopening conversations. - Emphasizes schema-first execution and confirmation before any action that changes Intercom state. Source: `oomol-lab/skills@d4aeb09`","fileCount":3,"zipByteSize":3604},{"version":"1.0.1","createdAt":"2026-06-09T10:18:19.005Z","changelog":"- Adds an OOMOL-backed Intercom skill for working with connected Intercom workspaces through the `oo` CLI. - Supports reading admins, contacts, conversations, current admin, and workspace metadata. - Provides contact creation, contact updates, conversation replies, closing, and reopening with write-action safety guidance. - Includes contact search via Intercom’s official search DSL and cursor-based listing for contacts and conversations. - Documents schema-first action execution plus first-time setup fallbacks for auth, connection, billing, and CLI issues. Source: `oomol-lab/skills@146ef20`","fileCount":3,"zipByteSize":3455},{"version":"1.0.0","createdAt":"2026-06-03T14:32:35.744Z","changelog":"- Adds an OOMOL-powered Intercom skill for working with an already connected Intercom workspace through the `oo` CLI. - Supports contact workflows including create, update, list, search, lookup by ID, and lookup by external ID. - Supports conversation workflows including list, fetch with conversation parts, reply as an admin, close, and reopen. - Provides admin and workspace access through current-admin lookup, admin lookup, and admin listing actions. - Documents safe execution patterns, live schema inspection before payload construction, and confirmation requirements for write actions.","fileCount":17,"zipByteSize":11129}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-intercom","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-intercom` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/oomol/oo-intercom before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T10:49:45.995Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:43:10.936Z","emptyReason":null},"readme":"Skill: Intercom\n\nOwner: oomol\n\nSummary: Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-09-23T10:53:02.749Z | user\n\n- Provides OOMOL-connected Intercom access through the `oo` CLI without handling raw API tokens.\n- Supports reading workspace data such as admins, contacts, companies, conversations, tickets, articles, tags, events, counts, and job statuses.\n- Adds contact and ticket search using Intercom’s official search DSL.\n- Enables controlled write actions for creating/updating contacts and replying to or reopening conversations.\n- Marks destructive actions, such as closing conversations, with explicit safety guidance and approval requirements.\n\nSource: `oomol-lab/skills@e4c868f`\n\nv1.0.5 | 2026-09-20T03:33:52.008Z | user\n\n- Operates Intercom through an OOMOL-connected account using the `oo` CLI, without exposing raw credentials.\n- Supports contact, company, admin, article, ticket, conversation, tag, event, count, and job-status lookups.\n- Adds list and search workflows for contacts, companies, conversations, articles, admins, tickets, tags, and events.\n- Provides write actions for creating/updating contacts and replying to or reopening conversations.\n- Marks destructive or state-changing actions clearly, including conversation close safeguards.\n\nSource: `oomol-lab/skills@792ad44`\n\nv1.0.4 | 2026-09-15T03:56:31.855Z | user\n\n- Operates Intercom through an OOMOL-connected account using the `oo` CLI, with credentials injected server-side.\n- Provides read actions for admins, articles, companies, contacts, conversations, counts, jobs, tickets, events, and tags.\n- Supports cursor-based listing and official DSL search for contacts and tickets.\n- Includes write actions to create or update contacts and close, reopen, or reply to conversations.\n- Requires live schema inspection before action payloads and explicit confirmation before state-changing operations.\n\nSource: `oomol-lab/skills@75bac03`\n\nv1.0.2 | 2026-07-12T16:07:41.584Z | user\n\n- Operates Intercom through an OOMOL-connected account using the `oo` CLI, with credentials injected server-side.\n- Supports reading workspace data including admins, contacts, companies, conversations, tickets, articles, tags, counts, events, and job status.\n- Adds search workflows for contacts and tickets using Intercom’s official search DSL.\n- Provides write actions for creating and updating contacts plus replying to, closing, and reopening conversations.\n- Emphasizes schema-first execution and confirmation before any action that changes Intercom state.\n\nSource: `oomol-lab/skills@d4aeb09`\n\nv1.0.1 | 2026-06-09T10:18:19.005Z | user\n\n- Adds an OOMOL-backed Intercom skill for working with connected Intercom workspaces through the `oo` CLI.\n- Supports reading admins, contacts, conversations, current admin, and workspace metadata.\n- Provides contact creation, contact updates, conversation replies, closing, and reopening with write-action safety guidance.\n- Includes contact search via Intercom’s official search DSL and cursor-based listing for contacts and conversations.\n- Documents schema-first action execution plus first-time setup fallbacks for auth, connection, billing, and CLI issues.\n\nSource: `oomol-lab/skills@146ef20`\n\nv1.0.0 | 2026-06-03T14:32:35.744Z | user\n\n- Adds an OOMOL-powered Intercom skill for working with an already connected Intercom workspace through the `oo` CLI.\n- Supports contact workflows including create, update, list, search, lookup by ID, and lookup by external ID.\n- Supports conversation workflows including list, fetch with conversation parts, reply as an admin, close, and reopen.\n- Provides admin and workspace access through current-admin lookup, admin lookup, and admin listing actions.\n- Documents safe execution patterns, live schema inspection before payload construction, and confirmation requirements for write actions.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 3590 bytes\n\nFiles: skill-card.md (2146b), SKILL.md (4970b), _meta.json (130b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: oo-intercom\ndescription: \"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Intercom\"\n  author: \"OOMOL\"\n  version: \"1.0.6\"\n  services: [\"intercom\"]\n  icon: \"https://static.oomol.com/logo/third-party/intercom.svg\"\n---\n\n# Intercom\n\nOperate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"intercom\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `close_conversation` — Close an Intercom conversation. [destructive]\n- `create_contact` — Create a new Intercom contact. [write]\n- `get_admin` — Get a single Intercom admin by identifier.\n- `get_article` — Get a single Intercom help center article by identifier.\n- `get_company` — Get a single Intercom company by company ID or name.\n- `get_contact` — Get a single Intercom contact by identifier.\n- `get_contact_by_external_id` — Get a single Intercom contact by external ID.\n- `get_conversation` — Get a single Intercom conversation with its conversation parts.\n- `get_counts` — Read Intercom workspace, conversation, or grouped counts.\n- `get_current_admin` — Get the currently authorized Intercom admin and workspace metadata.\n- `get_job_status` — Get the status of an Intercom asynchronous job.\n- `get_ticket` — Get a single Intercom ticket by internal ticket identifier.\n- `list_admins` — List Intercom admins for the current workspace.\n- `list_articles` — List Intercom help center articles.\n- `list_companies` — List Intercom companies with pagination.\n- `list_contacts` — List Intercom contacts with cursor-based pagination.\n- `list_conversations` — List Intercom conversations with cursor-based pagination.\n- `list_events` — List recent Intercom data events for one user or lead.\n- `list_tags` — List all Intercom tags for the current workspace.\n- `reopen_conversation` — Reopen an Intercom conversation. [write]\n- `reply_to_conversation` — Reply to an Intercom conversation as an admin. [write]\n- `search_contacts` — Search Intercom contacts with the official search DSL.\n- `search_tickets` — Search Intercom tickets with the official search DSL.\n- `update_contact` — Update an existing Intercom contact. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Intercom state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Intercom is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=intercom\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Intercom homepage: https://www.intercom.com\n\nFile v1.0.6:_meta.json\n\n{\n  \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n  \"slug\": \"oo-intercom\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1790160782749\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nThis skill helps an agent handle Intercom requests through OOMOL's oo CLI, including reading, creating, updating, and deleting Intercom data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nSupport, operations, and engineering teams use this skill to read and manage Intercom workspace data through OOMOL-connected Intercom actions, including contacts, conversations, tickets, articles, tags, events, counts, and admin records.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Setup instructions include piping remote installer scripts directly into a shell.\n\nMitigation: Prefer a verified package-manager or installer path, and review any remote script locally before execution.\n\nRisk: Write actions can change Intercom contacts or conversations.\n\nMitigation: Confirm the exact action, target, payload, and expected effect with the user before execution.\n\nRisk: The close conversation action is destructive.\n\nMitigation: Require explicit approval for the specific conversation target before running the action.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-intercom)\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n- [Intercom homepage](https://www.intercom.com)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, JSON, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Commands are intended for the OOMOL oo CLI and may return JSON responses from Intercom connector actions.]\n\n## Skill Version(s):\n\n1.0.6 (source: server evidence and frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 3 files, 3603 bytes\n\nFiles: skill-card.md (2114b), SKILL.md (4970b), _meta.json (130b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: oo-intercom\ndescription: \"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Intercom\"\n  author: \"OOMOL\"\n  version: \"1.0.5\"\n  services: [\"intercom\"]\n  icon: \"https://static.oomol.com/logo/third-party/Intercom.svg\"\n---\n\n# Intercom\n\nOperate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"intercom\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `close_conversation` — Close an Intercom conversation. [destructive]\n- `create_contact` — Create a new Intercom contact. [write]\n- `get_admin` — Get a single Intercom admin by identifier.\n- `get_article` — Get a single Intercom help center article by identifier.\n- `get_company` — Get a single Intercom company by company ID or name.\n- `get_contact` — Get a single Intercom contact by identifier.\n- `get_contact_by_external_id` — Get a single Intercom contact by external ID.\n- `get_conversation` — Get a single Intercom conversation with its conversation parts.\n- `get_counts` — Read Intercom workspace, conversation, or grouped counts.\n- `get_current_admin` — Get the currently authorized Intercom admin and workspace metadata.\n- `get_job_status` — Get the status of an Intercom asynchronous job.\n- `get_ticket` — Get a single Intercom ticket by internal ticket identifier.\n- `list_admins` — List Intercom admins for the current workspace.\n- `list_articles` — List Intercom help center articles.\n- `list_companies` — List Intercom companies with pagination.\n- `list_contacts` — List Intercom contacts with cursor-based pagination.\n- `list_conversations` — List Intercom conversations with cursor-based pagination.\n- `list_events` — List recent Intercom data events for one user or lead.\n- `list_tags` — List all Intercom tags for the current workspace.\n- `reopen_conversation` — Reopen an Intercom conversation. [write]\n- `reply_to_conversation` — Reply to an Intercom conversation as an admin. [write]\n- `search_contacts` — Search Intercom contacts with the official search DSL.\n- `search_tickets` — Search Intercom tickets with the official search DSL.\n- `update_contact` — Update an existing Intercom contact. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Intercom state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Intercom is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=intercom\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Intercom homepage: https://www.intercom.com\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n  \"slug\": \"oo-intercom\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1789875232008\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nIntercom helps agents read, create, update, and delete Intercom data through an OOMOL-connected account using the oo CLI.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nSupport, operations, and developer teams use this skill to inspect Intercom contacts, conversations, tickets, companies, articles, admins, tags, events, counts, and job status, and to perform confirmed contact and conversation updates.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can install the OOMOL CLI by piping a remote install script into a shell.\n\nMitigation: Review the OOMOL CLI installation path before use and prefer verified official documentation or a package manager.\n\nRisk: The skill can operate on sensitive customer-support data in Intercom.\n\nMitigation: Connect only an Intercom workspace where the agent is allowed to read contacts, conversations, tickets, and related records.\n\nRisk: Write and destructive actions can change Intercom records or close conversations.\n\nMitigation: Confirm the exact target, payload, and expected effect with the user before running write or destructive actions.\n\n## Reference(s):\n\n- [ClawHub Intercom skill page](https://clawhub.ai/oomol/skills/oo-intercom)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [Intercom](https://www.intercom.com)\n\n## Skill Output:\n\n**Output Type(s):** [text, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May produce oo CLI commands that return JSON responses from Intercom actions.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release metadata and skill metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 3569 bytes\n\nFiles: skill-card.md (2048b), SKILL.md (4954b), _meta.json (130b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: oo-intercom\ndescription: \"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, and updating data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Intercom\"\n  author: \"OOMOL\"\n  version: \"1.0.4\"\n  services: [\"intercom\"]\n  icon: \"https://static.oomol.com/logo/third-party/Intercom.svg\"\n---\n\n# Intercom\n\nOperate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"intercom\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `close_conversation` — Close an Intercom conversation. [write]\n- `create_contact` — Create a new Intercom contact. [write]\n- `get_admin` — Get a single Intercom admin by identifier.\n- `get_article` — Get a single Intercom help center article by identifier.\n- `get_company` — Get a single Intercom company by company ID or name.\n- `get_contact` — Get a single Intercom contact by identifier.\n- `get_contact_by_external_id` — Get a single Intercom contact by external ID.\n- `get_conversation` — Get a single Intercom conversation with its conversation parts.\n- `get_counts` — Read Intercom workspace, conversation, or grouped counts.\n- `get_current_admin` — Get the currently authorized Intercom admin and workspace metadata.\n- `get_job_status` — Get the status of an Intercom asynchronous job.\n- `get_ticket` — Get a single Intercom ticket by internal ticket identifier.\n- `list_admins` — List Intercom admins for the current workspace.\n- `list_articles` — List Intercom help center articles.\n- `list_companies` — List Intercom companies with pagination.\n- `list_contacts` — List Intercom contacts with cursor-based pagination.\n- `list_conversations` — List Intercom conversations with cursor-based pagination.\n- `list_events` — List recent Intercom data events for one user or lead.\n- `list_tags` — List all Intercom tags for the current workspace.\n- `reopen_conversation` — Reopen an Intercom conversation. [write]\n- `reply_to_conversation` — Reply to an Intercom conversation as an admin. [write]\n- `search_contacts` — Search Intercom contacts with the official search DSL.\n- `search_tickets` — Search Intercom tickets with the official search DSL.\n- `update_contact` — Update an existing Intercom contact. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Intercom state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Intercom is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=intercom\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Intercom homepage: https://www.intercom.com\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n  \"slug\": \"oo-intercom\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1789444591855\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:\n\nIntercom helps agents read, create, and update Intercom data through an OOMOL-connected account.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nSupport, operations, and developer teams use this skill to manage Intercom workspace data from an agent, including contacts, conversations, companies, articles, tickets, events, tags, and counts. It supports read workflows and user-confirmed write workflows such as creating or updating contacts and replying to conversations.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: First-time setup includes remote installer commands that execute downloaded code directly.\n\nMitigation: Review installer steps before use and prefer a verified, versioned release or package manager with checksum or signature validation.\n\nRisk: Intercom write actions can create or update contacts and close, reopen, or reply to conversations.\n\nMitigation: Require explicit approval for the exact payload and expected effect before running any write action.\n\n## Reference(s):\n\n- [Intercom homepage](https://www.intercom.com)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-intercom)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, API calls, JSON, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON command results]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses oo CLI connector actions; write actions require explicit user confirmation.]\n\n## Skill Version(s):\n\n1.0.4 (source: server release and skill metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.2: 3 files, 3604 bytes\n\nFiles: skill-card.md (2249b), SKILL.md (4954b), _meta.json (130b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: oo-intercom\ndescription: \"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, and updating data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Intercom\"\n  author: \"OOMOL\"\n  version: \"1.0.2\"\n  services: [\"intercom\"]\n  icon: \"https://static.oomol.com/logo/third-party/Intercom.svg\"\n---\n\n# Intercom\n\nOperate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"intercom\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `close_conversation` — Close an Intercom conversation. [write]\n- `create_contact` — Create a new Intercom contact. [write]\n- `get_admin` — Get a single Intercom admin by identifier.\n- `get_article` — Get a single Intercom help center article by identifier.\n- `get_company` — Get a single Intercom company by company ID or name.\n- `get_contact` — Get a single Intercom contact by identifier.\n- `get_contact_by_external_id` — Get a single Intercom contact by external ID.\n- `get_conversation` — Get a single Intercom conversation with its conversation parts.\n- `get_counts` — Read Intercom workspace, conversation, or grouped counts.\n- `get_current_admin` — Get the currently authorized Intercom admin and workspace metadata.\n- `get_job_status` — Get the status of an Intercom asynchronous job.\n- `get_ticket` — Get a single Intercom ticket by internal ticket identifier.\n- `list_admins` — List Intercom admins for the current workspace.\n- `list_articles` — List Intercom help center articles.\n- `list_companies` — List Intercom companies with pagination.\n- `list_contacts` — List Intercom contacts with cursor-based pagination.\n- `list_conversations` — List Intercom conversations with cursor-based pagination.\n- `list_events` — List recent Intercom data events for one user or lead.\n- `list_tags` — List all Intercom tags for the current workspace.\n- `reopen_conversation` — Reopen an Intercom conversation. [write]\n- `reply_to_conversation` — Reply to an Intercom conversation as an admin. [write]\n- `search_contacts` — Search Intercom contacts with the official search DSL.\n- `search_tickets` — Search Intercom tickets with the official search DSL.\n- `update_contact` — Update an existing Intercom contact. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Intercom state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Intercom is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=intercom\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Intercom homepage: https://www.intercom.com\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n  \"slug\": \"oo-intercom\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783872461584\n}\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nIntercom (intercom.com). Use this skill for ANY Intercom request: reading, creating, and updating data through an OOMOL-connected Intercom account. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[oomol](https://clawhub.ai/user/oomol) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nSupport, operations, and developer teams use this skill to let an agent inspect Intercom workspace data and perform confirmed contact or conversation updates through the oo CLI. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can update Intercom contacts and reply to, close, or reopen conversations. <br>\nMitigation: Confirm the exact target, payload, and expected effect with the user before running any write action. <br>\nRisk: The skill can read workspace data such as contacts, companies, conversations, tickets, events, tags, and admin records. <br>\nMitigation: Install only for Intercom workspaces where agent access to this data is intended. <br>\nRisk: Connector schemas can change over time. <br>\nMitigation: Fetch the live action schema before constructing each payload. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Intercom skill page](https://clawhub.ai/oomol/skills/oo-intercom) <br>\n- [Intercom homepage](https://www.intercom.com) <br>\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli) <br>\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON payload examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses live connector schemas before building action payloads; write actions require user confirmation.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release metadata and SKILL.md frontmatter) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 3 files, 3455 bytes\n\nFiles: skill-card.md (2485b), SKILL.md (4235b), _meta.json (130b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: oo-intercom\ndescription: \"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, and updating data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Intercom\"\n  author: \"OOMOL\"\n  version: \"1.0.1\"\n  services: [\"intercom\"]\n  icon: \"https://static.oomol.com/logo/third-party/Intercom.svg\"\n---\n\n# Intercom\n\nOperate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"intercom\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `close_conversation` — Close an Intercom conversation. [write]\n- `create_contact` — Create a new Intercom contact. [write]\n- `get_admin` — Get a single Intercom admin by identifier.\n- `get_contact` — Get a single Intercom contact by identifier.\n- `get_contact_by_external_id` — Get a single Intercom contact by external ID.\n- `get_conversation` — Get a single Intercom conversation with its conversation parts.\n- `get_current_admin` — Get the currently authorized Intercom admin and workspace metadata.\n- `list_admins` — List Intercom admins for the current workspace.\n- `list_contacts` — List Intercom contacts with cursor-based pagination.\n- `list_conversations` — List Intercom conversations with cursor-based pagination.\n- `reopen_conversation` — Reopen an Intercom conversation. [write]\n- `reply_to_conversation` — Reply to an Intercom conversation as an admin. [write]\n- `search_contacts` — Search Intercom contacts with the official search DSL.\n- `update_contact` — Update an existing Intercom contact. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Intercom state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Intercom is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=intercom\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Intercom homepage: https://www.intercom.com\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n  \"slug\": \"oo-intercom\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1781000299005\n}\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nUse this skill for Intercom requests involving reading, creating, and updating data. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[oomol](https://clawhub.ai/user/oomol) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, support operators, and developers use this skill to inspect Intercom admins, contacts, conversations, and workspace metadata through an OOMOL-connected Intercom workspace. It also helps create or update contacts and manage conversation replies, closing, and reopening when the user confirms the intended write action. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Write actions can create or update contacts and change conversation state in Intercom. <br>\nMitigation: Confirm the exact target, payload, and intended effect with the user before running create, update, reply, close, or reopen actions. <br>\nRisk: The skill depends on OOMOL's oo CLI and an OOMOL-connected Intercom workspace. <br>\nMitigation: Install only when the operator trusts the OOMOL CLI and is comfortable connecting the workspace through OOMOL. <br>\nRisk: Action input fields may change with the live Intercom connector contract. <br>\nMitigation: Fetch the action schema with `oo connector schema` before constructing or running each payload. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/oomol/oo-intercom) <br>\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol) <br>\n- [Intercom homepage](https://www.intercom.com) <br>\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli) <br>\n- [OOMOL CLI install guide](https://cli.oomol.com/install-guide.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON payload guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses live connector schemas before action execution and returns Intercom connector responses as JSON when commands are run.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release metadata and skill frontmatter) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 17 files, 11129 bytes\n\nFiles: actions/close_conversation.md (806b), actions/create_contact.md (780b), actions/get_admin.md (638b), actions/get_contact_by_external_id.md (728b), actions/get_contact.md (652b), actions/get_conversation.md (701b), actions/get_current_admin.md (703b), actions/list_admins.md (653b), actions/list_contacts.md (670b), actions/list_conversations.md (705b), actions/reopen_conversation.md (812b), actions/reply_to_conversation.md (836b), actions/search_contacts.md (682b), actions/update_contact.md (786b), skill-card.md (2601b), SKILL.md (4688b), _meta.json (130b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: oo-intercom\ndescription: \"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, and updating data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Intercom\"\n  author: \"OOMOL\"\n  version: \"1.0.0\"\n  service: \"intercom\"\n  categories: \"Communication, Productivity\"\n  homepage: \"https://www.intercom.com\"\n  icon: \"https://static.oomol.com/logo/third-party/Intercom.svg\"\n---\n\n# Intercom\n\nOperate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Communication, Productivity. Exposes 14 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"intercom\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`close_conversation`](actions/close_conversation.md) — Close an Intercom conversation.\n- [`create_contact`](actions/create_contact.md) — Create a new Intercom contact.\n- [`get_admin`](actions/get_admin.md) — Get a single Intercom admin by identifier.\n- [`get_contact`](actions/get_contact.md) — Get a single Intercom contact by identifier.\n- [`get_contact_by_external_id`](actions/get_contact_by_external_id.md) — Get a single Intercom contact by external ID.\n- [`get_conversation`](actions/get_conversation.md) — Get a single Intercom conversation with its conversation parts.\n- [`get_current_admin`](actions/get_current_admin.md) — Get the currently authorized Intercom admin and workspace metadata.\n- [`list_admins`](actions/list_admins.md) — List Intercom admins for the current workspace.\n- [`list_contacts`](actions/list_contacts.md) — List Intercom contacts with cursor-based pagination.\n- [`list_conversations`](actions/list_conversations.md) — List Intercom conversations with cursor-based pagination.\n- [`reopen_conversation`](actions/reopen_conversation.md) — Reopen an Intercom conversation.\n- [`reply_to_conversation`](actions/reply_to_conversation.md) — Reply to an Intercom conversation as an admin.\n- [`search_contacts`](actions/search_contacts.md) — Search Intercom contacts with the official search DSL.\n- [`update_contact`](actions/update_contact.md) — Update an existing Intercom contact.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Intercom state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Intercom is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=intercom\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Intercom homepage: https://www.intercom.com\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n  \"slug\": \"oo-intercom\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1780497155744\n}\n\nFile v1.0.0:actions/close_conversation.md\n\n# Intercom · `close_conversation`\n\nClose an Intercom conversation.\n\n- **Service**: `intercom`\n- **Action**: `close_conversation`\n- **Action id**: `intercom.close_conversation`\n- **Required scopes**: intercom.conversations.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"close_conversation\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"close_conversation\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Intercom state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/create_contact.md\n\n# Intercom · `create_contact`\n\nCreate a new Intercom contact.\n\n- **Service**: `intercom`\n- **Action**: `create_contact`\n- **Action id**: `intercom.create_contact`\n- **Required scopes**: intercom.contacts.write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"create_contact\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"create_contact\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Intercom state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/get_admin.md\n\n# Intercom · `get_admin`\n\nGet a single Intercom admin by identifier.\n\n- **Service**: `intercom`\n- **Action**: `get_admin`\n- **Action id**: `intercom.get_admin`\n- **Required scopes**: intercom.admins.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"get_admin\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"get_admin\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_contact_by_external_id.md\n\n# Intercom · `get_contact_by_external_id`\n\nGet a single Intercom contact by external ID.\n\n- **Service**: `intercom`\n- **Action**: `get_contact_by_external_id`\n- **Action id**: `intercom.get_contact_by_external_id`\n- **Required scopes**: intercom.contacts.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"get_contact_by_external_id\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"get_contact_by_external_id\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_contact.md\n\n# Intercom · `get_contact`\n\nGet a single Intercom contact by identifier.\n\n- **Service**: `intercom`\n- **Action**: `get_contact`\n- **Action id**: `intercom.get_contact`\n- **Required scopes**: intercom.contacts.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"get_contact\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"get_contact\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_conversation.md\n\n# Intercom · `get_conversation`\n\nGet a single Intercom conversation with its conversation parts.\n\n- **Service**: `intercom`\n- **Action**: `get_conversation`\n- **Action id**: `intercom.get_conversation`\n- **Required scopes**: intercom.conversations.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"get_conversation\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"get_conversation\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_current_admin.md\n\n# Intercom · `get_current_admin`\n\nGet the currently authorized Intercom admin and workspace metadata.\n\n- **Service**: `intercom`\n- **Action**: `get_current_admin`\n- **Action id**: `intercom.get_current_admin`\n- **Required scopes**: intercom.admins.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"get_current_admin\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"get_current_admin\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_admins.md\n\n# Intercom · `list_admins`\n\nList Intercom admins for the current workspace.\n\n- **Service**: `intercom`\n- **Action**: `list_admins`\n- **Action id**: `intercom.list_admins`\n- **Required scopes**: intercom.admins.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"list_admins\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"list_admins\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_contacts.md\n\n# Intercom · `list_contacts`\n\nList Intercom contacts with cursor-based pagination.\n\n- **Service**: `intercom`\n- **Action**: `list_contacts`\n- **Action id**: `intercom.list_contacts`\n- **Required scopes**: intercom.contacts.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"list_contacts\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"list_contacts\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_conversations.md\n\n# Intercom · `list_conversations`\n\nList Intercom conversations with cursor-based pagination.\n\n- **Service**: `intercom`\n- **Action**: `list_conversations`\n- **Action id**: `intercom.list_conversations`\n- **Required scopes**: intercom.conversations.read\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"intercom\" --action \"list_conversations\"\n```\n\n## Run\n\n```bash\noo connector run \"intercom\" --action \"list_conversations\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.","readmeExcerpt":"Skill: Intercom Owner: oomol Summary: Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly. Tags: latest:1.0.6 Version history: v1.0.6 | 2026-09-23T10:53:02.749Z | user - Provides OOMOL-connected Intercom access through the oo CLI without handling raw API tokens. - Suppor","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"oo connector schema \"intercom\" --action \"<action_name>\""},{"language":"bash","snippet":"oo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux"},{"language":"powershell","snippet":"irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell"},{"language":"bash","snippet":"oo auth login"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: oo-intercom\ndescription: \"Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Intercom\"\n  author: \"OOMOL\"\n  version: \"1.0.6\"\n  services: [\"intercom\"]\n  icon: \"https://static.oomol.com/logo/third-party/intercom.svg\"\n---\n\n# Intercom\n\nOperate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"intercom\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"intercom\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `close_conversation` — Close an Intercom conversation. [destructive]\n- `create_contact` — Create a new Intercom contact. [write]\n- `get_admin` — Get a single Intercom admin by identifier.\n- `get_article` — Get a single Intercom help center article by identifier.\n- `get_company` — Get a single Intercom company by company ID or name.\n- `get_contact` — Get a single Intercom contact by identifier.\n- `get_contact_by_external_id` — Get a single Intercom contact by external ID.\n- `get_conversation` — Get a single Intercom conversation with its conversation parts.\n- `get_counts` — Read Intercom workspace, conversation, or grouped counts.\n- `get_current_admin` — Get the currently authorized Intercom admin and workspace metadata.\n- `get_job_status` — Get the status of an Intercom asynchronous job.\n- `get_ticket` — Get a single Intercom ticket by internal ticket identifier.\n- `list_admins` — List Intercom admins for the current workspace.\n- `list_articles` — List Intercom help center articles.\n- `list_companies` — List Intercom companies with pagination.\n- `list_contacts` — List Intercom contacts with cursor-based pagination.\n- `list_conversations` — List Intercom conversations with cu"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n  \"slug\": \"oo-intercom\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1790160782749\n}"},{"path":"skill-card.md","content":"## Description:\n\nThis skill helps an agent handle Intercom requests through OOMOL's oo CLI, including reading, creating, updating, and deleting Intercom data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nSupport, operations, and engineering teams use this skill to read and manage Intercom workspace data through OOMOL-connected Intercom actions, including contacts, conversations, tickets, articles, tags, events, counts, and admin records.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Setup instructions include piping remote installer scripts directly into a shell.\n\nMitigation: Prefer a verified package-manager or installer path, and review any remote script locally before execution.\n\nRisk: Write actions can change Intercom contacts or conversations.\n\nMitigation: Confirm the exact action, target, payload, and expected effect with the user before execution.\n\nRisk: The close conversation action is destructive.\n\nMitigation: Require explicit approval for the specific conversation target before running the action.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-intercom)\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n- [Intercom homepage](https://www.intercom.com)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, JSON, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Commands are intended for the OOMOL oo CLI and may return JSON responses from Intercom connector actions.]\n\n## Skill Version(s):\n\n1.0.6 (source: server evidence and frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1488,"uniquenessScore":39,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T08:43:10.936Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T08:43:10.936Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T10:49:45.997Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}