ray-skill

Send structured JSON payloads to the Ray desktop debugging tool via its local HTTP API.

997|201|Updated May 6, 2014

Search Tags:#debugging #php #javascript #visualization #http #ray #payloads

Ready to run

npx skills add https://github.com/freekmurze/dotfiles --skill ray-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ray-skill
Source: https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/ray-skill
Command: npx skills add https://github.com/freekmurze/dotfiles --skill ray-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ray provides a straightforward way to visualize, inspect, and diagnose runtime data by sending structured payloads to the Ray desktop app over a local HTTP API. This enables developers to see logs, tables, and diagrams in real time without scattering debugging output across logs.

Core Features & Use Cases

Local HTTP API: Send JSON payloads to a running Ray instance on localhost:23517.
Payload Types: Supports log, table, color, label, and notify, enabling immediate visualization and debugging from PHP, Node.js, or other applications.
Use Case: Attach runtime telemetry or debugging outputs from PHP, Node.js, or other applications to Ray for interactive exploration and diagramming.

Quick Start

Start Ray on your desktop, ensure it is running and listening on http://localhost:23517/, and begin sending payloads from your app or via curl.

Frequently Asked Questions about ray-skill

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

FAQPage Schema

How do I send runtime data to Ray for visual debugging from PHP or Node.js?▼

To send runtime data to Ray for visual debugging, you send structured JSON payloads containing uuid, payloads, and optional meta to the local HTTP API at localhost:23517. This allows you to visualize logs and tables from PHP or Node.js in real time.

What is the best way to visualize runtime debugging output without cluttering application logs?▼

Visualizing runtime debugging output without cluttering application logs is done by sending structured payloads like log, table, color, and label directly to the Ray desktop app. This provides interactive exploration of telemetry over a local HTTP API.

Does visual debugging with Ray require a specific desktop environment or local server?▼

Visual debugging with Ray requires the Ray desktop application to be running and listening on your local machine at http://localhost:23517/. Your application sends JSON payloads to this local HTTP API endpoint to display the debugging output.

Can I send structured data like tables and custom labels to Ray for inspection?▼

Yes, you can send structured data like tables and custom labels to Ray for inspection. The skill supports common payload types including log, table, color, label, and notify, enabling immediate visualization and interactive exploration of your runtime data.

What payload types are supported when sending data to Ray over the local HTTP API?▼

The payload types supported when sending data to Ray over the local HTTP API include log, table, color, label, and notify. These payloads are structured using a simple JSON schema with a uuid, payloads array, and optional meta object.

Why use Ray for visual debugging instead of writing to standard application logs?▼

Using Ray for visual debugging instead of standard application logs prevents scattering debug output across text files. It enables developers to see logs, tables, and diagrams in real time, providing a straightforward way to inspect and diagnose runtime data visually.