Do I need an API key to use nasa-automation?

No API keys are required; connect Rube MCP and the NASA toolkit via RUBE_MANAGE_CONNECTIONS.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas change; you must fetch current tool slugs and input schemas before executing.

What if the NASA connection isn't ACTIVE?

Complete the authentication flow shown by the returned auth link and ensure ACTIVE before running workflows.

nasa-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Nasa Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/nasa

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate NASA operations through Composio's NASA toolkit using Rube MCP. It emphasizes discovering current tool schemas before execution to avoid hardcoding. The setup requires a connected Rube MCP and an active NASA connection.

How This Skill Works

Connect to Rube MCP, search for tool schemas with RUBE_SEARCH_TOOLS, and verify an ACTIVE NASA connection via RUBE_MANAGE_CONNECTIONS. Then execute tools using RUBE_MULTI_EXECUTE_TOOL with schema-compliant arguments and a memory payload.

When to Use It

Automating recurring NASA operations via Rube MCP.
Need current tool schemas before execution (avoid hardcoding).
Orchestrating tool discovery, connection, and execution in a single workflow.
Validating ACTIVE NASA connection prior to running tools.
Handling multi-tool batches with RUBE_MULTI_EXECUTE_TOOL and memory payload.

Quick Start

Step 1: Add the Rube MCP endpoint at https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["nasa"] and complete authentication if prompted; ensure status ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute them via RUBE_MULTI_EXECUTE_TOOL using a memory payload and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS before selecting tool slugs.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Use exact field names and types from search results to ensure schema compliance.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow to maintain continuity.

Example Use Cases

Discover tools for a NASA telemetry fetch and execute the appropriate tool with correct arguments.
Establish an ACTIVE NASA connection and run a workflow that checks status before execution.
Chain RUBE_SEARCH_TOOLS → RUBE_MANAGE_CONNECTIONS → RUBE_MULTI_EXECUTE_TOOL in a single task.
Regularly re-search tools to pick up updated schemas before running NASA operations.
Use RUBE_REMOTE_WORKBENCH to run multiple NASA tool calls in bulk.

Frequently Asked Questions

Add this skill to your agents