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.
45
47%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/activecampaign-automation/SKILL.mdQuality
Discovery
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 reasonably specific about what it does and names a clear platform (ActiveCampaign via Rube MCP/Composio), making it distinctive. However, it lacks an explicit 'Use when...' clause, which caps completeness, and the trigger terms lean toward technical jargon rather than natural user language. Adding explicit trigger guidance and more user-facing keywords would strengthen it.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ActiveCampaign, email marketing automation, CRM contacts, or subscriber management.'
Include more natural user-facing trigger terms such as 'email marketing', 'CRM', 'subscriber', 'mailing list', or 'campaign automation' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
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, subscriptions, etc. via ActiveCampaign), 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 misses common user variations like 'email marketing', 'CRM', 'subscriber', 'campaign automation', or 'Composio'. 'Rube MCP' is technical jargon most users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'ActiveCampaign' and 'Rube MCP (Composio)'. This is a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill covers ActiveCampaign operations comprehensively with good tool naming and parameter documentation, but suffers from significant verbosity and repetition. Information is duplicated across per-workflow pitfalls and the consolidated 'Known Pitfalls' section. The lack of executable examples, validation checkpoints, and progressive disclosure into separate reference files makes this a lengthy but only moderately useful skill document.
Suggestions
Consolidate pitfalls into a single section and remove duplicates from individual workflows, or vice versa—pick one location for each piece of information.
Add concrete tool invocation examples showing actual parameter values and expected response structures rather than pseudocode numbered lists.
Split detailed parameter references and the pitfalls catalog into separate bundle files (e.g., PARAMETERS.md, PITFALLS.md) and reference them from the main skill.
Add explicit validation steps after key operations (e.g., verify contact creation by searching for the newly created contact before proceeding to tag/subscribe operations).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines, with significant repetition across sections. The 'Known Pitfalls' section largely duplicates pitfalls already listed under each workflow. The 'Common Patterns' section restates what's already covered. The quick reference table is helpful but the overall document could be cut by 40-50% without losing information. It also explains things Claude would know (e.g., what ISO 8601 format is, what rate limiting means). | 1 / 3 |
Actionability | Tool names and parameter lists are concrete and specific, which is good. However, there are no executable code examples—the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual tool invocation syntax. The skill also lacks concrete example payloads or response structures that would make it copy-paste ready. | 2 / 3 |
Workflow Clarity | Each workflow has a clear tool sequence with prerequisite/required labels, which is good. However, there are no explicit validation checkpoints or error recovery steps. For example, after creating a contact, there's no step to verify creation succeeded. The bulk tagging pattern mentions 'reasonable delays' but gives no concrete guidance on handling failures or 429 responses beyond 'implement backoff.' | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files. All detailed parameter lists, pitfalls, and patterns are inline. With no bundle files, the content that could be split (e.g., detailed parameter references, pitfall catalog, quick reference) is all crammed into one long document, making it hard to navigate and consuming excessive context window. | 1 / 3 |
Total | 6 / 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.
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
- sickn33/antigravity-awesome-skills
- Commit
b3869ba
- 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.