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

—

Does it follow best practices?

Impact

99%

2.53x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A thorough, actionable skill body with concrete tool/parameter guidance and clearly sequenced workflows. Its weaknesses are redundancy between per-workflow pitfalls and the consolidated pitfalls section, and the absence of validation feedback loops for batch/destructive operations.

Suggestions

De-duplicate the pitfalls: keep them only in the per-workflow sections or only in 'Known Pitfalls' and cross-reference, rather than stating them twice.

Add explicit verification checkpoints after batch/destructive operations (e.g., re-query the contact to confirm a tag/subscription changed) to support a feedback loop.

Consider moving the detailed per-workflow parameter lists into one-level-deep reference files, leaving SKILL.md as a tighter overview with the Quick Reference table.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but content is repeated — per-workflow 'Pitfalls' reappear in 'Known Pitfalls' (action capitalization, ID types, automations) and the 'Quick Reference' table restates params — so it could be tightened. Not score 3 because of this redundancy; not score 1 because nothing explains concepts Claude already knows.	2 / 3
Actionability	Provides concrete, copy-paste-ready guidance: exact tool slugs, required/optional parameters, types, and format examples (e.g., duedate '2025-01-15T14:30:00-05:00', capitalized 'Add'/'Remove' vs lowercase 'subscribe'). Matches the score-3 anchor of specific, actionable instruction.	3 / 3
Workflow Clarity	Tool sequences are clearly ordered with [Prerequisite]/[Required]/[Optional] markers and Setup includes a status checkpoint, but batch/destructive operations (bulk tagging, unsubscribe, tag removal) lack explicit validate-then-verify feedback loops, which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Well-organized into clear sections with a Quick Reference overview table, but it is a single monolithic file (~200 lines) with all per-workflow parameter detail inline; content that could be split into one-level-deep reference files is not. No bundle files are present to support deeper references.	2 / 3
	Total	9 / 12 Passed

Description

82%

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

A specific, well-scoped description that enumerates concrete capabilities and uses natural domain terms. Its main gap is the absence of an explicit 'Use when...' trigger clause, which leaves the usage timing implied rather than stated.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when managing ActiveCampaign contacts, tags, list subscriptions, automation enrollment, or contact tasks.'

Consider adding common phrasing variations users might say ('add a contact to a list', 'tag a contact', 'enroll a contact in an automation') to strengthen trigger matching.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'manage contacts, tags, list subscriptions, automation enrollment, and tasks' — matching the score-3 anchor of enumerating several specific capabilities rather than vague language.	3 / 3
Completeness	Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2; the when is only implied by the domain terms.	2 / 3
Trigger Term Quality	Surfaces natural domain terms a user would say (ActiveCampaign, contacts, tags, list subscriptions, automation enrollment, tasks); these are the actual phrases used in requests, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche — ActiveCampaign via Rube MCP (Composio) — with distinct triggers unlikely to overlap with other skills.	3 / 3
	Total	11 / 12 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: davepoon/buildwithclaude
Commit: 366e45b

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