Do I need API keys to use this skill?

No API keys are required. You only need to add the Rube MCP server endpoint and connect to Teamcamp.

Why should I always search tools first?

Tool schemas change over time. Fetch current slugs and input fields from RUBE_SEARCH_TOOLS before executing.

What if the connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup and ensure ACTIVE before running workflows.

teamcamp-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Teamcamp Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/teamcamp

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["teamcamp"]
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 Teamcamp-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `teamcamp`
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/teamcamp-automation/SKILL.mdView on GitHub

Overview

Automate Teamcamp operations using Composio's Teamcamp toolkit via Rube MCP. It emphasizes discovering current tool schemas first to avoid hardcoded slugs and arguments.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to fetch tool schemas, then RUBE_MANAGE_CONNECTIONS to prepare the Teamcamp connection, and finally RUBE_MULTI_EXECUTE_TOOL to run a chosen tool with the required arguments. A core workflow pattern is Discover Available Tools, Check Connection, and Execute Tools.

When to Use It

Automate routine Teamcamp operations like creating tasks, updating statuses, or bulk edits via Rube MCP.
When tool schemas change and you must fetch current slugs and input fields before execution.
When you need to verify that the Teamcamp connection is ACTIVE before running workflows.
When chaining multiple Teamcamp tools in a single session, reusing the session_id for continuity.
During bulk operations and pagination to fetch and process multiple Teamcamp items safely.

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS.
Step 2: Manage the Teamcamp connection with RUBE_MANAGE_CONNECTIONS and ensure the toolkit teamcamp is ACTIVE.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL using a memory object and your session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results to avoid schema errors.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new runs.

Example Use Cases

Auto create a daily standup task in Teamcamp by discovering the create_task tool and executing it with a due date.
Sync task statuses from an external system into Teamcamp by discovering and calling the update_status tool.
Bulk assign Teamcamp tasks to a team by discovering the assign_batch tool and executing with a list of task IDs.
Chain multiple Teamcamp operations in a single session by discovering tools, ensuring ACTIVE connection, and executing in sequence.
List Teamcamp tasks with pagination and process each item until all pages are fetched.

Frequently Asked Questions

Add this skill to your agents