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

SKILL

ritekit-automation

Name: ritekit-automation
Author: Composio

Automate Ritekit workflows through Rube MCP for faster social content operations.

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 an open-source prompt-style wrapper with strong community adoption, and the provided material shows no intrinsic local execution or embedded-secret red flags. The main caution is that it relies on remote Rube MCP/Composio connectivity and third-party Ritekit authorization, so actual data egress and permissions depend on the connected external toolchain.

CredentialsCaution

The material says the skill itself needs no API keys, but it requires an ACTIVE `ritekit` connection via `RUBE_MANAGE_CONNECTIONS` and an auth-link flow. This implies third-party account authorization/tokens are involved, just managed by the external MCP rather than configured directly in the skill; this creates normal delegated-credential and wrong-account connection considerations.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and invoking Ritekit tools through Composio/Rube; task arguments, session IDs, connection state, and execution content are therefore expected to be sent through that declared external service chain. This is normal networked-tool behavior, and the material does not show exfiltration to unrelated or hidden endpoints.

Code executionLow risk

The system flags it as `prompt-only`, and the content is mainly operational guidance and call ordering, with no install scripts, local command execution, shell snippets, or requests for elevated system privileges. Based on the material itself, it does not provide direct local code-execution capability.

Data accessCaution

The skill is intended to 'Automate Ritekit operations' and can execute remote tools via `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`; the exact data scope is not enumerated in the material and depends on the discovered Ritekit tool schemas and granted user authorization. There is no stated local file access, but the remote business-data access surface is not fully transparent and should be used with least privilege.

Supply chainLow risk

The source is an open GitHub repository, the system marks it `open-source`, and community adoption is high (~64.9k stars), all of which are strong risk-reducing signals. The license and maintenance status are unclear, and the skill depends on external Rube/Composio services and docs, but the current material does not show a concrete supply-chain red flag.

Recommendations

Verify the relationship between `rube.app/mcp`, Composio, and Ritekit before connecting, and ensure the authorization page uses the correct domain.
Grant only the minimum Ritekit account permissions needed, preferably using a test or low-sensitivity account for first-time setup.
Inspect the schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending sensitive content as unnecessary remote tool arguments.
Track and periodically review established external connections, and revoke Ritekit/Composio authorizations that are no longer needed.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Ritekit Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ritekit

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ritekit"]
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 Ritekit-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ritekit`
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_