activecampaign
ActiveCampaign integration. Manage Users, Organizations, Leads, Projects, Goals, Filters. Use when the user wants to interact with ActiveCampaign data.
64
76%
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 ./skills/activecampaign/SKILL.mdQuality
Discovery
75%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 clearly identifies the target platform (ActiveCampaign) and includes an explicit 'Use when' clause, which are strengths. However, the verb 'Manage' is vague and doesn't convey specific actions, and the trigger terms miss common CRM-related vocabulary users might naturally use when requesting ActiveCampaign tasks.
Suggestions
Replace the vague 'Manage' with specific actions like 'Create, update, delete, search, and list' to improve specificity.
Add natural trigger terms users might say, such as 'CRM', 'contacts', 'deals', 'email campaigns', 'automations', or 'pipelines' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ActiveCampaign) and lists entity types (Users, Organizations, Leads, Projects, Goals, Filters), but doesn't describe concrete actions beyond the vague 'Manage'. No specifics like 'create', 'update', 'delete', 'search', or 'sync'. | 2 / 3 |
Completeness | Answers both 'what' (manage Users, Organizations, Leads, Projects, Goals, Filters in ActiveCampaign) and 'when' ('Use when the user wants to interact with ActiveCampaign data'), with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'ActiveCampaign' as a strong trigger term and lists entity names users might mention (Leads, Organizations, etc.), but misses common variations like 'CRM', 'email marketing', 'contacts', 'deals', 'automations', or 'pipelines' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | ActiveCampaign is a specific named platform, making this highly distinctive and unlikely to conflict with other skills. The explicit platform name creates a clear niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity—every step has executable commands and the connection state machine is well-documented with error recovery paths. The main weaknesses are unnecessary introductory content explaining what ActiveCampaign is and a somewhat monolithic structure that could benefit from splitting the action reference table and proxy details into separate files.
Suggestions
Remove the opening paragraph explaining what ActiveCampaign is and the entity overview section—Claude already knows this and it wastes tokens.
Move the popular actions table and proxy request documentation into separate reference files (e.g., ACTIONS.md, PROXY.md) and link to them from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what ActiveCampaign is wastes tokens on information Claude already knows. The entity overview section adds little value. However, the CLI commands and action tables are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, re-check). The overall flow from install → auth → connect → discover → run is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but the popular actions table and proxy request details could be split into separate reference files. For a skill with no bundle files, everything is inline which makes it somewhat long, though the sections are well-signaled. | 2 / 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.
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
- membranedev/application-skills
- Commit
f484c82
- 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.