docmosis-automation
by ComposioHQdocmosis-automation helps agents run Docmosis workflow automation through Composio Rube MCP by discovering current tool schemas, checking the Docmosis connection, and executing with less guesswork.
This skill scores 66/100, meaning it is acceptable for listing but limited. Directory users can understand when to use it and what external setup is required, and agents get a useful Rube MCP discovery pattern for Docmosis. However, the repository evidence shows mostly generic operational scaffolding rather than concrete Docmosis workflows, so installers should expect to rely on live tool discovery and the linked toolkit docs for specifics.
- Clear trigger and scope: it is meant for automating Docmosis operations through Composio's Docmosis toolkit via Rube MCP.
- Prerequisites and setup steps identify the required Rube MCP server, RUBE_SEARCH_TOOLS availability, and active Docmosis connection via RUBE_MANAGE_CONNECTIONS.
- The skill instructs agents to search tools first for current schemas, which reduces schema guesswork and helps keep execution aligned with live Composio tool definitions.
- Workflow guidance appears generic to Rube MCP discovery and does not document concrete Docmosis operations, example inputs, or common document-generation scenarios in the provided evidence.
- No install command or supporting files are present; adoption depends on users already understanding Rube MCP and having an active Docmosis connection.
Overview of docmosis-automation skill
What docmosis-automation does
docmosis-automation is a Claude skill for running Docmosis-related workflow automation through Composio’s Rube MCP server. It is designed to help an agent discover the current Docmosis tool schemas, verify the Docmosis connection, and then execute document automation tasks with less guesswork than a generic prompt.
The core value is not a prebuilt script library. The value is an execution pattern: connect Rube MCP, authenticate the docmosis toolkit, call RUBE_SEARCH_TOOLS before acting, and use the returned schemas to choose the right Docmosis operation.
Best fit for this skill
Use the docmosis-automation skill if you want an AI agent to help with Docmosis operations inside a broader workflow automation setup. It is most useful when your task depends on live tool availability, current API schemas, or authenticated Docmosis access through Composio.
Good fits include teams that already use Docmosis for document generation and want Claude to help orchestrate tasks such as finding available operations, preparing inputs, checking connection state, or chaining Docmosis actions into a larger business workflow.
Key differentiator: schema discovery first
The most important instruction in this skill is to always search tools first. Instead of assuming a fixed Docmosis API shape, the agent should call RUBE_SEARCH_TOOLS for the specific use case and rely on the returned tool slugs, schemas, execution plans, and pitfalls.
That makes the docmosis-automation skill better suited to changing MCP tool environments than a static prompt that hardcodes parameters.
What to know before installing
This skill requires Rube MCP and an active Docmosis connection managed through RUBE_MANAGE_CONNECTIONS. It does not include extra scripts, bundled templates, or local helper files; the repository path contains only SKILL.md. If you need a complete document-template system, you will still need your own Docmosis templates, data model, and business rules.
How to Use docmosis-automation skill
docmosis-automation install and setup context
Install the skill from the Composio skills repository:
npx skills add ComposioHQ/awesome-claude-skills --skill docmosis-automation
Then configure Rube MCP in your AI client by adding:
https://rube.app/mcp
Before using the skill, confirm that RUBE_SEARCH_TOOLS is available. Next, call RUBE_MANAGE_CONNECTIONS with toolkit docmosis. If the connection is not ACTIVE, complete the returned authorization flow and check again before attempting any Docmosis operation.
Inputs the skill needs from you
The docmosis-automation skill works best when your prompt includes the actual business goal, not just “use Docmosis.” Provide:
- The Docmosis task you want performed
- Whether the Docmosis connection is already active
- Template names, document identifiers, or expected output formats if known
- Input data shape, such as customer fields, invoice fields, or report fields
- Any workflow constraints, such as “do not send until I approve” or “only discover tools first”
A weak prompt is: “Create a document with Docmosis.”
A stronger prompt is: “Use the docmosis-automation skill to discover current Docmosis tools through Rube MCP. Check the docmosis connection, then identify the correct operation for generating a contract from an existing template. I have template name Standard_Service_Agreement and JSON data with client name, address, service dates, and pricing. Do not execute generation until you show the required schema.”
Practical workflow for reliable usage
Start every workflow with tool discovery:
RUBE_SEARCH_TOOLS
Use a query that matches your real task, for example: “generate a PDF from a Docmosis template using customer JSON data” or “list available Docmosis templates before document generation.”
Then check the connection with RUBE_MANAGE_CONNECTIONS for toolkit docmosis. Only after the connection is active should the agent select a tool and prepare the call. This order matters because Rube may return current schemas, required fields, recommended plans, or known pitfalls that are not visible from the static skill file.
Repository files to read first
The key file is:
composio-skills/docmosis-automation/SKILL.md
There are no visible README.md, scripts/, references/, resources/, or rules/ folders in this skill path. Read SKILL.md for the intended workflow and then rely on live Rube MCP discovery for exact tool names and parameters.
docmosis-automation skill FAQ
Is docmosis-automation for Workflow Automation or document design?
docmosis-automation is mainly for Workflow Automation around Docmosis operations, not for visually designing Docmosis templates. It can help an agent discover and call available Docmosis tools through Rube MCP, but your organization still needs the underlying Docmosis templates, data sources, and document rules.
How is this better than an ordinary prompt?
An ordinary prompt may guess tool names or invent parameters. The docmosis-automation skill explicitly tells the agent to use RUBE_SEARCH_TOOLS first, then work from current schemas. That reduces failures caused by stale assumptions and makes the workflow more compatible with Composio’s live toolkit interface.
Is this suitable for beginners?
It is beginner-friendly only if you are comfortable connecting an MCP server and completing an authentication flow. The skill’s instructions are short, but the surrounding setup matters: Rube MCP must be available, and the Docmosis toolkit connection must be active before useful work can happen.
When should I not use this skill?
Do not use it if you need offline document generation, a standalone Docmosis SDK wrapper, bundled sample templates, or a no-auth demo. Also avoid it if your AI client cannot use MCP tools, because the skill depends on Rube MCP capabilities rather than local scripts.
How to Improve docmosis-automation skill
Improve prompts for docmosis-automation results
The fastest way to improve docmosis-automation output is to describe the end-to-end document job. Include the intended Docmosis operation, known template details, input data fields, desired output type, approval steps, and whether execution should stop after schema discovery.
For example: “Discover tools first, verify Docmosis connection, then prepare but do not run the generation call for a PDF invoice using template Invoice_v3. Required data fields are invoice number, customer name, line items, subtotal, tax, total, and due date.”
Common failure modes to prevent
The main failure mode is skipping discovery and assuming a schema. Prevent this by explicitly saying: “Call RUBE_SEARCH_TOOLS before selecting any Docmosis tool.”
Another common issue is attempting execution before authentication is active. Ask the agent to check RUBE_MANAGE_CONNECTIONS and report the connection status before continuing. If required fields are unknown, pause after discovery and map your available data to the returned schema.
Iterate after the first tool discovery
Treat the first RUBE_SEARCH_TOOLS result as a planning step. Review the returned tool slugs, required inputs, and warnings, then refine the task. If the schema requires fields you did not provide, update your prompt with the missing values instead of asking the agent to guess.
This is especially important for document automation, where small field mismatches can produce invalid documents, incomplete merges, or failed generation calls.
Improve the skill itself
If you maintain a fork, the highest-value improvements would be examples for common Docmosis workflows, sample prompt patterns, and a short troubleshooting section for inactive connections and missing schemas. Because the current skill has no support files, adding concise references for template generation, template listing, and output handling would make the docmosis-automation guide easier to adopt without weakening its schema-first approach.