What prerequisites do I need to use docnify-automation?

Rube MCP must be connected, the docnify toolkit must be active, and you should always call RUBE_SEARCH_TOOLS first.

Why must I search tools before executing a workflow?

Tool schemas change over time. Fetching current schemas ensures you use the correct slugs and exact field names, preventing errors.

How do I reuse sessions and ensure active connections?

Reuse session IDs within a workflow and verify ACTIVE status via RUBE_MANAGE_CONNECTIONS before running tools; generate a new session_id for separate runs.

docnify-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/docnify-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Docnify Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/docnify

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Docnify connection via RUBE_MANAGE_CONNECTIONS with toolkit docnify
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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit docnify
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Docnify 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 Docnify task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["docnify"]
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 Docnify-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `docnify`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/docnify-automation/SKILL.mdView on GitHub

Overview

Automate Docnify operations through Composio's Docnify toolkit using Rube MCP. It emphasizes always searching for current tool schemas with RUBE_SEARCH_TOOLS to ensure correct tool slugs and arguments, keeping workflows up to date and repeatable.

How This Skill Works

Start by discovering tools with RUBE_SEARCH_TOOLS for a Docnify use_case, which returns tool slugs and input schemas. Then verify an ACTIVE Docnify connection via RUBE_MANAGE_CONNECTIONS and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, exact arguments, memory, and the session_id from the discovery step.

When to Use It

Automating a Docnify operation when you need up-to-date tool schemas before execution
When you must establish or verify an active Docnify connection via Rube MCP
During multi-step Docnify workflows that require session continuity
When you want to bulk-run multiple tools through RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
To fetch tool schemas and plan execution without hardcoding slugs or assumptions

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case set to 'Docnify operations' to discover tools
Step 2: RUBE_MANAGE_CONNECTIONS to connect toolkit 'docnify' and confirm ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and exact arguments, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input fields
Verify the RUBE_MANAGE_CONNECTIONS status is ACTIVE before executing tools
Use the exact field names and types from search results for tool arguments
Include the memory parameter (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow and generate new ones for separate runs; watch for pagination in responses

Example Use Cases

Discover tools for a Docnify operation, select the appropriate TOOL_SLUG_FROM_SEARCH, and execute with exact arguments
Establish a docnify connection via RUBE_MANAGE_CONNECTIONS and run a single-task workflow
Run multiple tools in sequence by using RUBE_MULTI_EXECUTE_TOOL with a shared session_id and memory object
Perform bulk operations using RUBE_REMOTE_WORKBENCH and run_composio_tool() across a batch of Docnify tasks
Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before automation

Frequently Asked Questions

Add this skill to your agents