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:Lingjie-chen/MT5 --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 actually say when needing email marketing or CRM automation help.
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 users might say: 'email marketing', 'CRM', 'mailing lists', 'email campaigns', 'subscriber management'.
| 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 through the capability listing, 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 automation'. | 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 well-structured workflows and helpful pitfall documentation. The main weaknesses are the lack of executable code examples (relying on pseudocode patterns instead) and some redundancy between the per-workflow pitfalls and the consolidated 'Known Pitfalls' section. The workflow clarity is strong with clear sequencing and prerequisite markers.
Suggestions
Replace pseudocode patterns in 'Common Patterns' section with actual executable tool call examples showing the exact parameters and expected response structure
Consolidate pitfall information—either keep detailed pitfalls per workflow OR have a single Known Pitfalls section, not both with overlapping content
Add a concrete example showing a complete workflow with actual parameter values and sample response parsing
| 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 duplicates parameter info from above. | 2 / 3 |
Actionability | Provides clear tool sequences 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 | Workflows are clearly sequenced with explicit prerequisite steps, tool sequences are numbered with [Optional], [Required], and [Prerequisite] markers, and pitfalls sections provide error recovery guidance. The multi-step processes are well-structured. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a useful quick reference table, but it's a monolithic document that could benefit from splitting detailed workflow documentation into separate files. The external toolkit docs link is good but internal structure could be improved. | 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.