sage-automation
Executes and manages Sage tasks via Rube MCP integration.
Install
mkdir -p .claude/skills/sage-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17019" && unzip -o skill.zip -d .claude/skills/sage-automation && rm skill.zipInstalls to .claude/skills/sage-automation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Automate Sage tasks via Rube MCP (Composio). Always search tools first for current schemas.Key capabilities
- →Automate Sage operations
- →Discover available Sage tools
- →Manage Sage connections
- →Execute Sage tools with schema-compliant arguments
- →Perform bulk operations in Sage
- →Retrieve full tool schemas
How it works
The skill automates Sage tasks by first discovering available tools via RUBE_SEARCH_TOOLS, then checking the connection status with RUBE_MANAGE_CONNECTIONS, and finally executing the tools using RUBE_MULTI_EXECUTE_TOOL with schema-compliant arguments.
Inputs & outputs
When to use sage-automation
- →Automating Sage platform tasks
- →Managing Sage tool connections
About this skill
Sage Automation via Rube MCP
Automate Sage operations through Composio's Sage toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/sage
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Sage connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsage - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitsage - 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: "Sage 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 Sage task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["sage"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Sage-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit sage |
| 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
When not to use it
- →When Rube MCP is not connected
- →When an active Sage connection is not established
Prerequisites
Limitations
- →Requires Rube MCP to be available and connected
- →Requires an active Sage connection
- →Tool schemas must be discovered before execution
How it compares
This skill provides a structured approach to automating Sage tasks by dynamically discovering tool schemas and managing connections through Rube MCP, rather than relying on static or manually configured tool interactions.
Compared to similar skills
sage-automation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sage-automation (this skill) | 0 | 5mo | No flags | Intermediate |
| zendesk | 15 | 4mo | Review | Intermediate |
| zapier-workflows | 11 | 9mo | Review | Beginner |
| controlling-spotify | 7 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by diegosouzapw
View all by diegosouzapw →You might also like
zendesk
vm0-ai
Zendesk Support REST API for managing tickets, users, organizations, and support operations. Use this skill to create tickets, manage users, search, and automate customer support workflows.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
controlling-spotify
oaustegard
Control Spotify playback and manage playlists via MCP server. Use when user requests playing music, controlling Spotify, creating playlists, searching songs, or managing their Spotify library.
smithery-ai-cli
smithery-ai
Find, connect, and use MCP tools and skills via the Smithery CLI. Use when the user searches for new tools or skills, wants to discover integrations, connect to an MCP, install a skill, or wants to interact with an external service (email, Slack, Discord, GitHub, Jira, Notion, databases, cloud APIs, monitoring, etc.).
connect-apps
ComposioHQ
Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.
freshdesk-automation
sickn33
Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.