corrently-automation

Automate Corrently energy data operations through the Rube MCP gateway.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of manually interacting with Corrently APIs by providing a standardized, agent-driven interface for energy data management and task automation.

Core Features & Use Cases

  • Tool Discovery: Automatically fetch and validate current Corrently API schemas via Rube MCP.
  • Connection Management: Handle authentication and session state for secure, persistent API access.
  • Multi-Tool Execution: Execute complex, multi-step energy workflows using a single, unified command structure.

Quick Start

Use the corrently-automation skill to search for available tools and execute a data retrieval task for your connected account.

Frequently Asked Questions about corrently-automation

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

FAQPage Schema
How do I discover available Corrently tools?

Call the RUBE_SEARCH_TOOLS function with a Corrently-specific use case query to retrieve current tool slugs, input schemas, and execution plans.

How to check if my Corrently connection is active?

Use the RUBE_MANAGE_CONNECTIONS tool with the 'corrently' toolkit argument to verify the current session status and trigger re-authentication if necessary.

Can I execute multiple Corrently tools in one workflow?

Yes, use the RUBE_MULTI_EXECUTE_TOOL function to chain multiple operations together, ensuring you include the required memory parameter and a valid session ID.

Why should I always call RUBE_SEARCH_TOOLS first?

Tool schemas and API endpoints change frequently; calling RUBE_SEARCH_TOOLS ensures your agent uses the most current arguments and prevents execution errors.

What should I do if a tool execution fails?

Verify your connection status via RUBE_MANAGE_CONNECTIONS, ensure your arguments match the schema returned by the latest search, and check for pagination tokens in the response.