agencyzoom
AgencyZoom integration. Manage Organizations, Leads, Users, Goals, Filters. Use when the user wants to interact with AgencyZoom data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill agencyzoom75
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agencyzoom/SKILL.mdDiscovery
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.
This description has good structure with explicit 'Use when' guidance and targets a specific platform (AgencyZoom), making it distinctive. However, it lacks specificity in the actions beyond the generic 'Manage' and could benefit from more natural trigger terms users might actually say when working with this insurance CRM.
Suggestions
Replace 'Manage' with specific concrete actions like 'Create, update, search, and delete Organizations, Leads, Users, Goals, and Filters'
Add natural trigger term variations such as 'insurance CRM', 'agency zoom', or action phrases like 'add a new lead', 'look up organization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AgencyZoom) and lists entity types (Organizations, Leads, Users, Goals, Filters) but uses vague action word 'Manage' without specifying concrete operations like create, update, delete, or query. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage Organizations, Leads, Users, Goals, Filters') and when ('Use when the user wants to interact with AgencyZoom data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'AgencyZoom' as a key trigger term and entity names, but lacks common variations users might say like 'agency zoom', 'CRM', 'insurance leads', or action-oriented phrases like 'add a lead' or 'create organization'. | 2 / 3 |
Distinctiveness Conflict Risk | AgencyZoom is a specific third-party platform, making this highly distinctive. The explicit platform name creates a clear niche unlikely to conflict with other CRM or data management skills. | 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 skill provides solid, actionable CLI commands for AgencyZoom integration via Membrane, with good coverage of common operations. However, it includes unnecessary introductory context about what AgencyZoom is, lacks validation/error handling guidance in workflows, and could benefit from better progressive disclosure by moving the large actions table to a reference file.
Suggestions
Remove the opening paragraph explaining what AgencyZoom is - Claude already knows this and it wastes tokens
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list')
Move the popular actions table to a separate ACTIONS.md reference file and link to it
Add error handling guidance for common failure scenarios (auth failures, invalid connection IDs)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AgencyZoom is and who uses it is unnecessary context Claude doesn't need. The rest is reasonably efficient but could be tighter. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout, with clear syntax examples for installation, authentication, searching actions, running actions, and proxy requests. Copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but lacks validation checkpoints. No guidance on verifying successful connection, handling auth failures, or confirming action execution succeeded. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the popular actions table is quite long and could be referenced externally. No external file references for advanced topics or detailed API documentation. | 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.