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.

2.53x

Quality

58%

Does it follow best practices?

Impact

99%

2.53x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/activecampaign-automation/SKILL.md

Quality

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 reasonably strong in specificity and distinctiveness, clearly identifying the ActiveCampaign platform and listing concrete actions. However, it lacks an explicit 'Use when...' clause, which weakens completeness, and could benefit from more natural trigger terms that users might actually say (e.g., 'email marketing', 'CRM', 'subscribers').

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ActiveCampaign, email marketing automation, CRM contacts, or subscriber management.'

Include additional natural trigger terms users might say, such as 'email marketing', 'CRM', '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/Rube MCP), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2.	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', 'campaign automation', or 'Composio'. The terms are somewhat domain-specific but not exhaustive of what users might naturally say.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche: specifically targets ActiveCampaign via Rube MCP (Composio), which is unlikely to conflict with other skills. The combination of platform name and integration method makes it clearly distinguishable.	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 coverage of ActiveCampaign operations with clear tool names, parameter details, and pitfall warnings. However, it suffers from redundancy (pitfalls repeated in individual sections and a summary section), lacks executable examples with actual tool call syntax, and misses validation/verification steps in workflows. The content would benefit from being more concise and splitting detailed reference material into separate files.

Suggestions

Consolidate pitfalls into a single section or keep them only in individual workflows to reduce redundancy and improve conciseness.

Add at least one fully executable tool call example (showing exact parameter JSON) rather than relying on pseudocode-style numbered lists in Common Patterns.

Add explicit validation steps to workflows—e.g., 'Verify the response contains the expected contact ID before proceeding' or 'Check response status to confirm tag was applied.'

Move detailed per-tool parameter listings to a separate REFERENCE.md file, keeping SKILL.md as a leaner overview with the quick reference table and workflow sequences.

Dimension	Reasoning	Score
Conciseness	The skill is fairly detailed and well-organized, but includes some redundancy—pitfalls are repeated across individual workflows and then again in the 'Known Pitfalls' section. Some parameter listings could be trimmed since the skill itself says to always call RUBE_SEARCH_TOOLS first for current schemas, making detailed parameter docs partially redundant.	2 / 3
Actionability	Tool names and parameter details are concrete and specific, but the 'Common Patterns' section uses pseudocode-style numbered lists rather than executable examples. There are no actual code snippets or copy-paste-ready tool invocations showing exact parameter formats, which would make this more actionable.	2 / 3
Workflow Clarity	Each workflow has a clear tool sequence with prerequisite steps, which is good. However, there are no explicit validation checkpoints or error-handling feedback loops—e.g., no guidance on what to do if FIND_CONTACT returns unexpected results, or how to verify that a tag was successfully applied. For batch operations like 'Bulk Contact Tagging,' there's no verification step.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and a quick reference table, but it's quite long (~200 lines) with all content inline. The detailed per-workflow pitfalls and parameter lists could be split into a reference file, with the main SKILL.md serving as a leaner overview pointing to details.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 days ago

Table of Contents

Discovery Implementation Validation

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.