[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSM25DMKT6VSBX0BGK5PZG":3,"skill-same:01M6FSM25DMKT6VSBX0BGK5PZG":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6FSM25DMKT6VSBX0BGK5PZG","intercom-automation",null,"Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fintercom-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"automation","intercom automation","intercom","MCP","tasks","search","Tools","first","automate","community","composio","via","segments","contacts","conversations","2026-11-10 10:12:30",false,"---\nname: intercom-automation\ndescription: \"Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Intercom Automation via Rube MCP\n\nAutomate Intercom operations through Composio's Intercom toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Intercom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`\n3. If connection is not ACTIVE, follow the returned auth link to complete Intercom OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Conversations\n\n**When to use**: User wants to create, list, search, or manage support conversations\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_ADMINS` - Get admin IDs for assignment [Prerequisite]\n2. `INTERCOM_LIST_CONVERSATIONS` - List all conversations [Optional]\n3. `INTERCOM_SEARCH_CONVERSATIONS` - Search with filters [Optional]\n4. `INTERCOM_GET_CONVERSATION` - Get conversation details [Optional]\n5. `INTERCOM_CREATE_CONVERSATION` - Create a new conversation [Optional]\n\n**Key parameters**:\n- `from`: Object with `type` ('user'\u002F'lead') and `id` for conversation creator\n- `body`: Message body (HTML supported)\n- `id`: Conversation ID for retrieval\n- `query`: Search query object with `field`, `operator`, `value`\n\n**Pitfalls**:\n- CREATE_CONVERSATION requires a contact (user\u002Flead) as the `from` field, not an admin\n- Conversation bodies support HTML; plain text is auto-wrapped in `\u003Cp>` tags\n- Search query uses structured filter objects, not free-text search\n- Conversation IDs are numeric strings\n\n### 2. Reply and Manage Conversation State\n\n**When to use**: User wants to reply to, close, reopen, or assign conversations\n\n**Tool sequence**:\n1. `INTERCOM_GET_CONVERSATION` - Get current state [Prerequisite]\n2. `INTERCOM_REPLY_TO_CONVERSATION` - Add a reply [Optional]\n3. `INTERCOM_ASSIGN_CONVERSATION` - Assign to admin\u002Fteam [Optional]\n4. `INTERCOM_CLOSE_CONVERSATION` - Close conversation [Optional]\n5. `INTERCOM_REOPEN_CONVERSATION` - Reopen closed conversation [Optional]\n\n**Key parameters**:\n- `conversation_id` \u002F `id`: Conversation ID\n- `body`: Reply message body (HTML supported)\n- `type`: Reply type ('admin' or 'user')\n- `admin_id`: Admin ID for replies from admin, assignment, and close\u002Freopen\n- `assignee_id`: Admin or team ID for assignment\n- `message_type`: 'comment' (default) or 'note' (internal)\n\n**Pitfalls**:\n- `admin_id` is REQUIRED for admin replies, close, reopen, and assignment operations\n- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN\n- Duplicate sends can occur on retry; implement idempotency checks\n- Internal notes use `message_type: 'note'`; visible only to workspace members\n- Closing requires an admin_id and optional body message\n\n### 3. Manage Contacts\n\n**When to use**: User wants to search, view, or manage contacts (users and leads)\n\n**Tool sequence**:\n1. `INTERCOM_SEARCH_CONTACTS` - Search contacts with filters [Required]\n2. `INTERCOM_GET_A_CONTACT` - Get specific contact [Optional]\n3. `INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID` - Look up by external ID [Optional]\n4. `INTERCOM_LIST_CONTACTS` - List all contacts [Optional]\n5. `INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT` - Get contact tags [Optional]\n6. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Get contact segments [Optional]\n7. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]\n\n**Key parameters**:\n- `contact_id`: Contact ID for retrieval\n- `external_id`: External system ID for lookup\n- `query`: Search filter object with `field`, `operator`, `value`\n- `pagination`: Object with `per_page` and `starting_after` cursor\n\n**Pitfalls**:\n- SEARCH_CONTACTS uses structured query filters, not free-text; format: `{field, operator, value}`\n- Supported operators: `=`, `!=`, `>`, `\u003C`, `~` (contains), `!~` (not contains), `IN`, `NIN`\n- Contact types are 'user' (identified) or 'lead' (anonymous)\n- LIST_CONTACTS returns paginated results; use `starting_after` cursor for pagination\n- External IDs are case-sensitive\n\n### 4. Manage Admins and Teams\n\n**When to use**: User wants to list workspace admins or identify specific admins\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_ADMINS` - List all admins and teams [Required]\n2. `INTERCOM_IDENTIFY_AN_ADMIN` - Get specific admin details [Optional]\n\n**Key parameters**:\n- `admin_id`: Admin ID for identification\n\n**Pitfalls**:\n- LIST_ALL_ADMINS returns both admins and teams\n- Admin IDs are required for conversation replies, assignment, close, and reopen\n- Teams appear in the admins list with `type: 'team'`\n\n### 5. View Segments and Counts\n\n**When to use**: User wants to view segments or get aggregate counts\n\n**Tool sequence**:\n1. `INTERCOM_LIST_SEGMENTS` - List all segments [Optional]\n2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Segments for a contact [Optional]\n3. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Segments for a company [Optional]\n4. `INTERCOM_GET_COUNTS` - Get aggregate counts [Optional]\n\n**Key parameters**:\n- `contact_id`: Contact ID for segment lookup\n- `company_id`: Company ID for segment lookup\n- `type`: Count type ('conversation', 'company', 'user', 'tag', 'segment')\n- `count`: Sub-count type\n\n**Pitfalls**:\n- GET_COUNTS returns approximate counts, not exact numbers\n- Segment membership is computed; changes may not reflect immediately\n\n### 6. Manage Companies\n\n**When to use**: User wants to list companies or manage company-contact relationships\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_COMPANIES` - List all companies [Required]\n2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Get company segments [Optional]\n3. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]\n\n**Key parameters**:\n- `company_id`: Company ID\n- `contact_id`: Contact ID for detachment\n- `page`: Page number for pagination\n- `per_page`: Results per page\n\n**Pitfalls**:\n- Company-contact relationships are managed through contact endpoints\n- DETACH_A_CONTACT removes the contact-company association, not the contact itself\n\n## Common Patterns\n\n### Search Query Filters\n\n**Single filter**:\n```json\n{\n  \"field\": \"email\",\n  \"operator\": \"=\",\n  \"value\": \"user@example.com\"\n}\n```\n\n**Multiple filters (AND)**:\n```json\n{\n  \"operator\": \"AND\",\n  \"value\": [\n    {\"field\": \"role\", \"operator\": \"=\", \"value\": \"user\"},\n    {\"field\": \"created_at\", \"operator\": \">\", \"value\": 1672531200}\n  ]\n}\n```\n\n**Supported fields for contacts**: email, name, role, created_at, updated_at, signed_up_at, last_seen_at, external_id\n\n**Supported fields for conversations**: created_at, updated_at, source.type, state, open, read\n\n### Pagination\n\n- Most list endpoints use cursor-based pagination\n- Check response for `pages.next` with `starting_after` cursor\n- Pass cursor in `pagination.starting_after` for next page\n- Continue until `pages.next` is null\n\n### Admin ID Resolution\n\n```\n1. Call INTERCOM_LIST_ALL_ADMINS to get all admins\n2. Find the desired admin by name or email\n3. Use admin.id for replies, assignments, and state changes\n```\n\n## Known Pitfalls\n\n**Admin ID Requirement**:\n- Admin ID is required for: reply (as admin), assign, close, reopen\n- Always resolve admin IDs first with LIST_ALL_ADMINS\n\n**HTML Content**:\n- Conversation bodies are HTML\n- Plain text is auto-wrapped in paragraph tags\n- Sanitize HTML input to prevent rendering issues\n\n**Idempotency**:\n- Replies and conversation creation are not idempotent\n- Duplicate sends can occur on retry or timeout\n- Track message IDs to prevent duplicates\n\n**Rate Limits**:\n- Default: ~1000 requests per minute (varies by plan)\n- 429 responses include rate limit headers\n- Implement exponential backoff for retries\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List conversations | INTERCOM_LIST_CONVERSATIONS | (pagination) |\n| Search conversations | INTERCOM_SEARCH_CONVERSATIONS | query |\n| Get conversation | INTERCOM_GET_CONVERSATION | id |\n| Create conversation | INTERCOM_CREATE_CONVERSATION | from, body |\n| Reply to conversation | INTERCOM_REPLY_TO_CONVERSATION | conversation_id, body, admin_id |\n| Assign conversation | INTERCOM_ASSIGN_CONVERSATION | conversation_id, admin_id, assignee_id |\n| Close conversation | INTERCOM_CLOSE_CONVERSATION | id, admin_id |\n| Reopen conversation | INTERCOM_REOPEN_CONVERSATION | id, admin_id |\n| Search contacts | INTERCOM_SEARCH_CONTACTS | query |\n| Get contact | INTERCOM_GET_A_CONTACT | contact_id |\n| Contact by external ID | INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID | external_id |\n| List contacts | INTERCOM_LIST_CONTACTS | (pagination) |\n| Contact tags | INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT | contact_id |\n| Contact segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT | contact_id |\n| Detach contact | INTERCOM_DETACH_A_CONTACT | contact_id, company_id |\n| List admins | INTERCOM_LIST_ALL_ADMINS | (none) |\n| Identify admin | INTERCOM_IDENTIFY_AN_ADMIN | admin_id |\n| List segments | INTERCOM_LIST_SEGMENTS | (none) |\n| Company segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES | company_id |\n| Get counts | INTERCOM_GET_COUNTS | type, count |\n| List companies | INTERCOM_LIST_ALL_COMPANIES | page, per_page |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Intercom Automation via Rube MCP\n\nAutomate Intercom operations through Composio's Intercom toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Intercom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`\n3. If connection is not ACTIVE, follow the returned auth link to complete Intercom OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Conversations\n\n**When to use**: User wants to create, list, search, or manage support conversations\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_ADMINS` - Get admin IDs for assignment [Prerequisite]\n2. `INTERCOM_LIST_CONVERSATIONS` - List all conversations [Optional]\n3. `INTERCOM_SEARCH_CONVERSATIONS` - Search with filters [Optional]\n4. `INTERCOM_GET_CONVERSATION` - Get conversation details [Optional]\n5. `INTERCOM_CREATE_CONVERSATION` - Create a new conversation [Optional]\n\n**Key parameters**:\n- `from`: Object with `type` ('user'\u002F'lead') and `id` for conversation creator\n- `body`: Message body (HTML supported)\n- `id`: Conversation ID for retrieval\n- `query`: Search query object with `field`, `operator`, `value`\n\n**Pitfalls**:\n- CREATE_CONVERSATION requires a contact (user\u002Flead) as the `from` field, not an admin\n- Conversation bodies support HTML; plain text is auto-wrapped in `\u003Cp>` tags\n- Search query uses structured filter objects, not free-text search\n- Conversation IDs are numeric strings\n\n### 2. Reply and Manage Conversation State\n\n**When to use**: User wants to reply to, close, reopen, or assign conversations\n\n**Tool sequence**:\n1. `INTERCOM_GET_CONVERSATION` - Get current state [Prerequisite]\n2. `INTERCOM_REPLY_TO_CONVERSATION` - Add a reply [Optional]\n3. `INTERCOM_ASSIGN_CONVERSATION` - Assign to admin\u002Fteam [Optional]\n4. `INTERCOM_CLOSE_CONVERSATION` - Close conversation [Optional]\n5. `INTERCOM_REOPEN_CONVERSATION` - Reopen closed conversation [Optional]\n\n**Key parameters**:\n- `conversation_id` \u002F `id`: Conversation ID\n- `body`: Reply message body (HTML supported)\n- `type`: Reply type ('admin' or 'user')\n- `admin_id`: Admin ID for replies from admin, assignment, and close\u002Freopen\n- `assignee_id`: Admin or team ID for assignment\n- `message_type`: 'comment' (default) or 'note' (internal)\n\n**Pitfalls**:\n- `admin_id` is REQUIRED for admin replies, close, reopen, and assignment operations\n- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN\n- Duplicate sends can occur on retry; implement idempotency checks\n- Internal notes use `message_type: 'note'`; visible only to workspace members\n- Closing requires an admin_id and optional body message\n\n### 3. Manage Contacts\n\n**When to use**: User wants to search, view, or manage contacts (users and leads)\n\n**Tool sequence**:\n1. `INTERCOM_SEARCH_CONTACTS` - Search contacts with filters [Required]\n2. `INTERCOM_GET_A_CONTACT` - Get specific contact [Optional]\n3. `INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID` - Look up by external ID [Optional]\n4. `INTERCOM_LIST_CONTACTS` - List all contacts [Optional]\n5. `INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT` - Get contact tags [Optional]\n6. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Get contact segments [Optional]\n7. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]\n\n**Key parameters**:\n- `contact_id`: Contact ID for retrieval\n- `external_id`: External system ID for lookup\n- `query`: Search filter object with `field`, `operator`, `value`\n- `pagination`: Object with `per_page` and `starting_after` cursor\n\n**Pitfalls**:\n- SEARCH_CONTACTS uses structured query filters, not free-text; format: `{field, operator, value}`\n- Supported operators: `=`, `!=`, `>`, `\u003C`, `~` (contains), `!~` (not contains), `IN`, `NIN`\n- Contact types are 'user' (identified) or 'lead' (anonymous)\n- LIST_CONTACTS returns paginated results; use `starting_after` cursor for pagination\n- External IDs are case-sensitive\n\n### 4. Manage Admins and Teams\n\n**When to use**: User wants to list workspace admins or identify specific admins\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_ADMINS` - List all admins and teams [Required]\n2. `INTERCOM_IDENTIFY_AN_ADMIN` - Get specific admin details [Optional]\n\n**Key parameters**:\n- `admin_id`: Admin ID for identification\n\n**Pitfalls**:\n- LIST_ALL_ADMINS returns both admins and teams\n- Admin IDs are required for conversation replies, assignment, close, and reopen\n- Teams appear in the admins list with `type: 'team'`\n\n### 5. View Segments and Counts\n\n**When to use**: User wants to view segments or get aggregate counts\n\n**Tool sequence**:\n1. `INTERCOM_LIST_SEGMENTS` - List all segments [Optional]\n2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Segments for a contact [Optional]\n3. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Segments for a company [Optional]\n4. `INTERCOM_GET_COUNTS` - Get aggregate counts [Optional]\n\n**Key parameters**:\n- `contact_id`: Contact ID for segment lookup\n- `company_id`: Company ID for segment lookup\n- `type`: Count type ('conversation', 'company', 'user', 'tag', 'segment')\n- `count`: Sub-count type\n\n**Pitfalls**:\n- GET_COUNTS returns approximate counts, not exact numbers\n- Segment membership is computed; changes may not reflect immediately\n\n### 6. Manage Companies\n\n**When to use**: User wants to list companies or manage company-contact relationships\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_COMPANIES` - List all companies [Required]\n2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Get company segments [Optional]\n3. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]\n\n**Key parameters**:\n- `company_id`: Company ID\n- `contact_id`: Contact ID for detachment\n- `page`: Page number for pagination\n- `per_page`: Results per page\n\n**Pitfalls**:\n- Company-contact relationships are managed through contact endpoints\n- DETACH_A_CONTACT removes the contact-company association, not the contact itself\n\n## Common Patterns\n\n### Search Query Filters\n\n**Single filter**:\n```json\n{\n  \"field\": \"email\",\n  \"operator\": \"=\",\n  \"value\": \"user@example.com\"\n}\n```\n\n**Multiple filters (AND)**:\n```json\n{\n  \"operator\": \"AND\",\n  \"value\": [\n    {\"field\": \"role\", \"operator\": \"=\", \"value\": \"user\"},\n    {\"field\": \"created_at\", \"operator\": \">\", \"value\": 1672531200}\n  ]\n}\n```\n\n**Supported fields for contacts**: email, name, role, created_at, updated_at, signed_up_at, last_seen_at, external_id\n\n**Supported fields for conversations**: created_at, updated_at, source.type, state, open, read\n\n### Pagination\n\n- Most list endpoints use cursor-based pagination\n- Check response for `pages.next` with `starting_after` cursor\n- Pass cursor in `pagination.starting_after` for next page\n- Continue until `pages.next` is null\n\n### Admin ID Resolution\n\n```\n1. Call INTERCOM_LIST_ALL_ADMINS to get all admins\n2. Find the desired admin by name or email\n3. Use admin.id for replies, assignments, and state changes\n```\n\n## Known Pitfalls\n\n**Admin ID Requirement**:\n- Admin ID is required for: reply (as admin), assign, close, reopen\n- Always resolve admin IDs first with LIST_ALL_ADMINS\n\n**HTML Content**:\n- Conversation bodies are HTML\n- Plain text is auto-wrapped in paragraph tags\n- Sanitize HTML input to prevent rendering issues\n\n**Idempotency**:\n- Replies and conversation creation are not idempotent\n- Duplicate sends can occur on retry or timeout\n- Track message IDs to prevent duplicates\n\n**Rate Limits**:\n- Default: ~1000 requests per minute (varies by plan)\n- 429 responses include rate limit headers\n- Implement exponential backoff for retries\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List conversations | INTERCOM_LIST_CONVERSATIONS | (pagination) |\n| Search conversations | INTERCOM_SEARCH_CONVERSATIONS | query |\n| Get conversation | INTERCOM_GET_CONVERSATION | id |\n| Create conversation | INTERCOM_CREATE_CONVERSATION | from, body |\n| Reply to conversation | INTERCOM_REPLY_TO_CONVERSATION | conversation_id, body, admin_id |\n| Assign conversation | INTERCOM_ASSIGN_CONVERSATION | conversation_id, admin_id, assignee_id |\n| Close conversation | INTERCOM_CLOSE_CONVERSATION | id, admin_id |\n| Reopen conversation | INTERCOM_REOPEN_CONVERSATION | id, admin_id |\n| Search contacts | INTERCOM_SEARCH_CONTACTS | query |\n| Get contact | INTERCOM_GET_A_CONTACT | contact_id |\n| Contact by external ID | INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID | external_id |\n| List contacts | INTERCOM_LIST_CONTACTS | (pagination) |\n| Contact tags | INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT | contact_id |\n| Contact segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT | contact_id |\n| Detach contact | INTERCOM_DETACH_A_CONTACT | contact_id, company_id |\n| List admins | INTERCOM_LIST_ALL_ADMINS | (none) |\n| Identify admin | INTERCOM_IDENTIFY_AN_ADMIN | admin_id |\n| List segments | INTERCOM_LIST_SEGMENTS | (none) |\n| Company segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES | company_id |\n| Get counts | INTERCOM_GET_COUNTS | type, count |\n| List companies | INTERCOM_LIST_ALL_COMPANIES | page, per_page |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":44,"source":33,"requires":45,"description":7},"unknown",{"mcp":46},[47],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fintercom-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add reikiplanet\u002Fdaoskills --skill intercom-automation",{"tool":62,"command":63},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill intercom-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill intercom-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fintercom-automation\u002FSKILL.md",true,[],[71,97,109,124,144,167],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":39},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[78,79,80,81,82,83,33,84,85,86,87,88,89,90,91,92,93,94,95,96],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":39},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[104,105,95,106,107,33,85,86,87,81,108,82],"ar","vr ar","interaction","requirements","performance",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":39},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[111,116,117,118,119,120,33,121,87,122,123,81],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[131,132,133,134,135,33,136,137,138,139,121,140,141,142,143],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":39},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[151,152,153,154,155,156,157,158,33,87,81,159,82,160,161,162,163,164,165,166],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":39},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,164,121,182,183,184,33,185,186,187,161,188,189],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]