Skill470 repo starsupdated 3d ago

appcircle-automation

The appcircle-automation skill enables automation of Appcircle CI/CD tasks through Composio's toolkit via Rube MCP. Use this skill when you need to programmatically manage Appcircle workflows, builds, or deployments by first discovering available tools with RUBE_SEARCH_TOOLS, verifying an active Appcircle connection through RUBE_MANAGE_CONNECTIONS, and executing operations with RUBE_MULTI_EXECUTE_TOOL using current tool schemas.

View source Repository: openteams

Install in Claude Code

Copy

git clone --depth 1 https://github.com/openteams-lab/openteams /tmp/appcircle-automation && cp -r /tmp/appcircle-automation/assets/skills/appcircle-automation ~/.claude/skills/appcircle-automation

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Appcircle Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/appcircle](https://composio.dev/toolkits/appcircle)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Appcircle connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appcircle`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appcircle`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Appcircle 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 Appcircle task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["appcircle"]
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 Appcircle-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appcircle` |
| 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](https://composio.dev)*