What is Typefully Automation via Rube MCP?

It is automating Typefully tasks through Composio's toolkit using RUBE_SEARCH_TOOLS to fetch current tool schemas and RUBE_MULTI_EXECUTE_TOOL to run selected tools.

Do I need API keys to use this skill?

No API keys are required. You add the MCP server (e.g., https://rube.app/mcp), ensure RUBE_SEARCH_TOOLS is available, and manage connections with RUBE_MANAGE_CONNECTIONS for the Typefully toolkit.

What are the common pitfalls to avoid?

Always search tools first because schemas change; ensure the connection is ACTIVE; use exact field names from search results; include memory in execute calls; reuse session IDs where appropriate and handle pagination when discovering tools.

typefully-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/typefully-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Typefully Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/typefully

Prerequisites

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

Step 2: Check Connection

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/typefully-automation/SKILL.mdView on GitHub

Overview

Automate Typefully operations through Composio's toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and requires an active Typefully connection managed by RUBE_MANAGE_CONNECTIONS. This approach keeps tooling up-to-date and avoids hardcoded slugs.

How This Skill Works

You verify connectivity by calling RUBE_SEARCH_TOOLS, then establish and confirm an ACTIVE Typefully connection with RUBE_MANAGE_CONNECTIONS. Next, you discover available tools and their input schemas, then execute a selected tool using RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id. The workflow relies on current tool schemas returned by RUBE_SEARCH_TOOLS to prevent schema drift.

When to Use It

Automating recurring Typefully operations like generating and posting threads on a schedule.
Initializing a new Typefully workflow and validating up-to-date tool schemas before run.
Batch-running multiple Typefully tasks in a single session using RUBE_MULTI_EXECUTE_TOOL.
Testing or debugging Typefully tasks by comparing behavior against current tool schemas.
Migrating existing Typefully automations to use fresh tool schemas without hardcoding slugs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and ensure RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["typefully"] and complete auth if required; ensure ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to fetch current Typefully tool slugs and schemas, then run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty ({}).
Reuse session IDs within a workflow; generate new IDs for new workflows and watch for pagination.

Example Use Cases

Auto-generate and post a Typefully thread daily using discovered tool slug and schema.
Validate a new Typefully task by discovering tools and then executing with test inputs.
Batch-run several Typefully tasks (draft, schedule, publish) in one session.
Migrate an existing Typefully automation to use up-to-date tool schemas from RUBE_SEARCH_TOOLS.
Handle large results by paging through tool-discovery responses until complete.

Frequently Asked Questions

Add this skill to your agents