forcemanager-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/forcemanager-automation --openclawFiles (1)
SKILL.md
2.9 KB
Forcemanager Automation via Rube MCP
Automate Forcemanager operations through Composio's Forcemanager toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/forcemanager
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Forcemanager connection via
RUBE_MANAGE_CONNECTIONSwith toolkitforcemanager - 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 toolkitforcemanager - 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: "Forcemanager 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 Forcemanager task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["forcemanager"]
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 Forcemanager-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit forcemanager |
| 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/forcemanager-automation/SKILL.mdView on GitHub Overview
This skill automates Forcemanager operations through Composio's Forcemanager toolkit via Rube MCP. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and RUBE_MANAGE_CONNECTIONS to establish an active connection, ensuring workflows always use up-to-date controls.
How This Skill Works
Technically, you first discover current tool schemas with RUBE_SEARCH_TOOLS, then establish a connection via RUBE_MANAGE_CONNECTIONS for the forcemanager toolkit. Once a tool slug and its exact argument schema are known, you execute it with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id to maintain state.
When to Use It
- Automating recurring Forcemanager operations (e.g., creating or updating tasks) to save time and reduce manual steps.
- When tool schemas may change and you need the latest slugs and arguments fetched via RUBE_SEARCH_TOOLS.
- Before running workflows to ensure the Forcemanager connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
- For bulk or batch operations that run multiple tools in sequence using RUBE_MULTI_EXECUTE_TOOL.
- When you want to maintain state across a workflow by reusing session IDs rather than starting anew.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed.
- Step 2: Verify RUBE_SEARCH_TOOLS responds and returns Forcemanager tool schemas.
- Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit 'forcemanager' and confirm the connection status is ACTIVE before running workflows.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs.
- Verify the Forcemanager connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing any tools.
- Use exact field names and types from the search results; avoid improvising arguments.
- Include a memory payload in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
- Reuse session IDs within a workflow to maintain context; generate new IDs only for new workflows.
Example Use Cases
- Auto-create a Forcemanager task when a trigger occurs, using the discovered tool slug and its required arguments.
- Bulk update the statuses of multiple Forcemanager tasks in a single run with RUBE_MULTI_EXECUTE_TOOL and shared memory.
- Generate a weekly report by executing a sequence of Forcemanager tools after confirming ACTIVE connection.
- Fetch the latest available Forcemanager tools before executing any workflow to adapt to schema changes.
- Complete a multi-step workflow by reusing a session_id across tools to avoid repeated authentication.
Frequently Asked Questions
Add this skill to your agents
