$ ~/registry/skill/composiohq-composio-skills-docnify-automation

SKILL

docnify-automation

Name: docnify-automation
Author: Composio

Automate Docnify document tasks through Rube MCP with schema-first tool discovery.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

The material is an open-source prompt/instruction skill with no embedded code execution, secrets, or direct local file access, so overall risk is low. The main consideration is that it is designed to rely on remote Rube MCP and external Docnify connections, which introduces third-party data flow and account authorization at runtime.

CredentialsCaution

The skill itself declares no keys or environment variables, but the README explicitly requires an active Docnify connection via `RUBE_MANAGE_CONNECTIONS` and completion of an auth link. So the skill does not directly embed credentials, yet runtime use depends on external account authorization; token scope and lifecycle on the third-party connection should be reviewed.

Network egressCaution

The README instructs users to configure `https://rube.app/mcp` as an MCP server and execute actions through Composio/Docnify tooling. This means task content, tool arguments, and related business data may be sent to remote Rube/Composio/Docnify services. This is normal for this kind of integration, but data flow and privacy boundaries should be verified.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no executable script, install command, or local process control logic. It describes how to call external MCP tools rather than directly executing code on the local machine.

Data accessCaution

The material does not describe direct read/write access to the local filesystem or system resources. However, once connected to Docnify, the remote tools may access account or document data relevant to Docnify operations. There is no clear sign of excessive local authorization beyond the stated purpose, but the connected account should still follow least-privilege principles.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.7k stars). Combined with its prompt-only nature, auditability is good and supply-chain risk is relatively low. The missing license declaration and unknown maintenance status are worth noting, but they are not enough on their own to raise this to high risk.

Recommendations

Enable this skill only after confirming you accept data flow through Rube/Composio/Docnify and reviewing their privacy/data-handling terms.
Use a least-privilege Docnify account connection and avoid granting unnecessary workspace or document access.
In production, validate the actual tool list and schemas returned by `RUBE_SEARCH_TOOLS` to avoid mistakes caused by remote schema changes.
Prefer trusted MCP service sources and keep watching the repository's maintenance status and future security updates.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "docnify-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/docnify-automation/SKILL.md
2. Save it as ~/.claude/skills/docnify-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Docugenerate document generation workflows through Rube MCP for faster operations.

ComposioGet→

$ loading_