Skill

show-nats-status

Show the current status of the Claude Code NATS agent — connection info, NATS URL, and all discovered agents with their capabilities. Use when the user says "nats status", "show nats agents", "what agents are connected", or wants to see the agent network state.

Install

npx claudepluginhub cameri/claude-skills --plugin nats

Tool Access

This skill is limited to using the following tools:

ReadBash(cat *)Bash(ls *)

Preview

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.0k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 24, 2026

Actions

View Source View Plugin View on GitHub View README

<objective> Shows the connection state of the local NATS agent and all known agents from the local cache. The NATS MCP server is managed automatically by Claude Code via the channel feature — no manual start/stop needed. </objective>

<quick_start> /nats:show-nats-status </quick_start>

<workflow> **1. Configuration:**

Read ~/.claude/channels/nats/.env if it exists. Show:

NATS_URL: value or "(not configured — using defaults: nats://nats:4222, nats://nats-server:4222)"

2. This agent's ID:

Read ~/.claude/skills/nats/agent-id if it exists. Show the agent ID, or "(not yet assigned — the channel server assigns one on first run)".

3. MCP server and connection:

Use the get_agents MCP tool to check whether the NATS MCP server is connected. If the tool call succeeds, the server is running and NATS is reachable. If it fails, note that the channel may not be active — the user can restart Claude Code with --channels plugin:nats@claude-skills.

4. Discovered agents:

Display the result of get_agents. For each agent:

Agent ID
Name
Last seen (ISO timestamp)
Capabilities (type + name + description)

Format as a structured list. If the cache is empty, suggest running /nats:discover-agents to scan the network.

5. Hint:

Agent cache is at ~/.claude/channels/nats/agents.json. Run /nats:discover-agents for a live scan of all connected agents. </workflow>

<success_criteria>

NATS URL and agent ID displayed (or clear not-configured messages)
Agent list from cache shown with capabilities
MCP server connectivity confirmed or failure explained
User knows next step (discover if cache empty, reconfigure if URL missing) </success_criteria>