Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.
81
72%
Does it follow best practices?
Impact
100%
1.88xAverage score across 3 eval scenarios
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 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
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear workflows and specific parameter guidance. The main weakness is verbosity—pitfalls and capitalization rules are repeated across sections, and the document could be more concise by consolidating common information and potentially splitting detailed workflows into separate reference files.
Suggestions
Consolidate repeated pitfall information (action capitalization, ID types) into a single 'Common Pitfalls' section and remove duplicates from individual workflows
Consider moving detailed workflow sections to a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the quick reference table and setup instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy—pitfalls are repeated across sections (e.g., action capitalization mentioned multiple times), and some explanations could be tighter. The 'Known Pitfalls' section largely duplicates information already covered in individual workflow sections. | 2 / 3 |
Actionability | Provides concrete tool sequences, specific parameter names with exact values (e.g., 'Add' vs 'subscribe'), and clear step-by-step workflows. The quick reference table and common patterns give copy-paste ready guidance for each operation. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered sequences with explicit prerequisites marked. The tool sequences distinguish between optional and required steps, and the common patterns section provides clear decision flows for contact lookup and ID resolution. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed workflow sections into separate files. The quick reference table at the end is helpful, but the document is lengthy for a SKILL.md overview. | 2 / 3 |
Total | 10 / 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 | |
ae2cadd
Table of Contents
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.