Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Dnsfilter Automation via Rube MCP

agent tool_use skill risk: medium

Dnsfilter Automation via Rube MCP

Instructs on automating Dnsfilter operations through Composio's Dnsfilter toolkit via Rube MCP, requiring RUBE_SEARCH_TOOLS calls first to obtain current schemas followed by RUBE_M…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: dnsfilter-automation
description: "Automate Dnsfilter tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Dnsfilter Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["dnsfilter"]
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 Dnsfilter-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dnsfilter` |
| 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 Dnsfilter connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • existing session_id
  • specific Dnsfilter use case

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • include setup steps
  • always start with RUBE_SEARCH_TOOLS
  • use exact schemas from tool discovery

SUCCESS CRITERIA

  • Discover tools via RUBE_SEARCH_TOOLS first
  • Confirm ACTIVE connection status
  • Execute only schema-compliant tool calls
  • Include memory parameter on every execution

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing before verifying ACTIVE connection
  • Using incorrect field names from outdated schemas
  • Omitting the memory parameter on tool execution

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Dnsfilter connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target execution environment or client (e.g., specific MCP client version)
  • Example values for session_id and memory contents
Ambiguities
  • Literal strings like 'generate_id: true' and 'existing_session_id' are shown without clear indication they are placeholders or examples.
  • Does not specify desired output length or format for tool responses.

QUALITY

OVERALL
0.74
CLARITY
0.82
SPECIFICITY
0.78
REUSABILITY
0.65
COMPLETENESS
0.72

IMPROVEMENT SUGGESTIONS

  • Replace inline placeholders with explicit template markers such as {{use_case}} and {{session_id}}.
  • Add a short 'Example' section showing a complete end-to-end call sequence with realistic values.

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