docmosis-automation
Automates Docmosis workflows using the Rube MCP server.
Install
mkdir -p .claude/skills/docmosis-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14345" && unzip -o skill.zip -d .claude/skills/docmosis-automation && rm skill.zipInstalls to .claude/skills/docmosis-automation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Automate Docmosis tasks via Rube MCP (Composio). Always search tools first for current schemas.Key capabilities
- →Discover available Docmosis tools via Rube MCP
- →Connect to Docmosis through `RUBE_MANAGE_CONNECTIONS`
- →Execute Docmosis operations using `RUBE_MULTI_EXECUTE_TOOL`
- →Handle tool schema changes by searching first
- →Manage connection status for Docmosis toolkit
How it works
The skill automates Docmosis tasks by first discovering available tools via `RUBE_SEARCH_TOOLS`, then ensuring an active connection through `RUBE_MANAGE_CONNECTIONS`, and finally executing the specific Docmosis operations using `RUBE_MULTI_EXECUTE_TOOL` with schema-compliant arguments.
Inputs & outputs
When to use docmosis-automation
- →Generating documents from templates
- →Managing Docmosis connections
- →Automating document creation tasks
About this skill
Docmosis Automation via Rube MCP
Automate Docmosis operations through Composio's Docmosis toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/docmosis
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Docmosis connection via
RUBE_MANAGE_CONNECTIONSwith toolkitdocmosis - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitdocmosis - 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: "Docmosis 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 Docmosis task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["docmosis"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Docmosis-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit docmosis |
| 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
When not to use it
- →When Rube MCP is not connected
- →When an active Docmosis connection is not established
- →When hardcoding tool slugs or arguments without `RUBE_SEARCH_TOOLS`
Prerequisites
Limitations
- →Requires Rube MCP to be connected
- →Requires an active Docmosis connection
- →Tool schemas can change, requiring `RUBE_SEARCH_TOOLS` first
How it compares
This skill provides a standardized, dynamic way to interact with Docmosis through Rube MCP, ensuring tool schemas are always current and connections are verified, which is more reliable than static API integrations.
Compared to similar skills
docmosis-automation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| docmosis-automation (this skill) | 0 | 3mo | No flags | Intermediate |
| notion-knowledge-capture | 10 | 9mo | No flags | Intermediate |
| feishu-doc | 14 | 5mo | No flags | Intermediate |
| openspec-continue-change | 4 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
feishu-doc
openclaw
Feishu document read/write operations. Activate when user mentions Feishu docs, cloud docs, or docx links.
openspec-continue-change
studyzy
通过创建下一个产出物继续处理 OpenSpec 变更。当用户想要推进其变更、创建下一个产出物或继续其工作流程时使用。
kimi-cli-help
MoonshotAI
Answer Kimi Code CLI usage, configuration, and troubleshooting questions. Use when user asks about Kimi Code CLI installation, setup, configuration, slash commands, keyboard shortcuts, MCP integration, providers, environment variables, how something works internally, or any questions about Kimi Code CLI itself.
openspec-archive-change
studyzy
归档实验性工作流中已完成的变更。当用户想要在实现完成后最终确定并归档变更时使用。
feishu-perm
m1heng
Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators.