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.
45
47%
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/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 fairly 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 could be improved by including more natural user-facing keywords rather than technical integration names.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ActiveCampaign contacts, email lists, CRM automation, or subscriber management.'
Include more natural trigger terms users might say, such as 'CRM', 'email marketing', '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), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'ActiveCampaign', 'contacts', 'tags', 'list subscriptions', 'automation enrollment', and 'tasks', but misses common user variations (e.g., 'CRM', 'email marketing', 'subscriber', 'mailing list'). '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 Rube MCP/Composio, which is a very specific niche. It is unlikely to conflict with other skills unless there are multiple ActiveCampaign integrations. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill covers ActiveCampaign operations comprehensively but suffers from significant verbosity and redundancy—pitfalls and parameter details are repeated multiple times, and much of the content duplicates what RUBE_SEARCH_TOOLS would provide. The workflows are reasonably well-structured but lack validation checkpoints and error recovery steps. The entire content is crammed into one file with no progressive disclosure, making it a poor use of the context window.
Suggestions
Reduce content by 50-60%: remove duplicated pitfalls (consolidate into one section), trim parameter lists to only non-obvious gotchas since RUBE_SEARCH_TOOLS provides current schemas, and cut the boilerplate 'When to Use' and 'Limitations' sections.
Add explicit validation steps to workflows: after each tool call, specify how to verify success (e.g., 'Confirm response contains contact ID before proceeding') and what to do on failure.
Split detailed parameter references and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table and links to details.
Replace pseudocode patterns in 'Common Patterns' with actual tool invocation examples showing the exact MCP call format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines, with significant redundancy. Pitfalls are repeated across sections (e.g., action capitalization appears in each workflow AND in a dedicated 'Known Pitfalls' section). Parameter lists duplicate what RUBE_SEARCH_TOOLS would return. The instruction to always search tools first makes much of this parameter documentation redundant. | 1 / 3 |
Actionability | Tool names and parameter names are concrete and specific, and the tool sequences are clear. However, there are no executable code examples—the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual tool invocation syntax. Key details like how to actually call these tools via Rube MCP (exact invocation format) are missing. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with prerequisite/required labels, and the contact lookup flow pattern is sensible. However, there are no explicit validation checkpoints or error recovery loops—no guidance on what to do if a tool call fails, how to verify success, or feedback loops for batch operations despite mentioning rate limits and bulk tagging. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no bundle files or external references. All parameter details, pitfalls, and patterns are inlined in a single file. The parameter lists and pitfalls for each workflow could easily be split into separate reference files, with SKILL.md serving as a concise overview with links. | 1 / 3 |
Total | 6 / 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
- sickn33/antigravity-awesome-skills
- Commit
76aea27
- 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.