Skill

access

Configure the NATS server URL for Claude Code agent communication. Use when the user wants to set up NATS, change the NATS server URL, check current connection settings, or says "configure nats".

Install

npx claudepluginhub cameri/claude-skills --plugin nats

Tool Access

This skill is limited to using the following tools:

ReadWriteBash(mkdir *)Bash(chmod *)Bash(ls *)Bash(cat *)Bash(grep *)Bash(nats *)

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 29, 2026

Actions

View Source View Plugin View on GitHub View README

<objective> Manages the NATS server URL for the Claude Code agent. The URL is stored in `~/.claude/channels/nats/${ENV}.env` (chmod 600) and used by the NATS MCP server to connect to the agent network. </objective>

<quick_start> Save URL: /nats:access NATS_URL=nats://nats:4222

Check status: /nats:access (no args)

Guided setup: /nats:access setup </quick_start>

<context> The `env=<name>` argument selects a named environment (e.g. `env=prod`). Omit for the default environment. When `ENV` is empty, the path resolves to `~/.claude/channels/nats/.env`. Display empty ENV as "(default)" in output; omit `env=` from suggested commands.

Credential key: NATS_URL — full NATS server URL (e.g. nats://nats:4222) </context>

<workflow> Parse `env=<name>` from `$ARGUMENTS` first. Strip it from remaining arguments before dispatch.

No arguments — status check:

Check if ~/.claude/channels/nats/${ENV}.env exists.
If not: report no configuration for this environment and suggest:
- /nats:access NATS_URL=nats://nats:4222
- /nats:access setup
If yes: load the file, show NATS_URL, then test connectivity:
```
nats --server "$NATS_URL" server ping 2>&1 | head -5
```
If nats CLI is not available, report the URL and note that connection test requires the nats CLI tool.
List all available environments by showing files in ~/.claude/channels/nats/ matching *.env, stripping the .env suffix. Display .env as "(default)".

setup — guided setup:

Explain: "The NATS_URL points to your NATS server. Common values:"
- nats://nats:4222 (Docker service named nats)
- nats://nats-server:4222 (Docker service named nats-server)
- nats://localhost:4222 (local NATS server)
Ask the user for the NATS server URL (default: nats://nats:4222).
Save and test (same as explicit save below).

NATS_URL=<value> — save the URL:

Parse NATS_URL from $ARGUMENTS. Accept both NATS_URL=... and url=... (case-insensitive).

mkdir -p ~/.claude/channels/nats

Write:

cat > ~/.claude/channels/nats/${ENV}.env <<'EOF'
NATS_URL=<value>
EOF
chmod 600 ~/.claude/channels/nats/${ENV}.env

Test connectivity with nats --server "$NATS_URL" server ping 2>&1 | head -5.
Report result.

clear — remove all credentials for this environment:

Delete ~/.claude/channels/nats/${ENV}.env and confirm.

clear NATS_URL — remove the key:

Remove the NATS_URL line from ${ENV}.env. </workflow>

<notes> If no URL is configured, the agent server defaults to trying: 1. `nats://nats:4222` 2. `nats://nats-server:4222`

These match common Docker Compose service names. </notes>

<success_criteria>

NATS URL saved to env file with chmod 600
Connectivity test passes (server ping succeeds)
Status output shows current URL and all available environments
Missing env file = not configured, reported clearly with next steps </success_criteria>