persistiq-automation
by ComposioHQpersistiq-automation helps Claude run PersistIQ sales outreach tasks through Composio Rube MCP by searching live tool schemas, checking the PersistIQ connection, and executing authenticated workflows with less guesswork.
This skill scores 68/100, which makes it acceptable but limited for directory listing. Directory users get enough information to understand when to use it and how an agent should begin Persistiq automation through Rube MCP, but they should expect a lightweight wrapper rather than a deeply documented Persistiq workflow pack.
- Clear trigger and scope: it is intended for automating Persistiq operations through Composio's Persistiq toolkit via Rube MCP.
- Provides concrete prerequisites and setup steps, including adding the Rube MCP endpoint, checking `RUBE_SEARCH_TOOLS`, and activating a Persistiq connection.
- Explicitly instructs agents to call `RUBE_SEARCH_TOOLS` first, which reduces schema guesswork and helps keep execution aligned with current tool definitions.
- No support files, examples, scripts, or reference material beyond SKILL.md, so users must rely on live Rube tool discovery for exact Persistiq schemas and operations.
- The guidance is mostly a generic Rube MCP discovery/connect/execute pattern, with limited Persistiq-specific task detail in the available evidence.
Overview of persistiq-automation skill
What persistiq-automation does
persistiq-automation is a Claude skill for running PersistIQ sales outreach operations through Composio’s Rube MCP. Instead of guessing API fields or relying on stale examples, the skill instructs the agent to search the available Rube tools first, confirm the PersistIQ connection, then execute the right action with the current schema.
Best fit for Sales Outreach teams
The persistiq-automation skill is most useful when you want an AI agent to help with operational PersistIQ work: finding the right tool for a contact, campaign, prospect, sequence, or outreach task; checking required fields; and running the workflow through an authenticated PersistIQ connection. It fits sales ops, growth teams, founders, and RevOps users who already use PersistIQ and want less manual tool navigation.
Key differentiator: schema discovery first
The main value is not a long library of hardcoded commands. The skill’s strongest pattern is: discover tools with RUBE_SEARCH_TOOLS, verify authentication with RUBE_MANAGE_CONNECTIONS, then execute using the returned schema. That matters because MCP tool names, required fields, and execution plans can change. For a sales outreach workflow, this reduces failed calls caused by missing IDs, outdated field names, or assumptions about PersistIQ’s data model.
Adoption considerations
You need an MCP client that can connect to Rube, and you need an active PersistIQ connection. This is not a standalone PersistIQ integration, scraper, or campaign strategy generator. It is best installed when you want Claude to operate PersistIQ through Composio-managed tools and you are comfortable authorizing account access.
How to Use persistiq-automation skill
persistiq-automation install and setup context
Install the skill from the Composio skills repository, for example:
npx skills add ComposioHQ/awesome-claude-skills --skill persistiq-automation
Then add Rube MCP as a server in your AI client using:
https://rube.app/mcp
Before asking for any PersistIQ action, verify that RUBE_SEARCH_TOOLS is available. Next, use RUBE_MANAGE_CONNECTIONS with toolkit persistiq and complete the returned authorization flow if the connection is not ACTIVE. Do not start campaign or prospect operations until the connection status is confirmed.
Inputs the skill needs for reliable execution
A weak request is: “Add this lead to PersistIQ.” A better persistiq-automation usage prompt includes the business goal, object type, known identifiers, acceptable matching rules, and safety limits.
Example:
“Use persistiq-automation for Sales Outreach. Search Rube tools for the current PersistIQ schema. I need to add Jane Doe, [email protected], VP Sales at Acme, to the outbound sequence named Q1 SaaS VP Follow-up. If multiple matching sequences exist, show me the options before acting. Do not create duplicates; first check whether this email already exists in PersistIQ.”
This gives the agent enough context to search for the right tool, inspect required fields, avoid duplicates, and ask before taking irreversible action.
Recommended workflow for a complete task
Use this sequence for most requests:
- Ask the agent to call
RUBE_SEARCH_TOOLSfor the specific PersistIQ task, not a generic “PersistIQ operations” query. - Ask it to summarize the returned tool slug, required inputs, and any known pitfalls before execution.
- Confirm the PersistIQ connection with
RUBE_MANAGE_CONNECTIONS. - Provide exact campaign, prospect, sequence, or account identifiers when you have them.
- Require a short post-action report: what was changed, what was skipped, and what needs human review.
This pattern is especially important for sales outreach because duplicate contacts, wrong sequence assignment, or unintended campaign changes can affect real prospects.
Repository files to read first
The upstream skill is compact. Start with composio-skills/persistiq-automation/SKILL.md; it contains the prerequisites, setup flow, discovery rule, and core workflow pattern. There are no extra rules/, resources/, references/, or scripts in the current file tree, so the practical behavior is concentrated in that single file. If you need deeper tool specifics, use the linked Composio PersistIQ toolkit documentation and live RUBE_SEARCH_TOOLS output rather than expecting static examples in the repository.
persistiq-automation skill FAQ
Is persistiq-automation beginner friendly?
Yes, if your MCP client is already configured and you can authorize PersistIQ through Rube. Beginners may struggle less with the skill than with raw API usage because it pushes the agent to discover schemas before acting. However, you still need to understand your sales process well enough to approve changes to prospects, campaigns, and sequences.
How is this better than an ordinary Claude prompt?
A generic prompt can suggest outreach steps, but it cannot reliably know the current Composio tool schema. The persistiq-automation skill adds an execution discipline: search tools first, check connection status, then run the task using live tool metadata. That makes it better for operational actions than a free-form sales automation prompt.
When should I not use this skill?
Do not use it when you only need copywriting, email personalization, lead research, or CRM strategy with no PersistIQ operation. It is also a poor fit if your organization does not allow AI agents to access sales outreach tools, or if you cannot tolerate agent-assisted changes without manual approval.
Does it replace PersistIQ campaign planning?
No. The skill helps operate PersistIQ through Rube MCP; it does not replace list strategy, compliance review, deliverability planning, or human judgment about who should receive outreach. Use it as an automation layer, not as the final authority on campaign design.
How to Improve persistiq-automation skill
Improve persistiq-automation prompts with constraints
The best results come from prompts that include explicit guardrails. Add constraints such as “do not create new prospects,” “ask before enrolling anyone,” “only update records matching this domain,” or “return a dry-run plan first.” These constraints matter because sales outreach actions can affect live contacts and campaign behavior.
Provide stronger identifiers and matching rules
Names alone are weak inputs. Prefer email addresses, PersistIQ IDs, campaign names, sequence names, company domains, and deduplication rules. For example: “Match by email first, then company domain plus full name; if confidence is below 90%, stop and ask.” This reduces accidental updates and helps the agent select the right Rube tool inputs.
Watch for common failure modes
The most common issues are inactive PersistIQ connections, skipped tool discovery, missing required fields, ambiguous campaign names, and assuming a tool exists before RUBE_SEARCH_TOOLS confirms it. If the first output looks uncertain, ask the agent to restate the discovered schema and explain which fields are required before it executes.
Iterate after the first output
After the first run, improve the workflow by asking for a concise execution log: tools searched, tool selected, inputs used, records changed, records skipped, and follow-up questions. Save successful prompt patterns for recurring sales outreach tasks such as adding prospects, checking existing contacts, updating campaign membership, or auditing sequence enrollment.