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.
Install with Tessl CLI
npx tessl i github:boisenoise/skills-collections --skill activecampaign-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates specific capabilities for ActiveCampaign automation and is highly distinctive due to platform-specific naming. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users might commonly say when needing email marketing or CRM functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions ActiveCampaign, email marketing automation, or CRM contact management.'
Include additional natural trigger terms like 'email marketing', 'CRM', 'mailing list', 'campaign', or 'email automation' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'manage contacts, tags, list subscriptions, automation enrollment, and tasks.' These are clear, actionable capabilities within the ActiveCampaign domain. | 3 / 3 |
Completeness | Clearly answers 'what' (manage contacts, tags, subscriptions, etc.) but lacks an explicit 'Use when...' clause. The 'when' is only implied by the capabilities listed, not explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'ActiveCampaign', 'contacts', 'tags', 'subscriptions', 'automation' but misses common variations users might say like 'email marketing', 'CRM', 'mailing list', or 'campaign management'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'ActiveCampaign' and 'Rube MCP (Composio)' as unique identifiers. Unlikely to conflict with other skills due to the specific platform and integration mentioned. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of ActiveCampaign operations with excellent workflow clarity and helpful pitfall documentation. However, it lacks executable code examples (relying on pseudocode patterns), contains some redundancy between sections, and could benefit from splitting detailed content into separate reference files for better progressive disclosure.
Suggestions
Add executable code examples showing actual MCP tool calls with realistic parameters instead of pseudocode numbered lists
Consolidate pitfall information to avoid repetition between individual workflow sections and the 'Known Pitfalls' section
Consider extracting the detailed parameter documentation and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy—the 'Known Pitfalls' section repeats information already covered in individual workflow pitfalls, and some explanations could be tighter. The quick reference table is valuable but the overall document could be trimmed. | 2 / 3 |
Actionability | Provides clear tool names and parameter lists, but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style numbered lists rather than actual API calls or code snippets that could be directly executed. | 2 / 3 |
Workflow Clarity | Each workflow has clear sequencing with explicit tool order, prerequisite steps marked, and detailed pitfalls for error avoidance. The tool sequences are well-structured with [Optional], [Required], and [Prerequisite] annotations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a quick reference table, but it's a monolithic document with no references to external files for detailed API schemas or extended examples. The document is long enough that splitting advanced content would improve navigation. | 2 / 3 |
Total | 9 / 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 | |
- 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.