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

agent tool_use skill risk: high

Craftmypdf Rube MCP Automation Guide

Instructs the model to automate Craftmypdf operations via Composio's Rube MCP by first calling RUBE_SEARCH_TOOLS, then RUBE_MANAGE_CONNECTIONS to activate the craftmypdf toolkit, a…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["craftmypdf"]
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 Craftmypdf-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `craftmypdf` |
| 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_SEARCH_TOOLS availability
  • craftmypdf connection status

OPTIONAL CONTEXT

  • existing session_id
  • specific use_case for tool search

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
  3. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
  4. If connection is not ACTIVE, follow the returned auth link to complete setup
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Always search first
  8. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS`
  9. Check connection
  10. Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools
  11. Use exact field names and types from the search results
  12. Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`)
  13. Reuse session IDs within a workflow
  14. Generate new ones for new workflows
  15. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from search results

EXAMPLES

Includes multiple example calls to RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL with sample arguments and session handling.

CAVEATS

Dependencies
  • RUBE_SEARCH_TOOLS available
  • Active Craftmypdf connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target AI model or agent framework expected to consume the prompt
  • Example of a complete end-to-end workflow with real tool slugs and arguments
Ambiguities
  • Example tool calls use placeholder syntax (e.g., 'your specific Craftmypdf task') without showing concrete filled-in values.
  • Does not specify desired output format or verbosity when executing workflows.

QUALITY

OVERALL
0.76
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.68
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Replace inline code blocks with explicit function-call templates that include both the call and an example response.
  • Add a 'Variables' section at the top listing all placeholders (session_id, use_case, tool_slug) and their expected formats.

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