kadoa-automation

Automate Kadoa data extraction tasks through the Rube MCP gateway.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill kadoa-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kadoa-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/kadoa-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill kadoa-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of interacting with Kadoa's web automation and data extraction tools, allowing for programmatic control over complex scraping and data retrieval workflows.

Core Features & Use Cases

  • Tool Discovery: Dynamically query available Kadoa tool schemas to ensure compatibility before execution.
  • Connection Management: Handle authentication and session state for Kadoa toolkits via the Rube MCP interface.
  • Use Case: Automate the extraction of structured data from dynamic websites by discovering the correct Kadoa tools, verifying the connection, and executing multi-step extraction workflows without manual browser interaction.

Quick Start

Use the kadoa-automation skill to discover available tools and execute a data extraction task for the target website.

Frequently Asked Questions about kadoa-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Kadoa tools?

Call the RUBE_SEARCH_TOOLS function with a specific use case query to retrieve available tool slugs, input schemas, and execution plans for your Kadoa task.

How to verify if my Kadoa connection is active?

Use the RUBE_MANAGE_CONNECTIONS command with the 'kadoa' toolkit parameter to check the current status and follow the provided authentication link if the status is not ACTIVE.

Can I hardcode tool slugs in my automation?

No, tool schemas and slugs change frequently. Always use RUBE_SEARCH_TOOLS to fetch the current schema before executing any tool to ensure compatibility and prevent errors.

What is the purpose of the memory parameter in RUBE_MULTI_EXECUTE_TOOL?

The memory parameter maintains state across tool executions within a session. Always include it in your calls, even as an empty object, to ensure the Rube MCP correctly processes the request.

How do I handle long-running extraction tasks?

Check the tool responses for pagination tokens and continue fetching data until the process is complete, ensuring you reuse the same session ID throughout the workflow.