Skill

relay-status

Use when you need to check the health and status of the relay server.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin agent-relay

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Query and display the relay server's operational status, including version, uptime, session count, and blob storage metrics.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitMay 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Relay Status

Query and display the relay server's operational status, including version, uptime, session count, and blob storage metrics.

When to use

Verifying the relay is online and healthy

Debugging connection issues

Monitoring relay load and resource usage

Confirming the client is properly connected

Inputs to gather

None — the skill reads the relay configuration from the local client.toml file.

Procedure

Load the relay URL and client_id from ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/agent-relay/client.toml.

Call the relay_status MCP tool.

Extract and render: server version, uptime, session count, total message count, blob count, total blob storage (bytes).

Optionally display per-client cursor positions and last-seen timestamp.

Print in a clear, structured format (e.g., table or YAML).

Output / side effects

Status report printed to stdout.

No local state changes.

If the relay is unreachable, report the error and suggest troubleshooting steps (check network, verify URL, etc.).

Safety / constraints

This is a read-only operation; no side effects on the relay.

Cursor data is per-session; only shows aggregated metrics if the relay's relay_status tool includes them.

Relay Status

Query and display the relay server's operational status, including version, uptime, session count, and blob storage metrics.

When to use

Verifying the relay is online and healthy
Debugging connection issues
Monitoring relay load and resource usage
Confirming the client is properly connected

Inputs to gather

None — the skill reads the relay configuration from the local client.toml file.

Procedure

Load the relay URL and client_id from ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/agent-relay/client.toml.
Call the relay_status MCP tool.
Extract and render: server version, uptime, session count, total message count, blob count, total blob storage (bytes).
Optionally display per-client cursor positions and last-seen timestamp.
Print in a clear, structured format (e.g., table or YAML).

Output / side effects

Status report printed to stdout.
No local state changes.
If the relay is unreachable, report the error and suggest troubleshooting steps (check network, verify URL, etc.).

Safety / constraints

This is a read-only operation; no side effects on the relay.
Cursor data is per-session; only shows aggregated metrics if the relay's relay_status tool includes them.