craftmypdf-automation
by ComposioHQcraftmypdf-automation is a Claude skill for Craftmypdf PDF automation through Composio Rube MCP, with schema-first tool discovery, connection checks, and guided usage for template-based PDF workflows.
This skill scores 66/100, which means it is acceptable for listing but should be treated as a lightweight connector workflow rather than a complete Craftmypdf automation playbook. Directory users get enough clarity to install it when they already use Rube MCP and want agents to discover and invoke Craftmypdf tools, but should expect limited built-in examples and reliance on live schema discovery.
- Defines clear prerequisites: Rube MCP availability, an active Craftmypdf connection, and mandatory use of RUBE_SEARCH_TOOLS before execution.
- Gives a usable setup and discovery pattern for agents, including RUBE_MANAGE_CONNECTIONS and session-based tool search.
- Links to the Craftmypdf toolkit docs and explains that current schemas should be retrieved dynamically, reducing stale-instruction risk.
- No support files, scripts, resources, or embedded schemas are included; the skill depends on live Rube MCP tool discovery for operational detail.
- Craftmypdf task coverage appears generic rather than workflow-specific, so users may still need to know the exact PDF/template operation they want.
Overview of craftmypdf-automation skill
What craftmypdf-automation does
craftmypdf-automation is a Claude skill for running Craftmypdf PDF-generation and document automation tasks through Composio’s Rube MCP. Instead of guessing tool names or hard-coding an API shape, the skill’s core instruction is to discover the current Craftmypdf tools first with RUBE_SEARCH_TOOLS, then execute the workflow using the returned schemas.
Use this skill when you want an AI agent to help create or automate PDFs with Craftmypdf templates, data payloads, exports, or related document workflows, while staying aligned with the live Composio toolkit rather than stale examples.
Best-fit users and jobs
The craftmypdf-automation skill is best for developers, automation builders, and operations teams who already use Claude with MCP tools and need repeatable PDF Processing workflows. Typical jobs include generating invoices, certificates, reports, statements, order documents, or template-based PDFs from structured data.
It is especially useful when the exact Craftmypdf operation may vary by account, connection state, or toolkit schema. The skill pushes the agent to check the active tool catalog before acting, which reduces broken calls when Composio updates parameters or tool slugs.
Main differentiator: schema-first execution
The important differentiator is not a large library of helper scripts; the repository contains a single SKILL.md. Its value is procedural: connect Rube MCP, verify the Craftmypdf connection, search for available tools, inspect current schemas, and only then run the document task.
That makes craftmypdf-automation a lightweight orchestration skill rather than a full PDF application. Install it if you want safer agent behavior around Craftmypdf automation. Do not install it expecting offline PDF rendering, a local CLI, or bundled templates.
How to Use craftmypdf-automation skill
craftmypdf-automation install and setup path
To install the skill from the directory repository, use:
npx skills add ComposioHQ/awesome-claude-skills --skill craftmypdf-automation
Then configure Rube MCP in your client with the endpoint:
https://rube.app/mcp
The skill requires the rube MCP server. Before asking for a PDF workflow, confirm RUBE_SEARCH_TOOLS is available. Next, use RUBE_MANAGE_CONNECTIONS with toolkit craftmypdf and complete the returned auth flow if the connection is not active. The skill is not ready for production use until the Craftmypdf connection status is ACTIVE.
Read composio-skills/craftmypdf-automation/SKILL.md first. There are no extra scripts/, rules/, references/, or resources/ folders in the current skill, so the operational guidance is concentrated in that file.
Inputs the skill needs from you
For strong craftmypdf-automation usage, give the agent the real document objective, not just “make a PDF.” Useful inputs include:
- the Craftmypdf template name or ID, if known
- the output format you need, such as PDF download URL or stored file
- the structured data payload, including required fields
- whether this is a test run or production document
- naming conventions for generated files
- error-handling expectations, such as retrying or stopping on missing fields
A weak prompt is: “Generate an invoice PDF.”
A stronger prompt is: “Use craftmypdf-automation for PDF Processing. First discover current Craftmypdf tools with Rube. Check the Craftmypdf connection. Generate a PDF from template invoice_v3 using this JSON order data. Return the tool used, the final payload shape, and the generated PDF link. Do not invent missing customer fields; ask me if required fields are absent.”
Recommended workflow
Start every run with tool discovery:
RUBE_SEARCH_TOOLS with a use case such as “generate PDF from Craftmypdf template with JSON data.”
Then verify the connection with RUBE_MANAGE_CONNECTIONS for toolkit craftmypdf. If inactive, authenticate before continuing. After that, ask the agent to map your goal to the discovered tool schema and show the planned call before execution, especially for production documents.
For repeatable workflows, save a known-good prompt containing the template ID, required data fields, output expectations, and validation rules. The skill’s “search tools first” pattern is still important even for saved workflows because Composio tool schemas can change.
craftmypdf-automation skill FAQ
Is craftmypdf-automation beginner-friendly?
It is beginner-friendly if you already have Claude MCP access and can complete a Composio/Rube connection flow. It is not a no-code PDF designer. You still need to understand your Craftmypdf templates and provide valid document data.
Beginners should start with a single test template and non-sensitive sample data. Ask the agent to discover tools, explain the schema it found, and show the planned payload before calling execution tools.
How is this better than an ordinary prompt?
An ordinary prompt may hallucinate Craftmypdf API names or rely on outdated examples. The craftmypdf-automation skill explicitly instructs the agent to call RUBE_SEARCH_TOOLS first and use the live schema returned by Rube MCP. That is the main reliability gain.
The skill also encodes the connection check as part of the workflow, which helps distinguish prompt mistakes from setup problems such as an inactive Craftmypdf connection.
When should I not use this skill?
Do not use it if you need local-only PDF generation, custom PDF rendering without Craftmypdf, or a fully packaged integration with scripts and tests. The current skill is a compact MCP workflow guide, not an SDK wrapper.
It is also a poor fit if you cannot connect Rube MCP or authorize the Craftmypdf toolkit. Without those prerequisites, the agent cannot discover or execute the relevant tools.
How to Improve craftmypdf-automation skill
Improve craftmypdf-automation prompts
The fastest way to improve craftmypdf-automation results is to provide complete document context. Include the business purpose, template identifier, required fields, sample data, and expected output. Tell the agent whether it may make assumptions or must pause for missing values.
For production workflows, add constraints such as: “Do not send the tool call until you have shown the mapped payload,” or “Validate that every template field has a corresponding data value.” These instructions reduce malformed PDFs and accidental submissions.
Common failure modes to prevent
Most failures come from three causes: inactive Craftmypdf connection, skipped tool discovery, or incomplete payload data. Prevent them by making the first steps explicit: search tools, check connection, inspect schema, map fields, then execute.
Another common issue is treating template fields as optional. If your template expects nested data, line items, dates, currency, or image URLs, provide representative JSON. The agent can map data more accurately when your sample resembles the real production payload.
Iterate after the first output
After the first PDF run, inspect both the generated document and the tool-call payload. If layout content is missing, update the data mapping rather than rewriting the whole workflow. If the wrong tool was selected, rerun RUBE_SEARCH_TOOLS with a more specific use case, such as “create PDF from existing Craftmypdf template and return export URL.”
For durable team use, maintain a short internal prompt recipe for each document type: template ID, required fields, sample payload, validation checklist, and expected response format. That turns the craftmypdf-automation skill from a one-off helper into a repeatable PDF automation workflow.