CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

2.53x
Quality

58%

Does it follow best practices?

Impact

99%

2.53x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/activecampaign-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 a comprehensive reference for ActiveCampaign operations via Rube MCP with good structural organization and useful pitfall documentation. Its main weaknesses are verbosity through repetition (pitfalls restated across sections), lack of executable examples (pseudocode patterns instead of concrete tool calls), and missing validation/error-recovery steps in workflows. The quick reference table is a strong addition.

Suggestions

Consolidate repeated pitfalls (e.g., ID precedence, capitalization rules) into the 'Known Pitfalls' section only, and remove duplicates from individual workflow sections to reduce token usage by ~30%.

Replace pseudocode patterns in 'Common Patterns' with concrete MCP tool call examples showing actual parameter values (e.g., a real RUBE_SEARCH_TOOLS call followed by ACTIVE_CAMPAIGN_FIND_CONTACT with specific email).

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 successfully'.

Consider splitting the detailed per-workflow parameter lists and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table and common patterns.

DimensionReasoningScore

Conciseness

The skill is reasonably structured but verbose for what it conveys. There's significant repetition across workflows (e.g., every workflow repeats the FIND_CONTACT prerequisite pattern, pitfalls about ID precedence are restated multiple times, and the 'Known Pitfalls' section largely duplicates pitfalls already listed in individual workflows). The content could be tightened substantially without losing clarity.

2 / 3

Actionability

The skill provides specific tool names, parameter names, and value formats (e.g., capitalization rules, ISO 8601 dates), which is useful. However, there are no executable code examples — the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual MCP tool call examples with concrete parameters. The instruction to 'always call RUBE_SEARCH_TOOLS first to get current tool schemas' partially undermines the detailed parameter documentation provided.

2 / 3

Workflow Clarity

Workflows are clearly sequenced with prerequisite steps identified, and the tool sequences are well-labeled. However, there are no explicit validation checkpoints or error recovery steps within the workflows. For operations like bulk tagging or automation enrollment, there's no feedback loop (e.g., verify the tag was applied, confirm enrollment succeeded). The 'rate limits' guidance says to implement backoff but doesn't specify how.

2 / 3

Progressive Disclosure

The content is organized with clear sections and a useful quick reference table. However, it's a monolithic document with no references to supporting files, and at ~200+ lines it could benefit from splitting detailed pitfalls or parameter references into separate files. The single external link to Composio docs is appropriate but the skill itself contains everything inline.

2 / 3

Total

8

/

12

Passed

Description

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 strong in specificity and distinctiveness, clearly naming the platform (ActiveCampaign), the integration mechanism (Rube MCP/Composio), and multiple concrete actions. However, it lacks an explicit 'Use when...' clause, which caps completeness, and could benefit from additional natural trigger terms that users might use when requesting CRM or email marketing automation tasks.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ActiveCampaign, CRM contact management, email list operations, or marketing automation workflows.'

Include broader natural trigger terms like 'CRM', 'email marketing', 'mailing list', 'subscriber management' to improve discoverability when users don't mention ActiveCampaign by name.

DimensionReasoningScore

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, list subscriptions, automation enrollment, tasks via Rube MCP/Composio), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied.

2 / 3

Trigger Term Quality

Includes relevant keywords like 'ActiveCampaign', 'contacts', 'tags', 'list subscriptions', 'automation enrollment', and 'tasks', but these are somewhat domain-specific. Missing common user phrasings like 'email marketing', 'CRM', 'mailing list', or 'subscriber' that users might naturally say.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific platform (ActiveCampaign) and integration method (Rube MCP / Composio). Unlikely to conflict with other skills given the narrow, well-defined niche.

3 / 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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.