$ ~/registry/skill/composiohq-composio-skills-y-gy-automation

SKILL

y-gy-automation

Name: y-gy-automation
Author: Composio

Automate Y Gy tasks and workflows through Rube MCP integrations.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself is an open-source prompt-style wrapper, but its documentation clearly depends on remote Rube MCP and Composio/Y Gy connections to discover and execute tools, so the overall posture is caution rather than high risk. No direct red flags for local secrets or local code execution are shown, but there is an external data/session handling surface via MCP that should be verified for actual authorization scope.

CredentialsCaution

The material states there are no local API keys, but it requires establishing an ACTIVE `y_gy` connection via `RUBE_MANAGE_CONNECTIONS` and completing authorization through a returned auth link; this implies credentials may live in the Rube/Composio connection layer rather than in the skill itself. No explicit request for local user secrets is shown; the main concern is external authorization scope and session handling.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and references `composio.dev` docs; tool discovery, connection management, and execution all occur through the remote MCP service, so task arguments, session IDs, and potentially business data are sent externally. The endpoints are relevant to the stated function, with no unrelated or covert exfiltration endpoints shown, so this is routine remote egress that warrants caution.

Code executionLow risk

The system marks this as `prompt-only`, and the material does not describe downloading, installing, running local scripts, or starting local processes; execution is framed as remote MCP tool invocation rather than local code execution. Based on the provided material, there is no sign of expanded local execution privileges.

Data accessCaution

The skill itself does not claim local file or system-resource access, but `RUBE_SEARCH_TOOLS`, `RUBE_MULTI_EXECUTE_TOOL`, and `RUBE_REMOTE_WORKBENCH` can pass user inputs, session information, and Y Gy-related business data into the remote toolchain. The document does not define the exact data boundaries of the y_gy toolkit, so least-privilege scope should be confirmed before authorization.

Supply chainLow risk

The source is an open GitHub repository, the system marks it as `open-source`, and community adoption is high (about 64.9k stars), all of which significantly reduce risk. Although the license is unspecified and maintenance status is unknown, and the repo appears to be a skills collection rather than a standalone implementation repo, the supply-chain posture is still relatively low risk due to auditability and source credibility.

Recommendations

Before enabling it, confirm which account, data scope, and actions the `y_gy` connection authorizes, and keep permissions minimal.
Treat task arguments sent to `rube.app/mcp` as leaving the local environment, and avoid sending unnecessary sensitive content.
Review Composio/Rube privacy, log-retention, and credential-handling practices, including how sessions and authorizations can be revoked.
For production use, validate the visible tool set and actual behavior first in an isolated or test account.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Y Gy Automation via Rube MCP

Automate Y Gy operations through Composio's Y Gy toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/y_gy

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Y Gy connection via RUBE_MANAGE_CONNECTIONS with toolkit y_gy
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 y_gy
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: "Y Gy 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 Y Gy task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["y_gy"]
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 Y Gy-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `y_gy`
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 YNAB budgeting tasks and data lookups through Rube MCP.

ComposioGet→

$ loading_