addresszen-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/addresszen-automation --openclawAddresszen Automation via Rube MCP
Automate Addresszen operations through Composio's Addresszen toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/addresszen
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Addresszen connection via
RUBE_MANAGE_CONNECTIONSwith toolkitaddresszen - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitaddresszen - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Addresszen operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Addresszen task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["addresszen"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Addresszen-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit addresszen |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/addresszen-automation/SKILL.mdView on GitHub Overview
Automate Addresszen operations through Composio's Rube MCP toolkit. The workflow emphasizes always searching for current tool schemas before executing tasks to keep integrations up to date, and requires an active Addresszen connection managed via RUBE_MANAGE_CONNECTIONS.
How This Skill Works
The skill discovers available tools with RUBE_SEARCH_TOOLS, validates the Addresszen connection via RUBE_MANAGE_CONNECTIONS, and executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the correct slug and schema-compliant arguments. It optionally references full tool schemas via RUBE_GET_TOOL_SCHEMAS and always includes a memory payload for each execution. This pattern ensures up-to-date tooling and robust session handling.
When to Use It
- Automating repetitive Addresszen operations (e.g., address verification, normalization, or updates).
- Setting up or refreshing an Addresszen connection to ensure ACTIVE status before workflows.
- When tool schemas change and you need to fetch current slugs and arguments via RUBE_SEARCH_TOOLS.
- Orchestrating multi-tool Addresszen workflows that require discovery, validation, and execution steps.
- Troubleshooting integration issues by re-validating tool schemas and connection status before reruns.
Quick Start
- Step 1: Verify RUBE_SEARCH_TOOLS responds to discover available Addresszen tools.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit addresszen and ensure the connection status is ACTIVE.
- Step 3: Execute a discovered tool slugs with RUBE_MULTI_EXECUTE_TOOL using the required memory and a valid session_id.
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas before any execution.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Use exact field names and types from the tool schemas returned by searches.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
- Reuse session IDs within a workflow and paginate responses as needed to complete tasks.
Example Use Cases
- Automate a batch of Addresszen address verifications across multiple accounts by discovering tools, validating the connection, then executing verifications in sequence.
- Create or update addresses from a CRM into Addresszen by discovering the appropriate tool slug and applying schema-compliant arguments.
- Normalize a list of addresses using the discovered Addresszen tools and validate results before syncing to downstream systems.
- Schedule a nightly sync of addresses by discovering relevant tools, validating connection status, and executing in a time-controlled session.
- Migrate Addresszen tasks in a new environment by re-fetching tool schemas, re-establishing ACTIVE connections, and executing with fresh session IDs.
