intercom-automation

Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.

Install with Tessl CLI

npx tessl i github:davepoon/buildwithclaude --skill intercom-automation

What are skills?

1.55x

Quality

52%

Does it follow best practices?

Impact

92%

1.55x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/intercom-automation/SKILL.md

SKILL.md

Review

Evals

Discovery

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear niche (Intercom automation) and lists relevant entity types, providing good distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and the actions are too vague ('automate tasks' rather than specific operations). The instruction to 'search tools first' is operational guidance rather than helping with skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Intercom, customer conversations, support tickets, or managing contacts/companies in Intercom'

Replace vague 'automate tasks' with specific actions like 'list conversations, create contacts, update companies, manage segments, lookup admins'

Include natural user terms like 'customer support', 'chat history', 'support inbox' that users might say when needing Intercom functionality

Dimension	Reasoning	Score
Specificity	Names the domain (Intercom via Rube MCP/Composio) and lists entity types (conversations, contacts, companies, segments, admins) but doesn't specify concrete actions beyond generic 'automate tasks'.	2 / 3
Completeness	Describes what it does (automate Intercom tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Intercom', 'conversations', 'contacts', 'companies' that users might mention, but missing common variations like 'customer support', 'chat', 'messaging', or action-oriented terms like 'send message', 'create contact'.	2 / 3
Distinctiveness Conflict Risk	Very specific to Intercom platform with clear technical context (Rube MCP, Composio), making it highly unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with comprehensive coverage of Intercom operations. Its main strengths are concrete tool names, clear parameter specifications, and helpful pitfall warnings. However, it's somewhat verbose with repeated information, and lacks explicit validation/verification steps for non-idempotent operations that could cause duplicate sends.

Suggestions

Add explicit validation steps after non-idempotent operations (e.g., 'After CREATE_CONVERSATION, verify with GET_CONVERSATION using returned ID before proceeding')

Consolidate repeated pitfalls (admin ID requirement, HTML content) into a single 'Critical Requirements' section to reduce redundancy

Consider splitting detailed workflow sections into separate files (e.g., CONVERSATIONS.md, CONTACTS.md) with SKILL.md as a concise overview pointing to them

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections (admin ID requirement mentioned multiple times), and some explanations could be tighter. The quick reference table duplicates information already covered in workflows.	2 / 3
Actionability	Provides concrete tool names, specific parameter names, and executable JSON examples for search queries. The tool sequences are explicit with clear parameter requirements, making it copy-paste ready for Claude to execute.	3 / 3
Workflow Clarity	Tool sequences are clearly listed with prerequisites marked, but lacks explicit validation checkpoints. For operations like conversation creation or replies (which the skill notes are not idempotent), there's no verify-then-proceed pattern or error recovery workflow.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the document is quite long (~250 lines) with all content inline. The toolkit docs link is provided but detailed workflows could be split into separate files with SKILL.md serving as a leaner overview.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.