What is required to begin automation?

A connected Rube MCP, an ACTIVE census_bureau connection, and tool schemas obtained via RUBE_SEARCH_TOOLS.

Should I always search for tools before running?

Yes. Tool slugs and input schemas can change, so fetch current definitions before execution.

How do I ensure a workflow is safe to run?

Verify ACTIVE status with RUBE_MANAGE_CONNECTIONS, reuse session IDs within a workflow, include memory in each RUBE_MULTI_EXECUTE_TOOL call, and strictly use the exact schema fields from the search results.

census-bureau-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Census Bureau Automation via Rube MCP

Automate Census Bureau operations through Composio's Census Bureau toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/census_bureau

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["census_bureau"]
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 Census Bureau-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `census_bureau`
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/census-bureau-automation/SKILL.md

View on GitHub

Overview

Census Bureau Automation via Rube MCP enables automated operations using Composio's census_bureau toolkit. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and an ACTIVE connection managed by RUBE_MANAGE_CONNECTIONS. This ensures workflows stay aligned with updated tool definitions and prevents hard-coded glitches.

How This Skill Works

First, discover available tools and their input schemas with RUBE_SEARCH_TOOLS. Then verify the census_bureau connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, and finally execute tools with RUBE_MULTI_EXECUTE_TOOL, passing memory and a session_id. Always include memory in calls and reuse session IDs within a workflow to maintain continuity.

When to Use It

Setting up a new Census Bureau workflow after establishing a Rube MCP connection
Running routine Census Bureau tasks using discovered tool slugs and schemas
Adapting to updated tool schemas by re-discovering tools with RUBE_SEARCH_TOOLS
Reusing a session across a multi-step census workflow
Performing bulk census operations via RUBE_REMOTE_WORKBENCH (run_composio_tool)

Quick Start

Step 1: Get Rube MCP by adding https://rube.app/mcp as an MCP server in your client configuration (no API keys needed).
Step 2: Verify RUBE_SEARCH_TOOLS responds and call RUBE_MANAGE_CONNECTIONS with toolkits: ["census_bureau"]; ensure the connection status is ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory: {}, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results (no hardcoding)
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and avoid creating new ones unnecessarily

Example Use Cases

Automate a monthly Census Bureau data pull by discovering tools and executing with current schemas
Validate a workflow after a tool schema update and re-run with new arguments
Perform bulk census operations using RUBE_REMOTE_WORKBENCH and run_composio_tool
Execute a multi-step census task reusing a single session_id across steps
Connect to the census_bureau toolkit and confirm ACTIVE status before execution

Frequently Asked Questions

Add this skill to your agents