What is the purpose of searching tools first?

Tool schemas can change; searching ensures you use the current tool slugs and input fields.

How do I know when the Netlicensing connection is ready?

Check RUBE_MANAGE_CONNECTIONS; the toolkit must show ACTIVE before executing any tool.

Why must I include memory in execute calls?

The memory parameter is required by RUBE_MULTI_EXECUTE_TOOL; include it even if it’s empty to maintain schema compliance.

labs64-netlicensing-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Labs64 Netlicensing Automation via Rube MCP

Automate Labs64 Netlicensing operations through Composio's Labs64 Netlicensing toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/labs64_netlicensing

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Labs64 Netlicensing connection via RUBE_MANAGE_CONNECTIONS with toolkit labs64_netlicensing
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 labs64_netlicensing
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: "Labs64 Netlicensing 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 Labs64 Netlicensing task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["labs64_netlicensing"]
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 Labs64 Netlicensing-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `labs64_netlicensing`
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/labs64-netlicensing-automation/SKILL.md

View on GitHub

Overview

This skill automates Labs64 Netlicensing tasks using Composio's Rube MCP and the labs64_netlicensing toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any workflow, and validating the active Netlicensing connection with RUBE_MANAGE_CONNECTIONS. Following these steps ensures resilient, schema-accurate automation.

How This Skill Works

Prerequisites must be met: Rube MCP connected and the labs64_netlicensing toolkit available. The workflow starts by discovering tools with RUBE_SEARCH_TOOLS, then verifying the Netlicensing connection via RUBE_MANAGE_CONNECTIONS. Finally, tools are executed through RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, exact input fields from the schema, a memory payload, and a session_id.

When to Use It

When you need to automate a Labs64 Netlicensing operation and must first fetch current tool schemas
When you must verify the Netlicensing connection is ACTIVE before running workflows
When you want to discover available tools and their input schemas before execution
When you execute a tool via RUBE_MULTI_EXECUTE_TOOL with memory and session context
When performing bulk operations or tooling via RUBE_REMOTE_WORKBENCH or need full tool schemas

Quick Start

Step 1: Add and verify Rube MCP endpoint (e.g., https://rube.app/mcp) and ensure RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit 'labs64_netlicensing' and complete any auth flow; confirm ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover a Lab64 Netlicensing task, then run RUBE_MULTI_EXECUTE_TOOL with the required inputs and memory

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas; never hardcode tool slugs or args
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing any tool
Adhere strictly to the field names and types shown in the tool schemas
Always include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls (even if empty `{}`)
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Discover a Labs64 Netlicensing task tool, then issue a license using the discovered slug and required inputs
Connect to labs64_netlicensing, ensure ACTIVE status, and run a batch update across multiple licenses
Perform bulk Netlicensing operations via RUBE_REMOTE_WORKBENCH using run_composio_tool()
Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS and adapt inputs for a custom automation
Implement a session-per-workflow pattern to manage several related Netlicensing tasks sequentially

Frequently Asked Questions

Add this skill to your agents