$ ~/registry/skill/composiohq-composio-skills-teamcamp-automation

SKILL

teamcamp-automation

Name: teamcamp-automation
Author: Composio

Automate Teamcamp task management and collaboration workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/documentation-only skill with no declared local execution, file access, or built-in secret requirements; combined with its GitHub source and strong community adoption, the overall risk is low. However, it is designed to connect users to a remote Rube MCP and then to Teamcamp/Composio, so actual data egress and authorization boundaries depend on the external MCP and third-party connection setup and warrant attention.

CredentialsCaution

The material states 'No API keys needed,' but it also requires establishing an ACTIVE Teamcamp connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link to complete setup. This means credentials are mainly handled through the external Rube/Teamcamp connection flow. The skill does not directly request secrets, but it does trigger third-party account authorization, which carries normal OAuth/connection-abuse exposure.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing operations through Composio/Teamcamp tools. Therefore, task content, tool discovery requests, execution arguments, and potentially business data will be sent to the stated third-party services. The endpoint is declared and relevant to the function, but this is a standard data-egress scenario.

Code executionLow risk

Based on the material, this is a prompt-only skill consisting mainly of workflow instructions and tool invocation patterns. It does not declare local process spawning, script execution, binary installation, or requests for system-level privileges.

Data accessLow risk

The skill itself does not declare reading or writing local files, accessing local directories, or requesting device/system data permissions. Its scope is mainly to invoke Teamcamp-related tools through a remote MCP. Based on the material alone, there is no sign of excessive local data access.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), which are clear risk-reducing signals. The license and maintenance status are not explicit, and the external Rube MCP/Composio services cannot be fully audited from this material alone, but the available facts are not enough to raise this to high risk.

Recommendations

Before connecting, verify the privacy policy, data handling scope, and account authorization scope of `https://rube.app/mcp`, Composio, and Teamcamp.
Use a least-privilege Teamcamp account for the connection, and regularly review and revoke third-party authorizations that are no longer needed.
Before production use, test with non-sensitive data to verify what fields and content are sent through `RUBE_SEARCH_TOOLS` and `RUBE_MULTI_EXECUTE_TOOL`.
Prefer pinned trusted repository versions and keep monitoring maintenance and updates for both the skill and the external MCP service.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "teamcamp-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/teamcamp-automation/SKILL.md
2. Save it as ~/.claude/skills/teamcamp-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Atlassian tasks and workflows through Rube MCP integrations.

ComposioGet→

$ loading_