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.
66
58%
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 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 structural organization with clear tool names, parameter specifications, and important pitfalls (like action capitalization differences). However, it lacks executable examples with concrete payloads, has redundant pitfall documentation, and is missing validation/verification steps in its workflows. The content would benefit from being more concise while adding concrete tool call examples and explicit verification checkpoints.
Suggestions
Add concrete, executable MCP tool call examples with actual parameter payloads (e.g., a full RUBE_SEARCH_TOOLS call followed by ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG with real-looking data) instead of pseudocode numbered lists.
Add explicit validation/verification steps after each tool call in workflows (e.g., 'Verify the response contains the contact ID before proceeding' or 'Check response status to confirm tag was applied').
Consolidate the per-workflow pitfalls into the single 'Known Pitfalls' section to reduce redundancy and improve conciseness.
Remove the generic 'When to Use' and 'Limitations' boilerplate sections at the end, as they add no skill-specific value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some redundancy—pitfalls are repeated across individual workflows and then again in a consolidated 'Known Pitfalls' section. The boilerplate 'When to Use' and 'Limitations' sections at the end add little value. Some parameter documentation could be more compact. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and expected values (e.g., capitalization of action values, ISO 8601 format), which is helpful. 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. Key details like how to discover list IDs or automation IDs are punted to 'use the UI.' | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with prerequisite/required labels, and the setup section has a clear 4-step verification flow. However, validation checkpoints are largely missing—there's no explicit 'verify the contact was created successfully' or 'check the tag was applied' step. For bulk operations, the guidance to 'batch with reasonable delays' is vague with no error recovery loop for 429 responses. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a quick reference table, but it's monolithic—all ~200 lines are in a single file with no references to external files for detailed API schemas, examples, or advanced patterns. The instruction to 'always call RUBE_SEARCH_TOOLS first to get current tool schemas' partially mitigates this, but the document itself could benefit from splitting detailed parameter docs into a reference file. | 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
431bfad
- 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.