home / skills / composiohq / awesome-claude-skills / dadata-ru-automation

dadata-ru-automation skill

/dadata-ru-automation

This skill automates Dadata Ru tasks through Composio's MCP, discovering current tool schemas first to ensure accurate tool execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill dadata-ru-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.9 KB
---
name: dadata-ru-automation
description: "Automate Dadata Ru tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Dadata Ru Automation via Rube MCP

Automate Dadata Ru operations through Composio's Dadata Ru toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/dadata_ru](https://composio.dev/toolkits/dadata_ru)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Dadata Ru connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dadata_ru`
- 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 `dadata_ru`
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: "Dadata Ru 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 Dadata Ru task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["dadata_ru"]
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 Dadata Ru-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dadata_ru` |
| 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](https://composio.dev)*

Overview

This skill automates Dadata Ru operations through Rube MCP (Composio) so agents can call Dadata services reliably. It orchestrates tool discovery, connection management, and schema-compliant execution to avoid runtime errors. The skill enforces a discover-first pattern to keep integrations resilient to changing tool schemas.

How this skill works

Before any action it calls RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended plans. It then verifies or activates the Dadata Ru connection via RUBE_MANAGE_CONNECTIONS and executes tasks with RUBE_MULTI_EXECUTE_TOOL using the discovered schemas and a session_id. The skill always includes a memory object in execute calls, handles pagination tokens, and encourages session reuse for multi-step workflows.

When to use it

  • Integrating Dadata Ru lookups or batch validation into an agent workflow
  • Automating address, company, or personal data queries with schema validation
  • Running bulk or paginated Dadata operations where reliability and retries matter
  • Building composable workflows that must adapt to changing tool schemas

Best practices

  • Always call RUBE_SEARCH_TOOLS first — never hardcode tool slugs or argument shapes
  • Confirm connection status via RUBE_MANAGE_CONNECTIONS and follow its auth link until ACTIVE
  • Pass schema-compliant fields and types exactly as returned by search results
  • Include a memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse a session_id for related steps; create a fresh session for distinct workflows
  • Check and follow pagination tokens in responses to retrieve full result sets

Example use cases

  • Validate and normalize an address list by discovering the address-cleaning tool and running it in bulk
  • Enrich company records by finding the company-enrichment tool schema, connecting, and executing paginated queries
  • Perform interactive lookups during a user session: discover relevant lookup tools, ensure connection, then execute single-step queries
  • Run scheduled batch jobs using RUBE_REMOTE_WORKBENCH to call composio tools with discovered schemas

FAQ

What is the first call I should make when using the skill?

Always call RUBE_SEARCH_TOOLS with a Dadata Ru use case to retrieve current tool slugs and input schemas.

What if the connection shows not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete authentication, then re-check until the status is ACTIVE.