salesmate-automation
by ComposioHQsalesmate-automation helps CRM Operations teams run Salesmate tasks through Composio Rube MCP. It emphasizes RUBE_SEARCH_TOOLS, active connection checks, and schema-based execution before CRM reads or writes.
This skill scores 66/100, which means it is acceptable for listing but should be presented as a limited, MCP-dependent helper rather than a complete Salesmate playbook. Directory users get enough information to understand when to use it and how an agent should start, but they should expect to rely on Rube tool discovery for most task-specific details.
- Valid frontmatter declares the required `rube` MCP and a clear Salesmate automation trigger.
- Prerequisites and setup steps explain how to connect Rube MCP, activate the Salesmate toolkit connection, and verify availability before execution.
- The skill repeatedly instructs agents to call `RUBE_SEARCH_TOOLS` first, reducing schema guesswork and helping adapt to current Salesmate tool definitions.
- The skill is mostly a Rube MCP discovery-and-connection wrapper; the available evidence shows limited Salesmate-specific operational detail beyond discovering tools for the user's task.
- No install command or supporting reference files are included, and the excerpt shows a possible naming inconsistency between `RUBE_MANAGE_CONNECTIONS` and `RUBE_MANAGE_CONNECTION`.
Overview of salesmate-automation skill
What salesmate-automation is for
salesmate-automation is a Claude skill for running Salesmate CRM tasks through Composio’s Rube MCP. It is designed for users who want an agent to discover the current Salesmate tool schema, confirm the CRM connection, and execute operations such as contact, company, deal, activity, or workflow-related CRM actions without hard-coding stale API assumptions.
Best fit for CRM Operations teams
The best fit is CRM Operations, RevOps, sales admins, and automation builders who already use Salesmate and want AI-assisted execution with safer tool discovery. The real job-to-be-done is not “write a Salesmate prompt”; it is “turn a CRM operation into a valid Rube MCP tool call after checking the available tools and active connection.”
What makes this skill different
The key differentiator is its insistence on RUBE_SEARCH_TOOLS before execution. Salesmate tool names, inputs, and supported operations can change, so the skill guides the agent to retrieve current schemas instead of guessing. That makes salesmate-automation more reliable than a generic CRM prompt when exact fields, tool slugs, or execution plans matter.
Important adoption constraints
This skill depends on Rube MCP and an active Salesmate connection. It does not include helper scripts, local configuration files, or custom business rules. If your workflow requires company-specific field mapping, deduplication policy, pipeline definitions, or approval logic, you must provide those details in the prompt or maintain them outside the skill.
How to Use salesmate-automation skill
salesmate-automation install and setup context
Install the skill from the Composio skills repository with your skills client, for example:
npx skills add ComposioHQ/awesome-claude-skills --skill salesmate-automation
Then configure Rube MCP in your AI client by adding https://rube.app/mcp as an MCP server. Before asking the agent to run CRM work, verify that RUBE_SEARCH_TOOLS is available and use RUBE_MANAGE_CONNECTIONS for the salesmate toolkit. If the Salesmate connection is not ACTIVE, complete the returned authorization flow first.
Inputs the skill needs before acting
Good salesmate-automation usage starts with a precise CRM objective and enough Salesmate context to avoid destructive or ambiguous changes. Provide:
- The object type: contact, company, deal, activity, note, task, or another Salesmate entity.
- The operation: search, create, update, list, link, enrich, or report.
- Matching rules: email, domain, record ID, owner, pipeline, stage, or date range.
- Field requirements: exact Salesmate field names when known, or ask the agent to inspect schemas first.
- Safety rules: dry run first, no bulk updates, limit records, require confirmation before writes.
Weak prompt: “Update my Salesmate deals.”
Stronger prompt: “Use salesmate-automation for CRM Operations. First run RUBE_SEARCH_TOOLS for Salesmate deal update tools, then check the Salesmate connection. Find open deals in pipeline ‘SMB Sales’ with close date before today and stage not ‘Closed Lost’. Return a preview with deal ID, owner, stage, close date, and proposed new task. Do not write changes until I approve.”
Practical workflow for reliable execution
A strong workflow follows the pattern in SKILL.md:
- Discover tools with
RUBE_SEARCH_TOOLSfor the exact Salesmate task. - Check the Salesmate connection with the Rube connection management tool.
- Review returned tool slugs, schemas, required fields, and pitfalls.
- Ask the agent to produce an execution plan before making writes.
- Run read or search calls first, then confirm write operations.
This order matters because it keeps the agent grounded in live tool schemas and reduces mistakes caused by outdated Salesmate assumptions.
Repository files to read first
Start with composio-skills/salesmate-automation/SKILL.md. This repository path is intentionally minimal: there are no extra rules/, resources/, references/, or scripts to inspect. The most important source details are the prerequisites, setup sequence, tool discovery requirement, and core workflow pattern. For Salesmate-specific tool coverage, use the linked Composio toolkit documentation and live RUBE_SEARCH_TOOLS results rather than relying on static repository text.
salesmate-automation skill FAQ
Is salesmate-automation better than a normal prompt?
Yes, when the task needs actual Salesmate tool execution through Rube MCP. A normal prompt can describe a CRM workflow, but it may invent fields or tool names. The salesmate-automation skill directs the agent to search tools first, check the active connection, and use current schemas before acting.
Can beginners use this skill?
Beginners can use it if Rube MCP is already available in their client and someone can authorize the Salesmate connection. The skill is not a full Salesmate training guide, so new users should start with read-only searches and previews before allowing creates or updates.
What should I not use it for?
Do not use salesmate-automation as a substitute for CRM governance. It will not define your lifecycle stages, dedupe rules, territory logic, or compliance approvals. Avoid using it for large bulk edits until you have tested the exact schema, record filters, and rollback plan.
Does it require Composio or Rube MCP?
Yes. The repository states that Rube MCP is required and that Salesmate operations run through Composio’s Salesmate toolkit via Rube. If your environment cannot use MCP tools or cannot connect Salesmate through Rube, this skill is not the right installation choice.
How to Improve salesmate-automation skill
Improve salesmate-automation prompts with CRM context
The fastest way to improve results is to include your Salesmate operating context. Add pipeline names, lifecycle definitions, required fields, custom field meanings, owner rules, and examples of valid records. This helps the agent choose the right discovered tool and prevents technically valid but operationally wrong CRM updates.
Prevent common failure modes
Common issues include inactive Salesmate connections, missing required fields, ambiguous record matching, and write operations run before a preview. To reduce risk, require the agent to state the discovered tool slug, required input schema, target record count, and proposed changes before execution. For bulk work, set a small limit such as 5 records for the first run.
Iterate after the first output
After the first tool discovery or preview, refine the task using the returned schema. If the tool requires id instead of email, ask for a search step first. If a field name differs from your internal terminology, map it explicitly. If the result set is too broad, add filters for owner, pipeline, stage, date, or status.
Add local operating rules around the skill
Because the upstream skill is intentionally compact, teams can improve practical output by pairing it with internal CRM rules: “never overwrite source,” “confirm before changing owner,” “log a note on every automated update,” or “create tasks instead of directly changing stages.” These rules make salesmate-automation safer for CRM Operations without changing the core skill.