agent tool_use skill risk: high
Datagma Automation via Rube MCP
Instructs on automating Datagma operations through Composio's Datagma toolkit via Rube MCP, including prerequisites, connection setup, tool discovery with RUBE_SEARCH_TOOLS, workfl…
- Policy sensitive
- Human review
- External action: high
SKILL 1 file
SKILL.md
---
name: datagma-automation
description: "Automate Datagma tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Datagma Automation via Rube MCP
Automate Datagma operations through Composio's Datagma toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/datagma](https://composio.dev/toolkits/datagma)
## Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Datagma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datagma`
- 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 `datagma`
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: "Datagma 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 Datagma task"}]
session: {id: "existing_session_id"}
```
### Step 2: Check Connection
```
RUBE_MANAGE_CONNECTIONS
toolkits: ["datagma"]
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 Datagma-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `datagma` |
| 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)*
REQUIRED CONTEXT
- Rube MCP connection
- active Datagma connection via RUBE_MANAGE_CONNECTIONS
OPTIONAL CONTEXT
- existing session_id
TOOLS REQUIRED
- RUBE_SEARCH_TOOLS
- RUBE_MANAGE_CONNECTIONS
- RUBE_MULTI_EXECUTE_TOOL
- RUBE_REMOTE_WORKBENCH
- RUBE_GET_TOOL_SCHEMAS
ROLES & RULES
- Always search tools first for current schemas.
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Always discover available tools before executing workflows.
- Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds.
- Confirm connection status shows ACTIVE before running any workflows.
- Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS.
- Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
- Use exact field names and types from the search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow. Generate new ones for new workflows.
- Check responses for pagination tokens and continue fetching until complete.
EXPECTED OUTPUT
- Format
- unknown
- Schema
- table · Operation, Approach
- Constraints
-
- always call RUBE_SEARCH_TOOLS first
- verify ACTIVE connection before execution
- use exact schemas from search results
SUCCESS CRITERIA
- Verify Rube MCP is available
- Confirm connection status shows ACTIVE
- Use schema-compliant arguments from search results
FAILURE MODES
- Hardcoding tool slugs or arguments without searching first
- Executing tools without ACTIVE connection status
- Omitting the memory parameter in execute calls
- Failing to reuse session IDs within a workflow
EXAMPLES
Includes multiple example RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL calls with arguments and session handling.
CAVEATS
- Dependencies
-
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Datagma connection via RUBE_MANAGE_CONNECTIONS with toolkit datagma
- Missing context
-
- Target client or environment where Rube MCP is configured
- Example concrete use_case values for RUBE_SEARCH_TOOLS
- Ambiguities
-
- Placeholder text 'your specific Datagma task' left unresolved in Step 1 example
- Code block syntax for tool calls (e.g., 'queries: [{use_case: ...}]') mixes pseudo-code and literal format without explicit clarification
QUALITY
- OVERALL
- 0.76
- CLARITY
- 0.78
- SPECIFICITY
- 0.82
- REUSABILITY
- 0.68
- COMPLETENESS
- 0.75
IMPROVEMENT SUGGESTIONS
- Replace the literal placeholder 'your specific Datagma task' with a bracketed template variable such as {{use_case_description}}
- Add a short 'Example' subsection showing a filled-in RUBE_SEARCH_TOOLS call with a realistic use_case
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR AGENT
- Xcode MCP Usage Guidelines for Agents agent tool_use
- Xcode MCP Usage Guidelines agent tool_use
- Xquik X/Twitter API Integration Skill agent tool_use
- Filesystem Agent Context Engineering agent tool_use
- Agent Tool Design Principles agent tool_use
- Conventional Git Commit Creator agent tool_use
- GitHub Trending Dashboard Generator agent tool_use
- Hosted Background Agent Infrastructure agent tool_use
- AudioCraft Text-to-Music Generation Guide agent tool_use
- Trello Boards Lists Cards Integrator agent tool_use
- Git Commit Push PR Automator agent tool_use
- GitHub Starred Projects Fetcher via Agent Browser agent tool_use
- 2chat Rube MCP Automation Guide agent tool_use
- Rube MCP Autom Task Automation agent tool_use
- Botbaba Automation via Rube MCP agent tool_use
- Aero Workflow Rube MCP Automation agent tool_use
- Boldsign Automation via Rube MCP agent tool_use
- API Sports Rube MCP Automation Guide agent tool_use
- Bolt IoT Rube MCP Automation Guide agent tool_use
- Booqable Automation via Rube MCP agent tool_use
- Coassemble Automation via Rube MCP agent tool_use
- D2L Brightspace Rube MCP Automation Guide agent tool_use
- Codacy Automation via Rube MCP agent tool_use
- Conversion Tools Rube MCP Automation agent tool_use
- Codereadr Automation via Rube MCP agent tool_use