activecampaign
ActiveCampaign integration. Manage Users, Organizations, Leads, Projects, Goals, Filters. Use when the user wants to interact with ActiveCampaign data.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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, it relies on the vague verb 'Manage' rather than listing specific actions (create, update, delete, search), and it misses common synonyms or related terms users might use when referring to CRM functionality.
Suggestions
Replace the vague 'Manage' with specific actions like 'Create, update, delete, search, and list' to improve specificity.
Add common related trigger terms users might say, such as 'CRM', 'contacts', 'deals', 'email marketing', 'automation', or 'pipeline' to improve trigger term 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'. It doesn't specify what operations can be performed (e.g., create, update, delete, search). | 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 like 'Leads', 'Organizations', 'Projects', which users might mention. However, it misses common action-oriented terms users would say like 'CRM', 'contacts', 'deals', 'email marketing', 'automation', or 'pipeline'. | 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
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional integration skill with strong actionability — every operation has a concrete, executable CLI command. Its main weaknesses are some unnecessary introductory context (explaining what ActiveCampaign is), a bulky inline actions table that could be externalized, and a workflow that lacks explicit validation checkpoints when running actions or handling errors.
Suggestions
Remove the opening paragraph explaining what ActiveCampaign is — Claude already knows this. Start directly with the entity overview or working instructions.
Move the popular actions table to a separate ACTIONS_REFERENCE.md file and link to it, keeping the SKILL.md leaner.
Add explicit error handling guidance for `membrane action run` — what to do if the action fails, how to inspect errors, and retry patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what ActiveCampaign is ('marketing automation platform used by small to mid-sized businesses...') is unnecessary context Claude already knows. The entity overview section is somewhat useful but could be tighter. The popular actions table is large but arguably useful as a reference. Overall mostly efficient with some fat. | 2 / 3 |
Actionability | Provides fully executable CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with input parameters. Commands are copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | The workflow is reasonably sequenced (install → authenticate → connect → search/create actions → run), and the action creation flow includes polling with state checking. However, there's no explicit validation or error recovery for running actions, and the overall flow isn't presented as a numbered sequence with checkpoints — it's spread across sections. | 2 / 3 |
Progressive Disclosure | Content is structured with clear headers and sections, but the large popular actions table (20 rows) could be in a separate reference file. The skill is somewhat monolithic — everything is inline with only an external link to official docs. No references to supplementary files for advanced usage or detailed schemas. | 2 / 3 |
Total | 9 / 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
56d7336
- 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.