y-gy-automation
Выполняет задачи в Y Gy через Rube MCP от Composio: подключает аккаунт, находит актуальные инструменты и запускает нужные действия.
Установка
npx skills add https://github.com/ComposioHQ/awesome-claude-skills/tree/be2a406907dbc61b73e6827ded415c96139d13a2/composio-skills/y-gy-automationСтавит скилл в текущий проект - CLI спросит, для каких агентов. С флагом -g - в домашнюю папку, для всех проектов. Другие способы
Установи скилл «y-gy-automation» из https://github.com/ComposioHQ/awesome-claude-skills/tree/be2a406907dbc61b73e6827ded415c96139d13a2/composio-skills/y-gy-automation: скопируй эту папку целиком в .claude/skills/y-gy-automation (для Codex - в .agents/skills/y-gy-automation). Потом прочитай SKILL.md и коротко скажи, в каких задачах будешь его применять.
Вставьте в Claude Code или Codex, открытый в папке проекта.
В Библиотеке ВайбКода этот скилл открывает исходник: автоматической установки для его формата пока нет. Поставьте командой или промптом.
Скачать ВайбКод · Windows и macOS
Описание автора
Automate Y Gy tasks via Rube MCP (Composio). Always search tools first for current schemas.
SKILL.md
СкачатьИсходник на GitHubY 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_CONNECTIONSwith toolkity_gy - 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 toolkity_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_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 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