activeprospect
ActiveProspect integration. Manage data, records, and automate workflows. Use when the user wants to interact with ActiveProspect data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill activeprospect72
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 correctly includes both 'what' and 'when' components with an explicit trigger clause, which is good structure. However, it suffers from vague action verbs ('manage', 'automate') and lacks specific ActiveProspect product terminology (LeadConduit, TrustedForm, leads) that would help Claude distinguish this skill and match user requests more accurately.
Suggestions
Replace vague verbs with specific actions like 'create and query leads', 'configure LeadConduit flows', 'validate with TrustedForm', or 'manage lead routing rules'.
Add natural trigger terms users would say: 'leads', 'LeadConduit', 'TrustedForm', 'lead validation', 'consent verification', or specific ActiveProspect product names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ActiveProspect) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - 'manage' and 'automate' are vague verbs without specifics like 'create leads', 'configure flows', or 'query records'. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with ActiveProspect data) with an explicit trigger clause, though both parts could be more detailed. | 3 / 3 |
Trigger Term Quality | Includes 'ActiveProspect' as a key trigger term and generic terms like 'data' and 'workflows', but lacks natural variations users might say such as 'leads', 'LeadConduit', 'TrustedForm', or specific product features. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic language that could overlap with many CRM or automation skills. The 'ActiveProspect' brand name provides some distinction, but the generic verbs create potential conflict with similar integration skills. | 2 / 3 |
Total | 9 / 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 skill provides solid, actionable CLI commands for ActiveProspect integration via Membrane, with good coverage of common operations and proxy requests. However, it wastes tokens on introductory context Claude doesn't need and a verbose action overview that duplicates discoverable information. The workflow lacks explicit validation steps for confirming successful operations.
Suggestions
Remove the introductory paragraph explaining what ActiveProspect is and who uses it - Claude already knows this context
Move or remove the detailed 'ActiveProspect Overview' entity listing since actions are discoverable via `membrane action list`
Add validation steps after connection creation (e.g., 'Verify connection: `membrane connection list --json` and confirm status is active')
Add error handling guidance for common failures like authentication timeout or invalid connection IDs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., describing what ActiveProspect is and who uses it - Claude can look this up). The overview section listing all entities/actions is verbose and could be trimmed since actions are discoverable via CLI. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including JSON parameter passing, proxy requests with flag documentation, and concrete examples for connection setup, action discovery, and running actions. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are clear, but lacks validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the lengthy entity/action overview could be moved to a separate reference file. Links to external docs exist but no internal file references for advanced topics. | 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 | |
- 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.