radar-automation

Automate Radar operations through the Rube MCP gateway for structured tool execution.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill radar-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: radar-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/radar-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill radar-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing Radar operations by providing a standardized, automated interface for tool discovery and execution, eliminating manual configuration errors.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetch current tool schemas and execution plans via Rube MCP.
  • Connection Management: Verify and maintain active Radar connections to ensure reliable workflow execution.
  • Multi-Tool Execution: Execute complex Radar workflows using a unified interface for tool calls and memory management.

Quick Start

Use the radar-automation skill to search for available tools and execute a specific Radar task.

Frequently Asked Questions about radar-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Radar tools?

Call the RUBE_SEARCH_TOOLS function with a specific use case query to retrieve current tool slugs, input schemas, and execution plans.

What should I do if my Radar connection is not active?

Use the RUBE_MANAGE_CONNECTIONS tool with the radar toolkit to check status and follow the provided authentication link to re-establish an active connection.

Why must I call RUBE_SEARCH_TOOLS before executing a task?

Tool schemas and slugs change frequently; calling RUBE_SEARCH_TOOLS ensures you are using the most current, valid arguments and preventing execution errors.

Can I reuse session IDs for different workflows?

No, you should generate new session IDs for distinct workflows to maintain state isolation, though you should reuse the same session ID within a single multi-step workflow.