ActiveCampaign integration. Manage Users, Organizations, Leads, Projects, Goals, Filters. Use when the user wants to interact with ActiveCampaign data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill activecampaign75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 adequately identifies the integration target and includes an explicit 'Use when' clause, which is good. However, it lacks specific action verbs beyond 'Manage' and misses common trigger terms users might naturally use when referring to CRM or marketing automation tasks.
Suggestions
Replace 'Manage' with specific actions like 'Create, update, delete, and sync Users, Organizations, Leads...'
Add common trigger terms users might say: 'CRM', 'contacts', 'email marketing', 'marketing automation', 'AC'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ActiveCampaign) and lists entity types (Users, Organizations, Leads, Projects, Goals, Filters), but 'Manage' is vague - doesn't specify concrete actions like create, update, delete, or sync. | 2 / 3 |
Completeness | Answers both what ('Manage Users, Organizations, Leads, Projects, Goals, Filters') 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 key trigger term and entity names, but misses common variations users might say like 'CRM', 'contacts', 'email marketing', 'automation', or 'campaigns'. | 2 / 3 |
Distinctiveness Conflict Risk | ActiveCampaign is specific, but 'Manage Users, Organizations, Leads' could overlap with other CRM integrations like Salesforce or HubSpot skills if present. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI guidance for ActiveCampaign integration with good structure and executable examples. However, it wastes tokens explaining what ActiveCampaign is and listing entities without context. The workflow lacks validation checkpoints for confirming successful connections or action execution.
Suggestions
Remove the opening paragraph explaining what ActiveCampaign is - Claude already knows this
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failures like authentication timeout or invalid credentials
Remove or condense the 'ActiveCampaign Overview' bullet list which provides no actionable information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what ActiveCampaign is wastes tokens on information Claude already knows. The overview section listing entities without context adds little value. However, the CLI commands and action tables are appropriately concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. The action table gives concrete action keys, and proxy request examples include all common flags with descriptions. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Setup steps are sequenced but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. The headless environment flow mentions completion but doesn't specify error handling. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections progressing from setup to usage to best practices. The skill is appropriately self-contained without needing external references, and the action table provides quick reference without overwhelming detail. | 3 / 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 | |
Table of Contents
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.