formbricks-automation
by ComposioHQformbricks-automation helps automate Formbricks tasks through Composio Rube MCP. Install the skill, add the Rube MCP endpoint, verify an active Formbricks connection, and search tools first for current schemas before running workflows.
This skill scores 66/100, which means it is acceptable for listing but should be presented as a lightweight connector-oriented skill rather than a deeply guided workflow pack. Directory users get enough information to understand when to use it—automating Formbricks through Composio's Rube MCP—and how an agent should discover tools and authenticate, but they should expect to rely on live tool discovery and external toolkit schemas for actual Formbricks operations.
- Valid frontmatter clearly declares the skill name, Formbricks automation purpose, and required `rube` MCP dependency.
- Prerequisites and setup steps are explicit: connect Rube MCP, use `RUBE_MANAGE_CONNECTIONS` for the `formbricks` toolkit, and verify ACTIVE connection status before workflows.
- The skill repeatedly instructs agents to call `RUBE_SEARCH_TOOLS` first, which improves schema correctness for a toolkit whose available actions may change.
- No support files, scripts, references, or README are present beyond SKILL.md, so adoption depends entirely on the embedded instructions and external Composio/Rube tooling.
- The workflow guidance is mostly a generic Rube MCP discovery-and-execute pattern, with limited concrete Formbricks-specific examples or task recipes visible in the evidence.
Overview of formbricks-automation skill
What formbricks-automation is for
formbricks-automation is a Claude skill for automating Formbricks operations through Composio’s Rube MCP toolkit. It is designed for users who want an agent to work with Formbricks data or configuration while first discovering the currently available Rube tools and schemas instead of guessing API fields from memory.
Best-fit users and jobs
This skill is a good fit if you already use Formbricks and want an AI agent to help with operational tasks such as finding the right Formbricks tool, checking connection state, preparing tool calls, and executing repeatable workflows through Rube MCP. It is especially useful for teams that need installation-oriented guidance before allowing an agent to touch a live survey, product feedback, or customer research workspace.
Main differentiator: schema discovery first
The key behavior in the formbricks-automation skill is not a static list of Formbricks actions. It instructs the agent to call RUBE_SEARCH_TOOLS before execution so it can retrieve current tool slugs, input schemas, execution plans, and pitfalls. That matters because MCP tool surfaces can change, and stale assumptions are a common cause of failed automation.
Important adoption constraint
This is not a standalone Formbricks client. It requires Rube MCP to be available and a Formbricks connection to be active through RUBE_MANAGE_CONNECTIONS with the formbricks toolkit. If your environment cannot add https://rube.app/mcp as an MCP server or cannot authorize Formbricks through Composio/Rube, this skill will not be useful yet.
How to Use formbricks-automation skill
formbricks-automation install context
Install the skill from the Composio skill collection in the context where your Claude-compatible client can use skills:
npx skills add ComposioHQ/awesome-claude-skills --skill formbricks-automation
Then configure Rube MCP in your client by adding https://rube.app/mcp as an MCP server. Before asking for real Formbricks work, confirm that RUBE_SEARCH_TOOLS is visible. Next, use RUBE_MANAGE_CONNECTIONS with toolkit formbricks; if the returned status is not ACTIVE, complete the authorization link and recheck.
What to read before using it
The repository path is composio-skills/formbricks-automation, and the main file to inspect is SKILL.md. It is short but operationally important: it defines the MCP requirement, the connection check, the required search-first pattern, and the core sequence. There are no separate scripts, rules, references, or README files in this skill folder, so most of the install decision comes from whether your client can expose Rube MCP tools reliably.
Turning a rough request into a strong prompt
A weak prompt is: “Update my Formbricks survey.” It leaves the agent guessing which workspace, survey, fields, and safety limits apply.
A stronger formbricks-automation usage prompt is:
“Use the formbricks-automation skill. First call RUBE_SEARCH_TOOLS for the exact Formbricks task and current schema. Check that the formbricks connection is ACTIVE. I want to list available surveys, identify the survey named ‘Post-purchase NPS’, and prepare a change plan before modifying anything. Do not execute destructive updates without showing me the tool name, input payload, and expected effect.”
This improves output quality because it supplies the target object, asks for discovery, separates planning from execution, and adds a review gate.
Practical workflow to follow
Use a four-step pattern: discover, connect, plan, execute. First ask the agent to search for tools using your specific use case, not a generic “Formbricks operations” query. Then verify the Formbricks connection. Next, have the agent summarize the discovered tool schema and propose the exact call. Only after you approve should it run write operations. For read-only tasks, still ask it to cite the tool slug and key inputs so failures are easier to debug.
formbricks-automation skill FAQ
Is formbricks-automation only for developers?
No, but it is best for users comfortable with connected AI tools and authorization flows. Non-developers can use it if an admin has already configured Rube MCP and Formbricks access. Developers and ops teams will get the most value because they can inspect tool schemas, review payloads, and diagnose connection issues.
How is this better than an ordinary Formbricks prompt?
An ordinary prompt may describe what you want, but it will not automatically know the current Composio Formbricks toolkit schema. The formbricks-automation skill explicitly tells the agent to search tools first, check connection state, and use the returned schema. That reduces hallucinated field names and makes tool execution more auditable.
When should I not use this skill?
Do not use it if you only need general Formbricks advice, survey-writing help, or UI navigation instructions. It is also a poor fit when you cannot enable Rube MCP, cannot authorize a Formbricks connection, or need guaranteed behavior without reviewing MCP tool output. For sensitive production changes, add an approval step before any write or delete action.
What ecosystem does it depend on?
The skill depends on Claude skill support, Rube MCP, and Composio’s Formbricks toolkit. The upstream skill points to the toolkit documentation at composio.dev/toolkits/formbricks. Because the available tools and schemas come from Rube discovery, always trust the live RUBE_SEARCH_TOOLS response over assumptions from an older prompt.
How to Improve formbricks-automation skill
Improve formbricks-automation results with sharper inputs
Give the agent the Formbricks object type, target name or ID if known, desired outcome, safety level, and whether changes should be read-only, proposed, or executed. For example: “Find responses for survey ID X from the last 30 days and summarize trends; do not modify surveys or contacts.” Clear permissions prevent the agent from overreaching and help it choose the right tool query.
Common failure modes to watch
The most common blockers are missing RUBE_SEARCH_TOOLS, inactive Formbricks authorization, vague task descriptions, and skipped schema review. If a tool call fails, ask the agent to rerun tool discovery with the failed use case, compare the attempted payload against the returned schema, and explain which field or connection state caused the issue.
Add review gates for risky operations
For edits, deletions, imports, or bulk updates, require a two-pass workflow. First, the agent should discover tools and draft the payload. Second, you approve or revise it. This is especially important for survey structure, audience/contact changes, and response data workflows where a technically valid tool call can still be operationally wrong.
Iterate after the first output
After the first result, ask for a short execution log: discovered tool slug, connection status, inputs used, returned result, and unresolved assumptions. This turns formbricks-automation from a one-off prompt into a repeatable Form Automation workflow and makes future prompts easier to tighten.