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.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-activecampaign-automation/SKILL.md

Quality

Content

61%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.

A well-structured, highly actionable reference for the Rube MCP ActiveCampaign toolset, rich in genuine gotchas Claude could not infer (capitalization rules, ID string formats, response nesting). Weaknesses are duplication between workflow-level and global pitfalls sections, boilerplate "When to Use"/"Limitations" text, and missing verification steps for the bulk/batch tagging pattern.

Suggestions

Add validation steps to the bulk tagging pattern (e.g., verify each tag was applied in the response, handle and retry on 429 with explicit backoff intervals) and remove duplicate content between per-workflow Pitfalls and the Known Pitfalls section.

Cut the boilerplate "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview") and generic Limitations lines that add no skill-specific information.

Move per-tool parameter tables and pitfall detail into a references/ file (e.g., references/tools.md), keeping SKILL.md to the workflows, setup, and Quick Reference table.

Dimension	Reasoning	Score
Conciseness	The body is dense with non-obvious, valuable details (capitalization quirks, "Response data may be nested under `data` or `data.data`"), but pitfalls are duplicated between each workflow's "Pitfalls" block and the "Known Pitfalls" section, and sections like "This skill is applicable to execute the workflow or actions described in the overview" are empty boilerplate — mostly efficient with clear trim opportunities (anchor 3).	3 / 5
Actionability	Concrete, executable guidance throughout: exact tool slugs ("ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG"), exact parameter names, exact action values ("'Add' or 'Remove' (not lowercase)", "'subscribe' or 'unsubscribe'"), and a worked ISO 8601 example. Falls short of anchor 5 only because there are no example call payloads and ID resolution (list IDs, automation IDs, assignee) is deferred to the ActiveCampaign UI.	4 / 5
Workflow Clarity	Sequences are clear — numbered tool orders with [Prerequisite]/[Required] labels and a setup verification step ("Confirm connection status shows ACTIVE before running any workflows") — but the "Bulk Contact Tagging" pattern ("For each contact, call ACTIVE_CAMPAIGN_MANAGE_CONTACT_TAG"; "Batch with reasonable delays") is a batch operation with no verification or outcome-checking steps, capping workflow clarity at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	A single, well-organized file with clear section headers, per-workflow structure, and a "Quick Reference" table for navigation; no bundle files exist and no references are made, so nothing is buried or nested. Anchor 4 rather than 5 because ~210 lines of per-tool parameter and pitfall detail could be split into reference files to keep SKILL.md a leaner overview.	4 / 5
	Total	14 / 20 Passed

Description

70%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.

A specific, well-scoped description that names the product domain and five concrete capability areas with strong distinctiveness. Its main weakness is the missing "Use when..." trigger clause, which caps completeness, and slightly generic verbs that keep specificity just short of comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to manage ActiveCampaign contacts, tags, list subscriptions, automations, or tasks."

Include natural synonyms users might say such as "CRM", "email marketing", "enroll contact in automation", or "unsubscribe" to broaden trigger coverage.

Replace generic verbs ("Automate ... tasks", "manage") with concrete ones ("create and find contacts, add/remove tags, subscribe contacts to lists, enroll contacts in automations, create follow-up tasks").

Dimension	Reasoning	Score
Specificity	Lists several concrete action areas — "manage contacts, tags, list subscriptions, automation enrollment, and tasks" — but the verbs are generic ("Automate ... tasks", "manage"), so it matches anchor 4 (several specific actions, minor gaps) rather than anchor 5's fully concrete action list.	4 / 5
Completeness	The "what" is clear ("Automate ActiveCampaign tasks ... manage contacts, tags, list subscriptions, automation enrollment, and tasks"), but there is no "Use when..." clause or equivalent trigger guidance; "Always search tools first for current schemas" is procedural, not a when-to-use trigger, capping this at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"ActiveCampaign", "contacts", "tags", "list subscriptions", "automation enrollment" are terms users would naturally say, but "Rube MCP (Composio)" is technical jargon and natural synonyms like "CRM", "email marketing", or "enroll contact" are absent — good coverage with a few terms missing (anchor 4).	4 / 5
Distinctiveness Conflict Risk	"ActiveCampaign" names a specific commercial product with a distinct operation set (tags, list subscriptions, automation enrollment), giving a clear niche with minimal overlap against generic CRM or document skills.	5 / 5
	Total	16 / 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: boisenoise/skills-collections
Path: skills/antigravity-activecampaign-automation/SKILL.md
Commit: 7390864

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