home / skills / composiohq / awesome-claude-skills / amcards-automation

amcards-automation skill

safe

/amcards-automation

This skill automates Amcards tasks via Rube MCP, ensuring tool schemas are fetched first and connections verified before execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill amcards-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: amcards-automation
description: "Automate Amcards tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Amcards Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["amcards"]
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 Amcards-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `amcards` |
| 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)*

Overview

This skill automates Amcards tasks through Composio's Amcards toolkit using the Rube MCP gateway. It streamlines discovery, connection management, and execution of Amcards tools while enforcing schema compliance and session handling. Designed for reliable, repeatable automation of Amcards workflows.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover current tool slugs and input schemas, RUBE_MANAGE_CONNECTIONS to ensure an active Amcards connection, and RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH) to run one or more tools. It always searches tools first, validates connection status, supplies memory and session IDs, and follows returned execution plans and pagination tokens.

When to use it

Automating routine Amcards operations (create, update, query cards) at scale
Orchestrating multi-step Amcards workflows that require several toolkit calls
Building integrations that must adapt to changing tool schemas
Running bulk operations or remote workbench jobs via Composio
Creating reliable CI/CD or scheduled jobs that interact with Amcards

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and exact input schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the amcards toolkit before executing
Include a memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs for a workflow; generate fresh sessions for new workflows
Handle pagination tokens and follow returned execution plans from search results

Example use cases

Discover available Amcards operations and run a create-card flow using discovered schema fields
Validate and refresh the Amcards connection, then perform a bulk update via RUBE_REMOTE_WORKBENCH
Orchestrate a multi-step card enrichment workflow that executes several composio tools in sequence
Automate scheduled exports of Amcards data, handling pagination and session reuse

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required.

What must I call before executing any tool?

Always call RUBE_SEARCH_TOOLS to obtain current tool slugs and full input schemas, then confirm connection via RUBE_MANAGE_CONNECTIONS.