home / skills / composiohq / awesome-claude-skills / ravenseotools-automation

ravenseotools-automation skill

safe

/ravenseotools-automation

This skill automates Ravenseotools workflows via Rube MCP, always discovering current tool schemas before execution to ensure up-to-date operations.

npx playbooks add skill composiohq/awesome-claude-skills --skill ravenseotools-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: ravenseotools-automation
description: "Automate Ravenseotools tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Ravenseotools Automation via Rube MCP

Automate Ravenseotools operations through Composio's Ravenseotools toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["ravenseotools"]
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 Ravenseotools-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ravenseotools` |
| 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 Ravenseotools operations through Composio's Ravenseotools toolkit using Rube MCP. It provides a reliable pattern for discovering tool schemas, validating connections, and executing multi-step workflows programmatically. Follow the search-first rule to avoid schema drift and ensure stable automation.

How this skill works

The skill always calls RUBE_SEARCH_TOOLS first to retrieve current tool slugs, input schemas, and recommended execution plans. It then checks or establishes an active Ravenseotools connection via RUBE_MANAGE_CONNECTIONS before running actions. Execution uses RUBE_MULTI_EXECUTE_TOOL (with a memory object and session_id) or RUBE_REMOTE_WORKBENCH for bulk tasks, while pagination and schema references are handled as returned.

When to use it

Automate repetitive SEO tasks that Ravenseotools supports (site audits, keyword checks, backlink scans).
Integrate Ravenseotools actions into agent workflows or pipelines that require up-to-date tool schemas.
Run bulk operations or scheduled workflows that must respect connection state and session reuse.
Build multi-step sequences where tool outputs feed subsequent tool inputs via Rube MCP.

Best practices

Always call RUBE_SEARCH_TOOLS first — never hardcode tool slugs or argument names.
Verify Ravenseotools connection status with RUBE_MANAGE_CONNECTIONS and complete any required auth flow until status is ACTIVE.
Include an explicit memory object in RUBE_MULTI_EXECUTE_TOOL calls (use {} when no memory is needed).
Reuse session_id within a single workflow; generate new session_ids for separate workflows.
Respect schema field types exactly and handle pagination tokens until the response set is complete.

Example use cases

Run a full site audit: search tools, confirm connection, execute the audit tool with schema-compliant args, then fetch paginated results.
Automate keyword tracking: discover the keyword tool, send batched queries via RUBE_MULTI_EXECUTE_TOOL, and store results in memory for follow-up processing.
Bulk backlink validation: use RUBE_SEARCH_TOOLS to find the backlink checker, then use RUBE_REMOTE_WORKBENCH to run run_composio_tool() across many domains.
Onboard a new account: call RUBE_MANAGE_CONNECTIONS to initiate auth, follow returned auth link, and confirm ACTIVE status before executing initial health checks.

FAQ

What should I do if RUBE_SEARCH_TOOLS returns different schemas than before?

Treat the returned schemas as authoritative. Update your arguments to match field names and types, and rerun any dependent steps. Never assume schema stability.

Is an API key required to use Rube MCP with this skill?

No API key is required. Add https://rube.app/mcp as an MCP server in your client and use the Rube MCP endpoints; connection setup and OAuth flows are handled via RUBE_MANAGE_CONNECTIONS.