ko-fi-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/ko-fi-automation --openclawKo Fi Automation via Rube MCP
Automate Ko Fi operations through Composio's Ko Fi toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/ko_fi
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Ko Fi connection via
RUBE_MANAGE_CONNECTIONSwith toolkitko_fi - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitko_fi - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Ko Fi operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Ko Fi task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["ko_fi"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Ko Fi-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit ko_fi |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/ko-fi-automation/SKILL.mdView on GitHub Overview
Automate Ko Fi operations using Composio's Ko Fi toolkit through Rube MCP. Always fetch current tool schemas with RUBE_SEARCH_TOOLS before running workflows to avoid broken slugs or arguments. This approach speeds up Ko Fi tasks and reduces errors by aligning with live tool schemas.
How This Skill Works
Connect Rube MCP and ensure a Ko Fi connection via RUBE_MANAGE_CONNECTIONS with toolkit ko_fi. Discover available tools with RUBE_SEARCH_TOOLS, then verify the connection status before executing. Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and proper arguments, always including memory and the current session_id.
When to Use It
- You need to automate a Ko Fi operation using a tool discovered via RUBE_SEARCH_TOOLS.
- You are setting up a new Ko Fi workflow and must validate the Ko Fi connection is ACTIVE.
- You want to execute a discovered Ko Fi tool with input that matches the live schema.
- You want to reuse a session ID across steps to optimize retries within a Ko Fi workflow.
- You need to perform bulk Ko Fi actions using RUBE_REMOTE_WORKBENCH and run_composio_tool.
Quick Start
- Step 1: Add Rube MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Use RUBE_SEARCH_TOOLS with use_case 'Ko Fi operations' to discover tools and start a session.
- Step 3: Check the Ko Fi connection with RUBE_MANAGE_CONNECTIONS, then run RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and memory.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas; never hardcode slugs or arguments.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
- Follow the exact field names and types from the search results to ensure schema compliance.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones for new workflows; monitor pagination in tool searches.
Example Use Cases
- Discover Ko Fi tools for a donation-update workflow and execute the appropriate tool with the returned schema.
- Establish a Ko Fi connection, verify ACTIVE, then run a tool to update a Ko Fi profile using live input fields.
- Execute multiple Ko Fi operations in sequence via RUBE_MULTI_EXECUTE_TOOL with a shared session_id.
- Reuse a single session across steps to perform a coordinated Ko Fi task with minimal retries.
- Bulk-run Ko Fi tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool for batch processing.
