activecampaign-automation
Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.
72
58%
Does it follow best practices?
Impact
99%
2.53xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/activecampaign-automation/SKILL.mdQuality
Discovery
67%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 is strong in specificity and distinctiveness, clearly naming the platform and listing concrete actions. However, it lacks an explicit 'Use when...' clause, which limits completeness, and the trigger terms could better cover natural user language like 'email marketing', 'CRM', or 'subscribers'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ActiveCampaign, managing email contacts, subscriber lists, or marketing automation workflows.'
Include natural user-facing trigger terms like 'email marketing', 'CRM', 'subscribers', 'mailing list', and 'campaign management' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manage contacts, tags, list subscriptions, automation enrollment, and tasks. Also includes the operational guidance to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (manage contacts, tags, subscriptions, automation, tasks via ActiveCampaign), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied by the domain. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'ActiveCampaign', 'contacts', 'tags', 'list subscriptions', 'automation enrollment', and 'tasks', but misses common user variations like 'email marketing', 'CRM', 'subscriber', 'campaign', or 'mailing list'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform name 'ActiveCampaign' and the integration method 'Rube MCP (Composio)'. Unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid domain-specific knowledge about ActiveCampaign tool usage through Composio/Rube MCP, with valuable details about capitalization quirks, ID types, and parameter precedence. Its main weaknesses are verbosity through repetition (pitfalls restated across sections), lack of executable examples with concrete parameter values, and missing validation/verification steps in workflows. Trimming duplicated content and adding concrete invocation examples would significantly improve it.
Suggestions
Consolidate pitfalls into a single section and remove duplicates from individual workflows — the same information about ID precedence, capitalization, and string types appears 2-3 times.
Add at least one concrete, executable tool invocation example with realistic parameter values (e.g., a full RUBE_SEARCH_TOOLS call followed by a MANAGE_CONTACT_TAG call with specific inputs and expected response structure).
Add explicit validation steps after key operations (e.g., 'After creating a contact, call FIND_CONTACT to confirm creation and retrieve the contact ID') to create proper feedback loops.
Remove 'When to use' lines that merely restate the section title — these add tokens without value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but verbose for what it conveys. There's significant repetition across workflows (e.g., every workflow repeats the FIND_CONTACT prerequisite pattern, pitfalls about ID precedence are restated multiple times). The 'Known Pitfalls' section at the bottom largely duplicates pitfalls already listed under each workflow. Claude doesn't need explanations like 'User wants to create new contacts or look up existing ones' for a section titled 'Create and Find Contacts'. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and important details like capitalization requirements, which is valuable. However, there are no executable code examples — the 'Common Patterns' section uses plain text pseudocode rather than actual tool invocation examples with concrete parameter values. The guidance is specific enough to act on but falls short of copy-paste ready. | 2 / 3 |
Workflow Clarity | Each workflow has a clear tool sequence with prerequisite steps and numbered ordering. However, there are no explicit validation checkpoints — no steps to verify that a contact was actually created, that tags were applied, or that automation enrollment succeeded. For batch operations (Bulk Contact Tagging), there's no error recovery or feedback loop, just a note to 'respect rate limits'. Missing verification steps cap this at 2. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a useful quick reference table. However, with no bundle files, all content is inline in a single long document (~180 lines of substantive content). The detailed pitfalls for each workflow and the duplicated 'Known Pitfalls' section could be split into a reference file. The external link to Composio docs is helpful but the skill itself is monolithic. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- Reviewed
Table of Contents
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.