perigon-automation

Automate Perigon platform operations through Rube MCP toolkits and structured execution workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing Perigon platform tasks by providing a standardized, automated interface for tool discovery, connection management, and multi-step execution.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetches current tool schemas and execution plans via Rube MCP to ensure compatibility.
  • Connection Management: Handles authentication and status verification for Perigon toolkits to prevent execution errors.
  • Workflow Automation: Enables complex, multi-step operations like bulk data processing or remote workbench tasks through a unified command structure.

Quick Start

Use the perigon-automation skill to search for available tools and execute a task for my specific Perigon workflow.

Frequently Asked Questions about perigon-automation

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

FAQPage Schema
How do I discover available Perigon tools?

Call the RUBE_SEARCH_TOOLS command with a specific use case query to retrieve current tool slugs, input schemas, and recommended execution plans for your Perigon tasks.

What should I do if my Perigon connection is inactive?

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

Can I reuse session IDs for multiple workflows?

No, you should generate new session IDs for distinct workflows to maintain state isolation, though you should reuse the same session ID within a single multi-step workflow.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas and slugs change frequently; calling RUBE_SEARCH_TOOLS ensures you are using the most current, valid arguments and prevents execution errors caused by outdated schemas.

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 maintains state context; it must be included in every call, even if passed as an empty object.