activecampaign
ActiveCampaign integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in ActiveCampaign. Routes through Apideck with serviceId "activecampaign".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the platform (ActiveCampaign), the integration mechanism (Apideck CRM unified API), specific supported entities and actions, and explicit trigger conditions. It uses third-person voice correctly and provides enough detail for Claude to distinguish it from other CRM connector skills. The mention of serviceId switching adds useful technical context for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and entities: 'read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in ActiveCampaign.' Also mentions the technical mechanism (Apideck unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both 'what' (ActiveCampaign integration via Apideck CRM unified API for reading, writing, searching CRM entities) and 'when' ('Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in ActiveCampaign'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'ActiveCampaign', 'contacts', 'companies', 'leads', 'opportunities', 'activities', 'pipelines', 'CRM', 'Apideck'. These cover the main entities and platform names a user would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform name 'ActiveCampaign', the specific serviceId, and the Apideck routing mechanism. Unlikely to conflict with other CRM skills unless there are other ActiveCampaign-specific skills. | 3 / 3 |
Total | 12 / 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 is a well-structured connector skill with strong actionability and excellent progressive disclosure to related skills and documentation. Its main weaknesses are verbosity around marketing-style explanations of Apideck's portability benefits and a lack of explicit workflow sequencing with validation checkpoints for the setup and usage process.
Suggestions
Trim the 'Portable across 21 CRM connectors' section to just the code example showing serviceId swapping — remove the marketing paragraph about 'compounding advantage' and 'no code changes needed'.
Condense the 'When to use this skill' section to 1-2 lines; Claude doesn't need detailed activation trigger explanations.
Consider adding a brief numbered workflow (e.g., 1. Configure Vault → 2. Verify coverage → 3. Call unified API → 4. If unsupported, use proxy) to make the operational sequence explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 21 CRM connectors' section is largely marketing copy explaining the 'compounding advantage' of Apideck, and the 'When to use this skill' section over-explains activation triggers. The repeated emphasis on portability across connectors adds little actionable value beyond the first mention. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for listing contacts, a concrete curl command for verifying coverage, and a complete proxy API curl example with all required headers. The serviceId, auth setup, and SDK initialization are all copy-paste ready. | 3 / 3 |
Workflow Clarity | There's an implicit workflow (set up auth → use unified API → verify coverage → fall back to proxy if needed), but it's not explicitly sequenced with numbered steps or validation checkpoints. The coverage verification step is presented as a standalone section rather than integrated into a clear workflow with error handling feedback loops. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to SDK skills, best practices, connector coverage, OpenAPI specs, and official docs. The 'See also' section provides clear navigation without nesting references multiple levels deep. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- 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.