active-campaign-automation

Automate ActiveCampaign tasks via Rube MCP (Composio). Always search tools first for current schemas.

12.37x

Quality

61%

Does it follow best practices?

Impact

99%

12.37x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/active-campaign-automation/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, lean, and actionable with concrete Rube MCP call templates, but its batch execution workflow lacks a post-execution verification checkpoint and its example arguments stay at placeholder level.

Suggestions

Add a verification step after RUBE_MULTI_EXECUTE_TOOL (e.g. inspect returned statuses/errors and retry failed tools) to satisfy the batch-operation validation requirement.

Replace placeholder arguments ('TOOL_SLUG_FROM_SEARCH', 'your specific ActiveCampaign task') with one fully concrete worked example so guidance is copy-paste ready.

Consolidate the repeated 'search tools first' guidance into a single authoritative callout to trim the remaining redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, with the only over-explanation being the 'search tools first' message repeated across Prerequisites, Tool Discovery, Step 1, and Pitfalls.	4 / 5
Actionability	Concrete RUBE_* call blocks with real field names (queries, session, toolkits, tool_slug) give mostly executable guidance, but arguments remain placeholders like 'TOOL_SLUG_FROM_SEARCH' and 'your specific ActiveCampaign task'.	4 / 5
Workflow Clarity	Setup and Core Workflow are clearly sequenced with a connection-ACTIVE checkpoint and an auth-link feedback loop, but RUBE_MULTI_EXECUTE_TOOL is a batch operation with no post-execution verification step, so the batch-cap pins this at 3.	3 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) and no nested references; it sits slightly above the simple-skill threshold with minor organization gaps rather than clean one-level-deep reference signaling.	4 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 concise and names a distinct product niche, but it lacks a 'Use when...' trigger clause and enumerates no specific ActiveCampaign actions, leaving the what clear but the when implicit.

Suggestions

Add a 'Use when...' clause naming concrete trigger phrases, e.g. 'Use when automating ActiveCampaign contacts, campaigns, tags, or lists'.

List 2-3 concrete actions (e.g. create contacts, manage campaigns, apply tags) to lift specificity above the generic 'tasks'.

Include natural synonyms or phrasings users might say ('ActiveCampaign automation', 'Composio ActiveCampaign') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('ActiveCampaign tasks') and the mechanism ('Rube MCP (Composio)') plus one operational action ('search tools first'), but does not enumerate multiple concrete actions like creating contacts or managing campaigns.	3 / 5
Completeness	It clearly states what the skill does ('Automate ActiveCampaign tasks via Rube MCP'), but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'ActiveCampaign' is a strong natural keyword a user would say, but there is no coverage of synonyms, related phrases, or task variations beyond the product name.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ('ActiveCampaign') plus a specific MCP route ('Rube MCP (Composio)') carves a clear niche with minimal conflict risk, though the thin trigger phrasing leaves minor overlap with other Composio/MCP skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ComposioHQ/awesome-claude-skills
Path: composio-skills/active-campaign-automation/SKILL.md
Commit: be2a406

Reviewed: 7 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.