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.
52
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-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 (ActiveCampaign) and listing concrete actions. However, it lacks an explicit 'Use when...' clause, which caps completeness, and the trigger terms lean technical rather than matching natural user language around email marketing or CRM tasks.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ActiveCampaign, managing email contacts, tagging subscribers, or enrolling contacts in automations.'
Include natural user-facing trigger terms like 'email marketing', 'CRM', 'subscriber management', 'mailing list', or 'campaign automation' 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, list subscriptions, automation enrollment, tasks via ActiveCampaign), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 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 be used by end users. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform reference '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.
The skill provides useful, non-obvious information about ActiveCampaign tool usage through Rube MCP, particularly around capitalization quirks, ID types, and parameter precedence rules. However, it suffers from significant redundancy (pitfalls repeated in multiple places), lacks executable examples showing actual tool invocations with concrete values, and is missing validation/verification steps after operations. Tightening the content by ~40% and adding concrete invocation examples would substantially improve it.
Suggestions
Consolidate pitfalls into a single section rather than repeating them in each workflow AND in the 'Known Pitfalls' section—this would significantly reduce token usage.
Replace pseudocode in 'Common Patterns' with concrete tool invocation examples showing actual parameter values (e.g., a real RUBE_SEARCH_TOOLS call followed by ACTIVE_CAMPAIGN_FIND_CONTACT with specific email).
Add explicit validation steps after key operations—e.g., after tagging a contact, call FIND_CONTACT to verify tags were applied; after subscribing, verify subscription status.
Remove the generic 'When to Use' and 'Limitations' boilerplate at the end, which adds no value beyond what the description already conveys.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose with some redundancy—pitfalls are repeated across individual workflows and then again in the 'Known Pitfalls' summary section. The 'Common Patterns' section uses pseudocode that largely restates what was already covered. However, the parameter details and capitalization notes are genuinely useful non-obvious information. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and important details like capitalization requirements, but lacks executable code examples—the 'Common Patterns' section uses numbered pseudocode steps rather than actual invocation examples with concrete parameter values. The instruction to 'always call RUBE_SEARCH_TOOLS first' is good but the skill never shows what an actual tool call looks like. | 2 / 3 |
Workflow Clarity | Each workflow has a clear tool sequence with prerequisite/required labels, and the contact lookup flow includes a branching path (if found/not found). However, there are no explicit validation checkpoints—no steps to verify that a tag was actually applied, a subscription succeeded, or an automation enrollment took effect. For batch operations, it mentions rate limits but lacks a concrete retry/backoff strategy. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a monolithic document with significant repetition (pitfalls repeated in individual sections and consolidated section). There are no bundle files to reference, but the content could benefit from splitting detailed parameter docs or pitfalls into separate reference files to keep the main skill leaner. | 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
- boisenoise/skills-collections
- Commit
95574f3
- 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.