activeprospect
ActiveProspect integration. Manage data, records, and automate workflows. Use when the user wants to interact with ActiveProspect data.
53
60%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/activeprospect/SKILL.mdQuality
Discovery
57%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 relies heavily on the 'ActiveProspect' brand name for distinctiveness but fails to describe any concrete capabilities specific to the platform. The actions are generic boilerplate ('manage data, records, and automate workflows') that could apply to virtually any integration. While it has proper structural completeness with a 'Use when' clause, the lack of specificity significantly undermines its usefulness for skill selection.
Suggestions
Replace generic actions with ActiveProspect-specific capabilities, e.g., 'Configure LeadConduit flows, manage TrustedForm certificates, set up lead routing rules, and monitor delivery reports.'
Add product-specific trigger terms users would naturally say, such as 'LeadConduit', 'TrustedForm', 'lead distribution', 'consent verification', 'lead buying/selling'.
Make the 'Use when' clause more specific, e.g., 'Use when the user mentions ActiveProspect, LeadConduit, TrustedForm, lead flows, or consent-based marketing automation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions listed ('manage data, records, and automate workflows') are extremely vague and generic. There are no concrete, specific actions like 'create leads', 'configure TrustedForm certificates', or 'set up LeadConduit flows' that would indicate what this skill actually does with ActiveProspect. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with ActiveProspect data) with an explicit 'Use when' clause. While the content is vague, the structural completeness requirement is met. | 3 / 3 |
Trigger Term Quality | It includes 'ActiveProspect' as a key trigger term, which is specific and useful. However, it lacks natural variations or product-specific terms users might say (e.g., 'LeadConduit', 'TrustedForm', 'lead distribution', 'consent verification') that would help match real user queries. | 2 / 3 |
Distinctiveness Conflict Risk | 'ActiveProspect' is a distinctive brand name that reduces conflict risk, but the generic actions ('manage data, records, automate workflows') could overlap with many other integration or data management skills. The description doesn't clearly carve out a unique niche beyond the brand name. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionable guidance with clear, executable CLI commands and a well-structured connection workflow with proper state handling and error recovery. However, it suffers from significant verbosity — the introductory explanation of ActiveProspect, the exhaustive resource listing, and some redundant descriptions inflate the token cost without adding value Claude needs. Trimming the overview and splitting reference material would substantially improve it.
Suggestions
Remove the introductory paragraph explaining what ActiveProspect is and who uses it — Claude doesn't need this context to execute the skill.
Remove or drastically condense the full resource/action overview listing (Person, Event, List, etc.) since `membrane action list --intent=QUERY` already provides dynamic discovery.
Move the proxy request details and flags table into a separate reference file to keep the main SKILL.md focused on the core workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what ActiveProspect is and who uses it — information Claude doesn't need. The massive overview listing every resource and action (Person, Event, List, Form, Campaign, etc.) adds bulk without actionable value. There's also redundant explanation of Membrane's auth handling and general concepts. | 1 / 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 and flags documented in a table. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, SETUP_FAILED). There's a polling/retry loop for BUILDING state and clear instructions for what to do at each state transition, including error states. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the large resource/action overview and the proxy request details could be split into separate reference files. Everything is inline in a single file with no bundle files to offload detail, making it longer than necessary for an overview. | 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
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.