agencyzoom-automation
Automate Agencyzoom tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill agencyzoom-automation69
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/skillEvaluation — 100%
↑ 12.50xAgent success when using this skill
Validation for skill structure
Discovery
22%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 is too vague to be useful for skill selection. It names the target platform (Agencyzoom) but fails to specify what actions can be performed or when Claude should select this skill. The procedural note about searching tools is implementation detail rather than capability description.
Suggestions
Add specific capabilities: list 2-4 concrete actions like 'manage leads, track policies, generate reports, update client records'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions Agencyzoom, insurance agency management, lead tracking, or policy workflows'
Remove or relocate the procedural guidance ('Always search tools first') to the skill body - descriptions should focus on capabilities, not implementation instructions
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Automate Agencyzoom tasks' which is extremely vague - it doesn't specify what tasks can be automated (e.g., lead management, policy tracking, reporting). 'Search tools first for current schemas' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely weak ('automate tasks' is not specific), and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | Includes 'Agencyzoom' which is a specific product name users might mention, and 'Composio' and 'Rube MCP' as technical terms. However, it lacks natural task-oriented keywords users would say like 'insurance agency', 'leads', 'policies', or 'CRM'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Agencyzoom' is a specific product which helps distinguish it, but 'automate tasks via MCP' is generic enough to potentially conflict with other Composio/MCP-based automation skills. The lack of specific task types increases overlap risk. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%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 skill that efficiently guides Claude through Agencyzoom automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that the tool call examples are structural patterns rather than fully executable code, though this may be appropriate given the dynamic nature of the tool discovery pattern.
Suggestions
Consider showing one complete end-to-end example with actual tool slugs and arguments that might be returned from RUBE_SEARCH_TOOLS, even if noted as illustrative
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Agencyzoom or Composio are. Every section provides actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudocode-style blocks rather than fully executable code. The examples show structure but aren't copy-paste ready for any specific programming language or environment. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status and explicit guidance to confirm ACTIVE status before proceeding. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table at the end provides easy navigation. External toolkit docs linked appropriately without deep nesting. | 3 / 3 |
Total | 11 / 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.