crustdata-automation

Automate Crustdata operations and data retrieval workflows 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 crustdata-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crustdata-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/crustdata-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill crustdata-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of navigating Crustdata's API and tool schemas, allowing you to execute complex data operations through a standardized, agent-driven interface.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetch current tool schemas and execution plans via Rube MCP.
  • Connection Management: Handle authentication and session state for Crustdata toolkits seamlessly.
  • Workflow Execution: Perform multi-step data operations, including bulk actions and remote workbench tasks, using a unified execution pattern.

Quick Start

Use the crustdata-automation skill to discover available tools and execute a data retrieval task for my current project.

Frequently Asked Questions about crustdata-automation

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

FAQPage Schema
How do I discover available Crustdata tools?

Call the RUBE_SEARCH_TOOLS command with a specific use case query to retrieve current tool slugs, input schemas, and recommended execution plans for your Crustdata task.

How to verify my Crustdata connection status?

Execute the RUBE_MANAGE_CONNECTIONS command with the 'crustdata' toolkit parameter to check if your connection is currently ACTIVE before attempting any tool execution.

Can I reuse session IDs for multiple tasks?

Yes, you should reuse session IDs within a single logical workflow to maintain state, but you must generate new session IDs when starting entirely new, unrelated workflows.

Why does my tool execution fail?

Execution often fails if the connection is not active or if the tool arguments do not strictly match the schema returned by the most recent RUBE_SEARCH_TOOLS call.