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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

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.

Highly actionable content with exact tool names, parameters, and value formats, plus clear sequenced workflows, but it is held back by redundant pitfalls/quick-reference duplication and missing validation feedback loops for batch and destructive operations.

Suggestions

Remove the consolidated 'Known Pitfalls' section (or the per-workflow 'Pitfalls') to eliminate duplication, and consider dropping the 'Quick Reference' table since it rehashes params already listed in each workflow.

Add explicit post-operation validation/feedback steps for batch and destructive operations (e.g., re-query the contact to confirm a tag or subscription status changed before proceeding).

Move the detailed per-workflow parameter and pitfall listings into reference files (e.g., WORKFLOWS.md) and keep SKILL.md as a concise overview with one-level-deep links to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	It avoids over-explaining concepts Claude knows, but pitfalls are duplicated per-workflow and again consolidated under 'Known Pitfalls', and the 'Quick Reference' table rehashes already-stated params, so it could be tightened.	2 / 3
Actionability	It gives exact tool slugs, parameter names, and value formats (e.g., 'Add'/'Remove' capitalization, ISO 8601 example '2025-01-15T14:30:00-05:00', numeric-string IDs) — concrete, copy-paste-ready guidance even without code.	3 / 3
Workflow Clarity	Sequences are clear with FIND_CONTACT prerequisites and a Setup validation step, but batch/destructive operations (bulk tagging, unsubscribe) lack post-operation validation or feedback loops, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a single monolithic SKILL.md over 50 lines with all per-workflow detail inline and no external references or deeper files, so it is not a 3.	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, distinctive description that names concrete ActiveCampaign operations and natural trigger terms, but it lacks an explicit 'when to use' trigger clause, capping completeness at 2.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants to manage ActiveCampaign contacts, tags, list subscriptions, or automation enrollment') to fully answer both what and when.

Consider trimming the implementation framing ('via Rube MCP (Composio)', 'Always search tools first for current schemas') from the description so it stays focused on user-facing capability triggers.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions — 'manage contacts, tags, list subscriptions, automation enrollment, and tasks' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The WHAT is explicit (the enumerated ActiveCampaign operations), but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural user-facing terms (contacts, tags, list subscriptions, automation, tasks) are well covered; only the 'Rube MCP (Composio)' framing is implementation jargon, but the capability keywords users would say are present.	3 / 3
Distinctiveness Conflict Risk	It names the specific product 'ActiveCampaign', giving it a clear niche with triggers unlikely to conflict 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: boisenoise/skills-collections
Commit: f36337d

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.