Do I need API keys to use this skill?

No API keys are required for MCP usage; you simply configure the rube MCP endpoint.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas change over time, so you should fetch current slugs and argument names to avoid failures.

What if the connection is not ACTIVE?

Complete the authentication flow via the provided link and retry until RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows.

hackernews-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Hackernews Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hackernews

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["hackernews"]
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 Hackernews-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `hackernews`
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/hackernews-automation/SKILL.mdView on GitHub

Overview

Automate Hackernews operations through Composio's Hackernews toolkit via Rube MCP. The workflow emphasizes discovering available tools and their schemas with RUBE_SEARCH_TOOLS before execution, and ensuring an active connection with RUBE_MANAGE_CONNECTIONS. This enables dynamic tool selection, reliable authentication, and memory backed sessions across steps.

How This Skill Works

Technically you first discover available Hackernews tools using RUBE_SEARCH_TOOLS for a given use case. Then you verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS. Finally you execute a tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool_slug, the required arguments, a session_id, and a memory object.

When to Use It

Discover and run the right Hackernews tool for a task by dynamically querying schemas first.
Validate the Hackernews connection is ACTIVE before executing any workflow.
Run multi-step workflows in a single session with memory preserved between steps.
Adapt to tool schema changes by re querying tools before runs rather than hardcoding slugs.
Handle large results with pagination by checking tokens and continuing fetches.

Quick Start

Step 1: Add the Rube MCP endpoint in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with the hackernews toolkit and ensure the session shows ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools for your use case, then run RUBE_MULTI_EXECUTE_TOOL with the chosen slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first before any run to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the tool schemas in your arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse a session ID within a workflow and generate a new one for new workflows.

Example Use Cases

Automate a daily Hackernews digest by discovering tools, fetching top stories, summarizing, and storing the result in a repo.
Run a multi-step workflow to fetch a story and its comments, then analyze sentiment within a single session.
Fetch all pages of top stories by handling pagination tokens until completion.
Keep automation resilient to changes by always re querying tool schemas before execution.
Maintain context across steps by reusing a session_id when chaining multiple tools.

Frequently Asked Questions

Add this skill to your agents