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

SKILL

amcards-automation

Name: amcards-automation
Author: Composio

Automate Amcards workflows via Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily an open-source prompt/instruction wrapper, but it is designed to drive Amcards actions through the remote Rube MCP and a third-party Composio connection. No clear red flags for local execution or direct secret harvesting are shown, so the overall posture is mostly caution, with lower supply-chain concern due to open source and strong community adoption.

CredentialsCaution

The material says the skill itself needs no API key, but it requires an ACTIVE `amcards` connection via `RUBE_MANAGE_CONNECTIONS` and an external auth link. This implies third-party account authorization/tokens are involved, likely brokered by Rube/Composio, which creates normal delegated-credential risk.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using it for tool discovery, connection management, and execution. User task details, arguments, and possible business data may transit through that remote service to the relevant toolkit. The endpoint is declared and relevant, but it is still a real egress path.

Code executionLow risk

Based on the provided material, this is a prompt-style skill description and does not describe launching local processes, running scripts, or requesting system-level execution privileges by itself. Its behavior is mainly orchestrating calls to connected MCP tools.

Data accessCaution

The skill is intended to 'Automate Amcards operations' and supports executing discovered tools, bulk operations, and paginated retrieval. That generally implies access to business objects and results within the connected Amcards account. The material does not show local file access or obvious overbroad system permissions, but it does present a normal operational surface over third-party account data.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (~64.9k stars), both of which are meaningful risk-reducing signals. Although the license is unspecified and maintenance status is unknown, and the workflow depends on external Rube/Composio services, the skill material itself has relatively good auditability and source trust.

Recommendations

Only connect to `https://rube.app/mcp` and authorize your Amcards account if you trust Rube/Composio and their data-handling practices.
Use least-privilege accounts for authorization and regularly review/revoke Amcards/Rube connections you no longer need.
Validate discovered tool schemas and argument meanings before execution to avoid sending unnecessary sensitive business data into the remote toolchain.
Review the linked open-source repository and verify recent maintenance and release history where possible.

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 "amcards-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/amcards-automation/SKILL.md
2. Save it as ~/.claude/skills/amcards-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Amcards Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit amcards
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: "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

Automate Amazon tasks through Rube MCP after checking current tool schemas.

ComposioGet→

$ loading_