exist-automation
by ComposioHQexist-automation helps Claude automate Exist tasks through Composio Rube MCP by discovering current tool schemas, checking the Exist connection, and guiding safe workflow execution.
This skill scores 68/100, which means it is acceptable for directory listing but should be presented as a lightweight MCP workflow guide rather than a turnkey automation package. Directory users get enough clarity to know it is for Exist automation through Rube MCP and how an agent should discover tools and verify connections, but adoption value is limited by the lack of bundled examples, scripts, or richer task-specific workflows.
- Frontmatter clearly names the required MCP dependency (`rube`) and describes the intended trigger: automating Exist tasks through Composio/Rube MCP.
- Provides concrete setup prerequisites, including checking `RUBE_SEARCH_TOOLS`, using `RUBE_MANAGE_CONNECTIONS`, and confirming the Exist connection is ACTIVE before execution.
- Emphasizes tool discovery first, which should reduce schema drift and help agents call current Exist tools more safely than a static prompt.
- Depends entirely on an external Rube MCP server and an active Exist connection; there are no bundled scripts, resources, or local validation assets.
- Workflow guidance is generic and schema-discovery-driven, so users still need to rely on RUBE_SEARCH_TOOLS for exact Exist operations rather than follow fully worked examples.
Overview of exist-automation skill
What exist-automation is for
exist-automation is a Claude skill for running Exist operations through Composio’s Rube MCP server. Exist is a personal analytics and tracking platform, and this skill helps an agent discover the current Exist toolkit tools, confirm the user’s connection, and execute workflow automation tasks with the right schema instead of guessing tool names or parameters.
Best-fit users and workflows
The exist-automation skill is best for users who already use Exist and want an AI assistant to help automate account-connected tasks through MCP. It fits workflows such as checking available Exist actions, preparing structured updates, coordinating repeated tracking tasks, or asking an agent to operate against Exist after authorization. It is especially useful when your assistant environment supports MCP tools and you want a repeatable pattern for safe tool discovery before execution.
Main differentiator: schema discovery first
The key behavior is not a fixed list of Exist commands. The skill explicitly instructs the agent to call RUBE_SEARCH_TOOLS first so it can retrieve current tool slugs, input schemas, execution plans, and pitfalls from Rube. That matters because Composio tool schemas can change, and ordinary prompts often fail by assuming stale parameter names.
Adoption requirements to check first
Before installing exist-automation for Workflow Automation, confirm that your AI client can use MCP, that Rube MCP is configured, and that an Exist connection can be activated through RUBE_MANAGE_CONNECTIONS. If your environment cannot expose MCP tools to the assistant, this skill will read like guidance but will not be able to perform authenticated Exist actions.
How to Use exist-automation skill
exist-automation install and setup context
Install the skill in a skills-compatible Claude environment, for example:
npx skills add ComposioHQ/awesome-claude-skills --skill exist-automation
Then add Rube MCP as an MCP server in your client configuration using:
https://rube.app/mcp
The upstream skill states that no API key is needed for the MCP endpoint itself. After MCP is available, the assistant should verify that RUBE_SEARCH_TOOLS responds, then call RUBE_MANAGE_CONNECTIONS with toolkit exist. If the connection is not ACTIVE, complete the returned auth link and re-check status before asking for actual Exist operations.
Inputs the skill needs from you
For good exist-automation usage, give the assistant a concrete Exist outcome, not just “use Exist.” Useful input includes:
- The exact task: create, retrieve, update, summarize, or inspect an Exist-related item.
- The time range or date boundaries, if relevant.
- Whether the assistant should only draft a plan or actually call tools.
- Any field values you already know.
- Any constraints, such as “do not modify anything until I approve.”
Weak prompt:
Check my Exist.
Stronger prompt:
Use exist-automation to discover the current Exist tools, confirm my
existconnection is active, then find what operations are available for updating today’s tracking data. Do not execute a write action until you show me the tool name, required fields, and planned payload.
The stronger version improves safety because it separates discovery, connection validation, and execution approval.
Recommended workflow for reliable execution
A practical exist-automation guide should follow this order:
- Invoke the skill by naming the goal and mentioning Exist.
- Ask the assistant to run
RUBE_SEARCH_TOOLSfor the specific use case, not a generic search. - Keep the same Rube session when moving from discovery to execution.
- Confirm the
existtoolkit connection withRUBE_MANAGE_CONNECTIONS. - Review the returned schema and required fields.
- Execute only after required inputs are complete.
Example discovery request the skill is designed around:
RUBE_SEARCH_TOOLS
queries: [{use_case: "update today's Exist tracking data"}]
session: {generate_id: true}
After that, the assistant should use the returned tool names and schemas, not invented API details.
Repository files to read before install
The source is compact: start with composio-skills/exist-automation/SKILL.md. There are no bundled scripts, reference folders, README, or metadata files in the skill directory, so the decision mostly depends on whether the instructions match your MCP setup. Pay close attention to the requires: mcp: [rube] frontmatter and the prerequisites section. For toolkit behavior outside the skill, check Composio’s Exist toolkit documentation at https://composio.dev/toolkits/exist.
exist-automation skill FAQ
Is exist-automation enough without Rube MCP?
No. The exist-automation skill is a routing and workflow instruction layer for an MCP-capable assistant. It depends on Rube MCP tools, especially RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS. Without those tools available in the client, the assistant can explain what to do but cannot perform connected Exist automation.
How is this different from a normal prompt?
A normal prompt may ask the model to “use Exist,” but the model may not know the current Composio tool schema. This skill forces a safer pattern: search available tools first, inspect schemas, verify connection status, and then execute. That makes it more reliable for Workflow Automation where incorrect field names or unauthenticated calls would block the task.
Is exist-automation beginner-friendly?
It is beginner-friendly if your AI client already supports MCP configuration. The Exist-side authorization flow is handled through RUBE_MANAGE_CONNECTIONS, but the user still needs to understand that tool access must be active before automation works. If you are new to MCP, expect the first setup to take longer than the actual Exist task.
When should I not use this skill?
Do not use exist-automation when you only need general advice about habit tracking, when you cannot connect Exist through Composio, or when you need a fully custom integration with code-level control. It is also not ideal for blind write operations; ask the assistant to show the discovered schema and planned payload before changing data.
How to Improve exist-automation skill
Improve exist-automation results with better prompts
The fastest way to improve exist-automation output is to state the intended action, permission level, and success condition. For example:
Discover the current Exist tools for retrieving recent data, verify my connection, then summarize what read-only actions are available. Stop before any write operation.
This tells the assistant which use case to search for, whether writes are allowed, and what counts as a complete answer.
Avoid common failure modes
The most common failure is skipping tool discovery and assuming a schema. If the assistant proposes a tool call before RUBE_SEARCH_TOOLS, redirect it. Another failure is attempting execution before the exist connection is ACTIVE. A third is vague task wording, which can return broad tool suggestions instead of the exact operation you need.
Iterate after the first tool response
After discovery, use the returned schema to tighten your request. If a tool requires a date, metric, note field, or identifier, provide it explicitly. If Rube returns multiple possible execution plans, ask the assistant to compare them and choose the lowest-risk option. For write actions, request a preview of the payload before approving the call.
What maintainers could add next
The upstream skill would be stronger with a short README, example end-to-end prompts, and a few read-only versus write-action patterns. It could also include troubleshooting notes for inactive connections, expired authorization, and ambiguous tool discovery results. Until then, users should rely on SKILL.md, Rube’s returned schemas, and the Composio Exist toolkit docs for the latest operational details.