botpress-automation
by ComposioHQbotpress-automation helps Claude automate Botpress operations through Composio's Botpress toolkit via Rube MCP. It guides agents to install Rube MCP, verify an ACTIVE Botpress connection, search current tool schemas first, then plan and run supported workflow actions safely.
This skill scores 68/100, which means it is acceptable for directory listing but should be presented as a lightweight integration guide rather than a rich automation pack. Directory users get enough clarity to understand that it enables Botpress operations through Composio/Rube MCP and how an agent should start, but they should expect to rely on live tool discovery for actual Botpress schemas and task details.
- Clear prerequisites identify the required Rube MCP server, `RUBE_SEARCH_TOOLS`, and an active Botpress connection via `RUBE_MANAGE_CONNECTIONS`.
- The skill gives agents an explicit trigger and safety pattern: always search tools first to obtain current Botpress schemas before executing.
- Setup and core workflow sections provide enough sequence guidance to verify MCP availability, authenticate the Botpress toolkit, and proceed through discovered tools.
- No support files, scripts, references, or README are provided beyond SKILL.md, so adoption depends entirely on the brief inline instructions.
- Workflow guidance is mostly a generic Rube MCP discovery-and-execution pattern rather than detailed Botpress-specific task recipes.
Overview of botpress-automation skill
What botpress-automation is for
botpress-automation is a Claude skill for automating Botpress operations through Composio’s Botpress toolkit via Rube MCP. Instead of asking the model to guess Botpress API fields, the skill instructs the agent to discover the current tool schemas first, verify the Botpress connection, and then execute actions through the available Rube tools.
Best-fit users and jobs
This botpress-automation skill is best for users who already work with Botpress and want an AI agent to help run operational tasks such as inspecting available Botpress actions, preparing workflow changes, or executing supported Botpress toolkit operations. It fits teams using Claude with MCP access who need repeatable tool-driven automation rather than one-off natural-language advice.
Key adoption requirement
The main blocker is not the skill file itself; it is the environment. You need Rube MCP connected and a Botpress connection marked ACTIVE through RUBE_MANAGE_CONNECTIONS. The skill’s most important rule is: call RUBE_SEARCH_TOOLS before acting, because Composio tool names, parameters, schemas, and pitfalls may change.
What makes it different from a generic prompt
A generic prompt may produce plausible but stale Botpress instructions. botpress-automation pushes the agent into a safer execution pattern: discover tools, check authentication, read current schemas, build an execution plan, then run the matching tool calls. That makes it more useful for live Botpress automation than for general Botpress documentation lookup.
How to Use botpress-automation skill
botpress-automation install and setup context
Install the skill in a compatible skills-enabled Claude environment:
npx skills add ComposioHQ/awesome-claude-skills --skill botpress-automation
Then add Rube MCP as an MCP server using:
https://rube.app/mcp
Before using the skill, confirm RUBE_SEARCH_TOOLS is available. Next, call RUBE_MANAGE_CONNECTIONS with toolkit botpress. If the connection is not ACTIVE, complete the returned authorization flow, then re-check status before attempting Botpress operations.
Inputs the skill needs from you
For strong botpress-automation usage, give the agent the operational goal, Botpress context, and safety boundaries. Useful inputs include:
- The exact Botpress task you want completed
- Workspace, bot, workflow, integration, or content identifiers if known
- Whether the action should inspect, create, update, delete, publish, or only draft a plan
- Constraints such as “do not modify production,” “ask before destructive changes,” or “only list available tools”
- Expected output format, such as a summary, tool-call plan, or execution log
Weak input: “Update my Botpress bot.”
Stronger input: “Use botpress-automation for Workflow Automation. First discover current Botpress tools, verify my Botpress connection, then list the tools that can update workflow nodes. Do not execute changes until I approve the proposed tool call and parameters.”
Practical workflow for first run
Start by reading composio-skills/botpress-automation/SKILL.md; it is the only support file surfaced for this skill, so it contains the full operating contract. In the session, ask the agent to follow this order:
- Use
RUBE_SEARCH_TOOLSfor the specific Botpress use case. - Use
RUBE_MANAGE_CONNECTIONSto confirm thebotpresstoolkit connection. - Summarize available tool slugs, required fields, and risks.
- Ask for missing IDs or approval if the operation changes Botpress state.
- Execute only after schemas and connection status are clear.
This sequence is especially important because the repository explicitly says schemas should be discovered at runtime rather than assumed from the skill text.
Prompt pattern that invokes the skill well
A good prompt should make the tool-discovery requirement explicit:
“Use the botpress-automation skill. My goal is to [specific Botpress task]. First call RUBE_SEARCH_TOOLS for this exact use case and report the available Botpress tool schemas. Then check the Botpress connection with RUBE_MANAGE_CONNECTIONS. If active, propose the safest execution plan with required parameters. Do not run destructive actions without confirmation.”
This wording improves output quality because it separates discovery, connection validation, planning, and execution instead of letting the agent jump directly to an uncertain tool call.
botpress-automation skill FAQ
Is botpress-automation suitable for beginners?
Yes, if the user has access to Claude skills and can configure MCP. It is not a no-code Botpress tutorial. Beginners should use it first for discovery tasks: list available Botpress tools, explain required parameters, and identify what information is missing before making changes.
Does the skill include its own Botpress scripts?
No. The repository evidence shows a single SKILL.md file and no companion scripts, resources, rules, README, or metadata files. The value is in the enforced Rube MCP workflow, not in local automation code bundled with the skill.
When should I not use botpress-automation?
Do not use it when you cannot connect Rube MCP, cannot authorize the Botpress toolkit, or need offline Botpress code generation without live tool access. Also avoid using it for destructive production changes unless your prompt requires confirmation before update, delete, publish, or deployment actions.
How does it compare with using Composio directly?
Using Composio or Rube directly gives you the tools; the botpress-automation guide gives the agent a narrow operating pattern for Botpress. It is useful when you want Claude to remember to search tools first, validate the connection, and avoid relying on stale assumptions.
How to Improve botpress-automation skill
Improve botpress-automation results with better goals
The most common failure mode is an underspecified Botpress request. Replace broad goals with task-specific language: “find tools for updating a workflow transition,” “inspect bot configuration,” or “prepare a publish plan.” Include known IDs and environment names whenever possible, because many Botpress operations depend on exact resource identifiers.
Add guardrails for state-changing actions
For safer botpress-automation usage, define approval rules before tool execution. Example: “Read-only inspection is allowed. For create, update, delete, publish, or deploy actions, show the tool slug, parameters, and expected effect, then wait for approval.” This prevents the agent from treating all Botpress operations as equally safe.
Iterate after the first tool discovery
The first RUBE_SEARCH_TOOLS result should shape the next prompt. If the returned schema exposes required fields you do not have, ask the agent to find or list candidate resources before executing the target operation. If multiple tools look relevant, request a comparison of required inputs, side effects, and failure risks.
What maintainers could add next
The skill would be stronger with examples for common Botpress tasks, a read-only-first workflow, and sample prompts for workspace inspection, workflow updates, and connection troubleshooting. A short troubleshooting section for inactive connections, missing schemas, and permission errors would also improve install confidence for teams evaluating botpress-automation.