Skill

discover-agents

Discover all Claude Code agents on the NATS network and list their capabilities. Use when the user says "discover agents", "who's on nats", "list nats agents", "find agents", or wants to see what agents are available.

Install

npx claudepluginhub cameri/claude-skills --plugin nats

Tool Access

This skill uses the workspace's default tool permissions.

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-editorial-review-prose

Reviews prose for communication issues impeding comprehension, outputs minimal fixes in a three-column table per Microsoft Writing Style Guide. Useful for 'review prose' or 'improve prose' requests.

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> Sends a discovery ping on `claude.discovery.ping` and collects pong responses for 3 seconds. All responding agents are listed with their capabilities. Results are cached to `~/.claude/channels/nats/agents.json`. </objective>

<quick_start> /nats:discover-agents

Pass a custom timeout for slow networks: /nats:discover-agents timeout=5000 </quick_start>

<workflow> Use the `discover` MCP tool (exposed by the NATS channel server):

discover(timeout_ms?: number)

Default timeout is 3000ms. Pass a larger value if the network is slow.

For each discovered agent:

Agent: <agentId>
  Name: <name>
  Last seen: <lastSeen>
  Capabilities (<count>):
    - [<type>] <name>: <description>
    ...

If no agents responded:

No agents discovered. Make sure other Claude Code instances are running with the NATS channel enabled and connected to the same NATS server.
</workflow>

<notes> The local agent is always included in the cache (it self-registers on startup) but won't appear in discover results unless another agent responds to the ping — the local agent does not respond to its own ping. </notes>

<success_criteria>

Discovery ping sent and response window collected
All responding agents listed with their capabilities
Cache updated at ~/.claude/channels/nats/agents.json
Zero-response case explained with troubleshooting guidance </success_criteria>