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.
63
55%
Does it follow best practices?
Impact
Pending
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 identifying the ActiveCampaign platform and listing concrete actions. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from more natural trigger terms that users might say when needing this skill (e.g., 'email marketing', 'CRM', 'subscribers').
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ActiveCampaign, email marketing automation, managing subscribers, or CRM contact management.'
Include additional natural trigger terms users might say, such as 'email marketing', 'CRM', 'subscribers', 'mailing list', or 'marketing automation'.
| 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/Rube MCP), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for 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 automation', or 'Composio'. The terms are somewhat domain-specific but not exhaustive of what users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: ActiveCampaign tasks via Rube MCP (Composio). The combination of the specific platform (ActiveCampaign) and integration method (Rube MCP/Composio) makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid domain-specific knowledge about ActiveCampaign tool names, parameter requirements, and capitalization gotchas that Claude wouldn't know otherwise. However, it suffers from redundancy (pitfalls repeated in sections and consolidated), lacks executable examples, and is entirely monolithic with no progressive disclosure. Adding validation/verification steps after key operations and splitting detailed reference content into separate files would significantly improve it.
Suggestions
Extract the detailed parameter lists and pitfalls for each workflow into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with tool sequences and links to details.
Add explicit validation steps after key operations (e.g., 'After creating a contact, call FIND_CONTACT to verify creation succeeded') to improve workflow reliability.
Remove the duplicated pitfalls—either keep them per-workflow or in the consolidated section, not both.
Replace the plain-text pseudocode in 'Common Patterns' with actual tool invocation examples showing parameter values.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across individual workflow sections and then again in a consolidated 'Known Pitfalls' section. Some parameter listings could be trimmed since the skill itself instructs to call RUBE_SEARCH_TOOLS for current schemas. The 'When to Use' footer adds no value. | 2 / 3 |
Actionability | Tool names and parameter details are specific and concrete, which is good. However, there are no executable code examples—the 'Common Patterns' section uses plain text pseudocode blocks rather than actual tool invocation syntax. The guidance is specific enough to act on but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Each workflow has a clear tool sequence with prerequisite steps labeled. However, there are no explicit validation checkpoints or error-recovery feedback loops. For operations like bulk tagging or automation enrollment (which can fail silently or hit rate limits), the absence of verify-after-action steps and error handling sequences is a gap. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic document with all details inline—parameter lists, pitfalls, patterns, and a quick reference table all in one file. There are no references to separate files for detailed API parameters, examples, or advanced workflows. At ~180 lines, this content would benefit from splitting detailed parameter docs and pitfalls into referenced files. | 1 / 3 |
Total | 7 / 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
636b862
- 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.