active-campaign-automation

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

12.37x

Quality

53%

Does it follow best practices?

Impact

99%

12.37x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/active-campaign-automation/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to effectively guide skill selection. It names the platform (ActiveCampaign) but fails to specify concrete actions or provide explicit trigger conditions. The implementation detail about searching tools first doesn't help Claude decide when to use this skill.

Suggestions

Add specific capabilities like 'create contacts, manage email campaigns, set up automations, track engagement metrics'

Add a 'Use when...' clause with trigger terms like 'ActiveCampaign', 'email marketing automation', 'contact management', 'campaign analytics'

Remove or relocate the procedural guidance ('Always search tools first') to the skill body, keeping the description focused on capabilities and triggers

Dimension	Reasoning	Score
Specificity	The description says 'Automate ActiveCampaign tasks' which is vague - it doesn't specify what tasks (e.g., create contacts, send campaigns, manage lists). 'Always search tools first' is procedural guidance, not a capability description.	1 / 3
Completeness	Describes a vague 'what' (automate tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance. The second sentence is implementation detail, not usage guidance.	1 / 3
Trigger Term Quality	Includes 'ActiveCampaign' which is a specific product name users would mention, but lacks natural variations like 'email marketing', 'contacts', 'campaigns', 'automation workflows', or 'CRM' that users might say when needing this skill.	2 / 3
Distinctiveness Conflict Risk	'ActiveCampaign' provides some distinctiveness as a specific platform, but 'automate tasks' is generic enough to potentially conflict with other automation or CRM-related skills. The Rube MCP/Composio reference adds some specificity.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

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

This is a well-structured skill that efficiently teaches ActiveCampaign automation via Rube MCP. It excels at workflow clarity with explicit validation steps and progressive disclosure with logical section organization. The main weakness is that tool call examples use placeholder syntax rather than fully concrete, executable examples with realistic field values.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual ActiveCampaign fields (e.g., creating a contact with email, firstName, lastName)

Add one complete end-to-end example showing a real workflow (e.g., 'Add a contact to a list') with actual tool slugs and arguments that would be returned from RUBE_SEARCH_TOOLS

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what ActiveCampaign or Composio are. Every section provides actionable information without padding or unnecessary context.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but uses pseudocode-style blocks rather than actual executable code. The argument placeholders like '/* schema-compliant args */' reduce copy-paste readiness.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows') and the Known Pitfalls section addresses error prevention.	3 / 3
Progressive Disclosure	Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table aids navigation.	3 / 3
	Total	11 / 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: ComposioHQ/awesome-claude-skills
Commit: 2790447

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