$ ~/registry/skill/composiohq-composio-skills-addresszen-automation

SKILL

addresszen-automation

Name: addresszen-automation
Author: Composio

Automate Addresszen workflows via Rube MCP using the latest tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source workflow prompt/instruction set rather than executable code, with no built-in secrets and no stated local execution or local file access, so the overall risk is relatively low. The main consideration is that it depends on external Rube MCP and an Addresszen connection, which means task data may be sent to those remote services during use.

CredentialsCaution

The material says there is 'no API key', but it requires establishing an `addresszen` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link if the connection is not active. So the skill itself does not embed secrets, but it depends on external account authorization tokens, and the scope of those permissions and token handling should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using calls such as `RUBE_SEARCH_TOOLS` and `RUBE_MULTI_EXECUTE_TOOL`, which send queries, arguments, session IDs, and workflow content to that service. It may also reach Addresszen/Composio-related backends. This is declared remote communication, but it does involve outbound transmission of task data.

Code executionLow risk

Based on the provided material, this is a prompt-only skill that mainly describes tool discovery, connection checks, and remote tool invocation order. There is no indication of starting local processes, executing shell/scripts, or requesting additional system privileges on the host.

Data accessCaution

There is no stated ability to read/write local files or access sensitive local directories. However, once the Addresszen connection is ACTIVE, the skill can drive remote tools to query or operate on Addresszen account/business data. The effective data scope depends on the permissions granted to that external connection, so least-privilege controls are important.

Supply chainLow risk

The source is an open-source GitHub repository with very strong community adoption (about 64.7k stars), which are meaningful positive trust signals. The material also indicates a prompt-only skill, making it easier to review. The license is not declared and maintenance status is unknown, but the current evidence does not justify a high-risk rating.

Recommendations

Enable it only if you trust `rube.app`, Composio, and their data-handling practices, and review their privacy and retention policies.
Grant the Addresszen connection the minimum necessary permissions and avoid using a highly privileged production account for testing.
Do not include unnecessary sensitive business data in requests, and periodically review/revoke unused connection authorizations.
Regularly review updates to the MCP service and repository, especially changes in licensing, maintenance status, and connection flows.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "addresszen-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/addresszen-automation/SKILL.md
2. Save it as ~/.claude/skills/addresszen-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Addresszen 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_CONNECTIONS with toolkit addresszen
Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit addresszen
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_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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

Automate Mezmo tasks via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_