What is acculynx-automation?

An automation skill to automate Acculynx tasks via Rube MCP (Composio) toolkits.

Why should I always search tools first?

Tool schemas change; RUBE_SEARCH_TOOLS ensures you use current slugs and fields.

How do I confirm the connection is ready?

Call RUBE_MANAGE_CONNECTIONS with toolkit 'acculynx' and check that status is ACTIVE before executing any tools.

acculynx-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/acculynx-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Acculynx Automation via Rube MCP

Automate Acculynx operations through Composio's Acculynx toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/acculynx

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Acculynx connection via RUBE_MANAGE_CONNECTIONS with toolkit acculynx
Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit acculynx
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: "Acculynx 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 Acculynx task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["acculynx"]
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_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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 Acculynx-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `acculynx`
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/acculynx-automation/SKILL.mdView on GitHub

Overview

Automate Acculynx operations using Composio's Acculynx toolkit through Rube MCP. It streamlines setup, discovery of current tool schemas, and execution of Acculynx tasks, ensuring workflows stay aligned with evolving schemas.

How This Skill Works

First, confirm RUBE_SEARCH_TOOLS to fetch current tool schemas. Then establish an active Acculynx connection via RUBE_MANAGE_CONNECTIONS with the acculynx toolkit. Finally, execute discovered tools using RUBE_MULTI_EXECUTE_TOOL with the required arguments and a memory payload, reusing sessions where appropriate.

When to Use It

Automating routine Acculynx tasks that repeat across claims (e.g., document uploads, status updates).
When tool schemas change frequently and you need up-to-date slugs and fields.
When you must confirm an ACTIVE connection before running any workflow.
When you want to reuse a session across multiple steps to improve efficiency.
For bulk operations on multiple Acculynx tasks using remote bench workflows.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Confirm RUBE_SEARCH_TOOLS responds to fetch current Acculynx tool schemas.
Step 3: Manage the Acculynx connection and execute tools with RUBE_MULTI_EXECUTE_TOOL, ensuring ACTIVE status and proper memory payload.

Best Practices

Always call RUBE_SEARCH_TOOLS first to pull current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results.
Always include memory in RUBE_MULTI_EXECUTE_TOOL, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover Acculynx tools for a new claim automation and execute a task with the correct slug and fields.
Fetch the latest Acculynx tool schemas via RUBE_SEARCH_TOOLS and run a task with updated arguments.
Verify the Acculynx connection is ACTIVE using RUBE_MANAGE_CONNECTIONS before executing a tool in a workflow.
Execute several Acculynx operations in a single session using RUBE_MULTI_EXECUTE_TOOL with a memory payload.
Perform a bulk set of Acculynx tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool() for efficiency.

Frequently Asked Questions

Add this skill to your agents