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

SKILL

rkvst-automation

Name: rkvst-automation
Author: Composio

Automate RKVST workflows via Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears primarily to be an open-source prompt/instruction wrapper, but it is intended to connect to remote services via Rube MCP and perform Rkvst operations. No direct malicious indicators are present in the provided material, and the source is a high-star open repository, so overall risk is low to moderate; actual capabilities and data flows depend on the connected Rube MCP and Rkvst integration.

CredentialsCaution

The material says the skill itself requires no API key, but it depends on an active `rkvst` connection established via `RUBE_MANAGE_CONNECTIONS` and an external auth flow. So the skill does not directly collect secrets itself, but real usage relies on third-party authorization, creating normal credential and misconfiguration risk.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and use Composio/Rube for tool discovery, connection management, and execution; it also links to composio.dev docs. This indicates network egress to declared third-party services, and Rkvst task inputs/metadata may transit those endpoints, but there is no evidence of unrelated or hidden destinations.

Code executionLow risk

The system flags this as `prompt-only`, and the provided content is mainly workflow guidance and tool-calling order. It does not include local script installation, shell execution, or requests for system-level privileges. Based on the skill material itself, it does not grant local code execution.

Data accessCaution

This skill is intended to perform Rkvst-related operations and requires session reuse plus passing arguments, memory, and connection status data; therefore task data, session identifiers, and execution parameters may be handled by remote tools. The material does not claim local file read/write or clearly excessive data access beyond Rkvst/connection management, but the effective data scope depends on the actual toolset exposed by Rube/Composio.

Supply chainLow risk

The source is an open GitHub repository, the system marks it as `open-source`, and community trust is high (64.7k stars), all of which are strong risk-reducing factors. The material shows no obfuscated installation, suspicious download commands, domain mismatch, or obvious injection content; drawbacks are that the license is unspecified and maintenance status is unknown, which should be verified before production use.

Recommendations

Enable this skill only after confirming trust in `rube.app`, Composio, and the actual Rkvst authorization flow.
Use least-privilege authorization for the `rkvst` connection and regularly review/revoke unused connections.
Log RUBE tool calls and outbound destinations at the client or gateway level to ensure data transfer stays within expectations.
Before production use, verify repository maintenance activity, licensing, and the privacy/security documentation of the dependent MCP services.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Rkvst Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/rkvst

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["rkvst"]
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 Rkvst-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `rkvst`
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 Timekit tasks via Rube MCP with schema lookup first.

ComposioGet→

$ loading_