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 does a good job listing specific capabilities and naming the target platform (ActiveCampaign) and integration method, making it distinctive. However, it lacks an explicit 'Use when...' clause, which caps completeness, and the trigger terms lean toward technical/platform-specific language rather than natural user phrasing like 'email marketing' or 'CRM'.
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 such as 'email marketing', 'CRM', 'subscriber management', and 'mailing list' 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, etc. 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', or 'campaign'. The term 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to ActiveCampaign via a specific integration (Rube MCP/Composio), making it highly distinctive and unlikely to conflict with other skills. | 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 coverage of ActiveCampaign operations via Rube MCP with clear tool names, parameter specifications, and useful pitfall documentation. However, it suffers from repetition across workflow sections (especially pitfalls and ID type notes), lacks executable example tool calls with concrete payloads, and misses validation/verification steps after operations. The content would benefit from deduplication, concrete examples, and splitting detailed reference material into separate files.
Suggestions
Add concrete, executable tool call examples with sample parameters (e.g., show an actual RUBE_SEARCH_TOOLS call and a complete ACTIVE_CAMPAIGN_CREATE_CONTACT invocation with realistic values) rather than pseudocode patterns.
Deduplicate pitfalls: consolidate the repeated ID type, capitalization, and precedence rules into the 'Known Pitfalls' section only, and remove them from individual workflow sections to reduce token usage by ~25%.
Add explicit validation steps after key operations (e.g., 'After creating a contact, verify by calling FIND_CONTACT with the email to confirm creation and retrieve the contact ID').
Consider splitting detailed parameter documentation and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table and workflow sequences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but verbose for what it conveys. There's significant repetition across workflows (e.g., every workflow repeats the FIND_CONTACT prerequisite pattern, pitfalls sections repeat ID type information). The 'Known Pitfalls' section at the bottom duplicates pitfalls already stated in individual workflow sections. The content could be tightened by ~30-40% without losing information. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and value formats (e.g., capitalization rules, ISO 8601 dates), which is useful. However, there are no executable code examples — the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual MCP tool call examples with concrete payloads. Including example tool invocations with sample parameters would make this significantly more actionable. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with prerequisite steps and tool ordering. However, there are no explicit validation checkpoints or error recovery steps. For example, after creating a contact or managing tags, there's no 'verify the operation succeeded' step. The bulk tagging pattern mentions rate limits but doesn't specify a feedback loop for handling failures. The setup section does include a validation step (confirm ACTIVE status), which is good. | 2 / 3 |
Progressive Disclosure | The content is a monolithic single file with no bundle files for reference. The quick reference table at the end is helpful, but the detailed pitfalls and parameter documentation for each workflow could be split into separate reference files. For a skill of this length (~180+ lines), the inline detail is excessive for an overview document. The external link to Composio docs is appropriate but there are no internal file references for deeper content. | 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
d065ead
- 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.