addresszen-automation
Automate Addresszen tasks via Rube MCP (Composio). Always search tools first for current schemas.
69
Quality
53%
Does it follow best practices?
Impact
97%
4.84xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/addresszen-automation/SKILL.mdQuality
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 effectively guide skill selection. It names specific tools/products but fails to explain what Addresszen actually does, what tasks can be automated, or when Claude should select this skill. The operational instruction about searching tools doesn't help with skill selection.
Suggestions
Add specific concrete actions that Addresszen enables (e.g., 'validate addresses', 'geocode locations', 'format postal addresses')
Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs address validation, geocoding, or postal address formatting')
Briefly explain what Addresszen is for users unfamiliar with the product to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Addresszen tasks' without specifying what concrete actions are possible. No specific capabilities are listed beyond a generic 'search tools' instruction. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Addresszen tasks') and there is no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Addresszen', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or task-oriented language. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names (Addresszen, Rube MCP, Composio) provide some distinctiveness, but the generic 'automate tasks' framing could overlap with other automation skills. | 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 Addresszen automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that tool call examples are structural templates rather than fully executable code, though this may be intentional given the dynamic nature of MCP tool discovery.
Suggestions
Consider showing one complete end-to-end example with actual tool slugs and arguments that would be returned from RUBE_SEARCH_TOOLS, even if noted as illustrative
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Addresszen or Composio are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter structures, but uses pseudo-code style rather than fully executable examples. The tool calls show structure but aren't copy-paste ready for any specific MCP client. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status before proceeding and addresses error recovery through the 'Known Pitfalls' section. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides at-a-glance 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 | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- 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.