‹ 首页

addresszen-automation

@openteams-lab · 收录于 昨天 · 上游提交 2 天前

Automate Addresszen tasks via Rube MCP (Composio). Always search tools first for current schemas.

场景地址处理批量任务

适合你，如果你需要自动完成地址服务的重复操作

/ 下载安装
https://github.com/openteams-lab/openteams/tree/main/assets/skills/addresszen-automation ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add openteams-lab/openteams/addresszen-automation
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- openteams-lab/openteams/addresszen-automation
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify openteams-lab/openteams/addresszen-automation
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
562GitHub stars
~545上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 808a325 · 表述以原文为准
它做什么

装上后，Claude 可以通过 Rube MCP 自动完成 Addresszen 的各类任务，包括搜索可用工具、检查连接状态、执行工具等操作，无需手动切换页面。

什么时候触发

当用户要求执行 Addresszen 相关的自动化操作（如搜索工具、执行工具、检查连接）时触发。需要先完成 Rube MCP 连接并激活 Addresszen。

装好后可以这样说
Claude 会调用 RUBE_SEARCH_TOOLS
Claude 会先搜索工具再执行
Claude 会调用管理连接工具
技能原文 SKILL.md作者撰写 · Apache-2.0 · 808a325

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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit addresszen
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. 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

按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…