piggy-automation

Automate Piggy platform tasks using Rube MCP toolkits and schema-compliant execution workflows.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill piggy-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: piggy-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/piggy-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill piggy-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the complexity of interacting with Piggy platform APIs by providing a standardized, schema-aware workflow that ensures tool calls are always valid and connections are active.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetches current tool schemas to prevent execution errors caused by API changes.
  • Connection Management: Validates and maintains active Piggy connections via Rube MCP before executing tasks.
  • Use Case: Automate repetitive Piggy operations by discovering available tools, verifying the connection status, and executing multi-step workflows in a single session.

Quick Start

Use the piggy-automation skill to discover available tools and execute a task for your specific Piggy workflow.

Frequently Asked Questions about piggy-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find available Piggy tools?

Call the RUBE_SEARCH_TOOLS command with a specific use case query to retrieve current tool slugs, input schemas, and execution plans for Piggy operations.

What should I do if my Piggy connection is inactive?

Use the RUBE_MANAGE_CONNECTIONS command with the 'piggy' toolkit to trigger the authentication flow and verify that the connection status returns as ACTIVE.

Why must I call RUBE_SEARCH_TOOLS before executing a task?

Tool schemas and arguments change frequently; searching first ensures you use the correct, current field names and types required for successful execution.

Can I reuse session IDs for different workflows?

Reuse session IDs within a single, continuous workflow to maintain state, but generate new session IDs for distinct, unrelated tasks to avoid data contamination.

What is the purpose of the memory parameter in tool execution?

The memory parameter is a required field for RUBE_MULTI_EXECUTE_TOOL calls that enables state tracking; always include it as an empty object '{}' if no specific memory is needed.