$ ~/registry/skill/composiohq-composio-skills-yandex-automation

SKILL

yandex-automation

Name: yandex-automation
Author: Composio

Automate Yandex 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 appears to be prompt-only and open source, but it is intended to drive Yandex operations through the remote Rube MCP/Composio stack, so the overall posture is caution rather than high risk. The material does not request local API keys and does not show local code execution or direct file access, but it does introduce normal third-party network egress and delegated authorization flows.

CredentialsCaution

The material says no API keys are needed, but it requires an ACTIVE Yandex connection via `RUBE_MANAGE_CONNECTIONS` and an auth link flow, which implies Yandex authorization tokens are still delegated to or mediated by a third-party service. No details are given about token scope, storage, or least-privilege controls.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio's Yandex toolkit for search, connection management, and tool execution. User task content, parameters, and session IDs are therefore likely sent to this third-party service. The endpoint is aligned with the stated function, so this is normal egress rather than a red flag, but data flow and retention are not described.

Code executionLow risk

Based on the material, this is a prompt-only guide and does not include local install scripts, shell commands, or process-spawning behavior. It invokes remote MCP tool interfaces rather than directly requesting local system execution privileges.

Data accessCaution

There is no indication of direct local file read/write access, but it can operate on resources in the user's authorized Yandex account through remote tools. The actual data access scope depends on the discovered tool schemas and granted permissions, and the material does not define those boundaries in detail.

Supply chainLow risk

The source is a GitHub open-source repository with strong community trust (~64.9k stars), which materially lowers supply-chain risk. What is shown here is a skill description rather than an executable package. Remaining caveats are the missing license declaration, unknown maintenance status, and the need to separately assess the underlying Rube/Composio services.

Recommendations

Before linking Yandex, verify Rube/Composio privacy terms, token handling, and data retention policies.
Use a least-privilege Yandex account and regularly review or revoke third-party connections.
Inspect the exact tool schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid broader-than-expected data actions.
If possible, limit this skill to low-sensitivity data or a 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 "yandex-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/yandex-automation/SKILL.md
2. Save it as ~/.claude/skills/yandex-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Yandex Automation via Rube MCP

Automate Yandex operations through Composio's Yandex toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/yandex

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["yandex"]
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 Yandex-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `yandex`
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 Amazon tasks through Rube MCP after checking current tool schemas.

ComposioGet→

$ loading_