nacos-group/nacos-group.github.io/public

Nacos Skill Registry

This skill helps you discover, install, update, merge, publish, and route synchronization workflows for AI skills through Nacos using the nacos-cli tool.

When to Use This Skill

Use this skill when the user:

• Asks "how do I do X" where X might be a task with an existing skill in Nacos
• Says "find a skill for X" or "is there a skill in Nacos for X"
• Asks "what skills are available" or "list skills from Nacos"
• Wants to search for tools, templates, or workflows stored in Nacos
• Needs to download or install a skill from a personal, team, or organization Nacos registry
• Wants to upload or publish a local skill to Nacos for reuse
• Mentions sharing or synchronizing skills across agents, machines, teammates, or execution environments
• Asks about nacos-cli skill-sync; route detailed sync workflow questions to https://nacos.io/skill-sync/SKILL.md
• Needs to merge local skill edits with a newer remote version and publish the merged result

What is nacos-cli?

The nacos-cli is a command-line tool for interacting with Nacos. It supports configuration management, skill management, agent spec management, and provides an interactive terminal.

GitHub: https://github.com/nacos-group/nacos-cli

Key skill commands:

• nacos-cli skill-list -- Search and list available skills
• nacos-cli skill-get <name...> -- Download and install one or more skills locally
• nacos-cli skill-upload <path> -- Upload a skill and create an editing draft
• nacos-cli skill-review <name> [--version <version>] -- Submit a draft for review
• nacos-cli skill-release <name> --version <version> -- Release an approved version online
• nacos-cli skill-describe <name> -- Inspect skill metadata and per-version status

Other commands:

• nacos-cli profile list|show|set|get|switch|edit|delete -- Manage connection profiles
• nacos-cli skill-sync -- Synchronize skills across local agent directories, with optional Nacos-backed tracking
• nacos-cli config-list|config-get|config-set -- Manage Nacos configurations
• nacos-cli agentspec-list|agentspec-get|agentspec-upload|agentspec-review|agentspec-release|agentspec-describe -- Manage agent specs
• nacos-cli interactive -- Start interactive terminal mode
• nacos-cli completion [bash|zsh|fish|powershell] -- Generate shell completion scripts

Version-Aware CLI Contract

Always check the installed nacos-cli version and available skill commands before publishing or documenting a workflow:

nacos-cli -v
nacos-cli --help

Use the command contract that matches the installed version:

For 1.0.4, treat these as distinct states:

• skill-upload: creates or updates an editing draft version
• skill-review: submits the draft, moving it toward reviewing
• skill-describe: use this to confirm the submitted version has passed review
• skill-release: publishes a reviewed/approved version online; it requires an explicit --version

How to Help Users Find and Install Skills

Step 1: Ensure nacos-cli is Available

Check if nacos-cli is installed:

which nacos-cli

Use the npm package through npx if you do not want to install a persistent local binary:

npx @nacos-group/cli --help
npx @nacos-group/cli skill-list --host 127.0.0.1 --port 8848 -u nacos -p nacos

When using npx, replace nacos-cli in the examples below with npx @nacos-group/cli. For non-interactive agent runs, use npx -y @nacos-group/cli ... if npx would otherwise prompt before downloading the package.

For a persistent local install, use the official installer script:

Linux / macOS:

curl -fsSL https://nacos.io/nacos-installer.sh | sudo bash -s -- --cli

Windows (PowerShell):

iwr -UseBasicParsing https://nacos.io/nacos-installer.ps1 -OutFile $env:TEMP\nacos-installer.ps1; & $env:TEMP\nacos-installer.ps1 -cli; Remove-Item $env:TEMP\nacos-installer.ps1

Step 2: Resolve Configuration (Profile)

nacos-cli uses a profile mechanism. Profile configs are stored in ~/.nacos-cli/<profile>.conf. The default profile is default (i.e., ~/.nacos-cli/default.conf). Use nacos-cli profile ... commands instead of asking the user to edit profile files by hand.

Before asking the user to create or edit a profile, check whether the environment already provides a complete sts-hiclaw setup:

printenv NACOS_AUTH_TYPE HICLAW_CONTROLLER_URL HICLAW_AUTH_TOKEN_FILE

If NACOS_AUTH_TYPE=sts-hiclaw, HICLAW_CONTROLLER_URL is set, and HICLAW_AUTH_TOKEN_FILE points to a readable local token file, use sts-hiclaw mode directly. Do not require a local ~/.nacos-cli/<profile>.conf file in this case.

You can verify connectivity directly:

nacos-cli skill-list

Treat NACOS_AUTH_TYPE as the source of truth for environment-based auth selection. If it is not set to sts-hiclaw, do not assume sts-hiclaw mode only because HICLAW_CONTROLLER_URL and HICLAW_AUTH_TOKEN_FILE exist. Fall back to profile initialization when the explicit environment-based setup is missing or fails.

First, inspect available profiles:

nacos-cli profile list
nacos-cli profile show
nacos-cli profile show <profile>

If a usable profile exists, proceed to Step 3. The current/default profile requires no extra flags:

nacos-cli skill-list

To use a named profile:

nacos-cli --profile dev skill-list

If no usable profile exists, guide the user through first-time initialization.

First-Time Profile Initialization

Ask the user the following information:

1. Nacos server address: the host and port of their Nacos server (e.g., 127.0.0.1:8848, or a remote address like nacos.example.com:8848)
2. Auth type: none, nacos, aliyun, or sts-hiclaw
3. Credentials:

• For none auth: no credentials are required
• For nacos auth: username and password from the user's local Nacos instance
• For aliyun auth: AccessKey and SecretKey
• For sts-hiclaw auth: credentials are fetched dynamically from HiClaw STS; the local environment must provide

HICLAW_CONTROLLER_URL and HICLAW_AUTH_TOKEN_FILE

1. Namespace (optional): the Nacos namespace ID to use. Leave empty for the default public namespace.

Once the user provides the info, create or update the profile with profile set. The command creates the profile if it does not exist, and sensitive values are encrypted before being saved.

nacos-cli profile set default server=<host>:<port> auth-type=none namespace=<namespace>
nacos-cli profile set dev server=<host>:<port> auth-type=nacos username=<username> password=<password> namespace=<namespace>
nacos-cli profile set dev server=<host>:<port> auth-type=aliyun access-key=<access-key> secret-key=<secret-key> namespace=<namespace>

Use host=<host> port=<port> instead of server=<host>:<port> if the values are already separate. Add scheme=https when the server requires HTTPS. Omit namespace=<namespace> when using the default public namespace. Do not include concrete usernames, passwords, access keys, or secret keys in shared docs or skill examples.

For sts-hiclaw, set the auth type but do not store STS credentials in the profile:

nacos-cli profile set dev server=<host>:<port> auth-type=sts-hiclaw namespace=<namespace>

The CLI reads HICLAW_CONTROLLER_URL and HICLAW_AUTH_TOKEN_FILE, then requests temporary credentials from $HICLAW_CONTROLLER_URL/api/v1/credentials/sts.

After writing the profile, verify it:

nacos-cli profile show <profile>
nacos-cli profile get <profile> server
nacos-cli profile get <profile> auth-type

Then do a quick connectivity test:

nacos-cli --profile <profile> skill-list

Omit --profile <profile> when testing the current/default profile.

If the connection succeeds, tell the user:

Profile initialized! nacos-cli is now connected to <host>:<port>.
You can start searching and installing skills.

If it fails (auth error, connection refused, etc.), help the user troubleshoot:

• Connection refused -> check host/port, is Nacos server running?
• 401/403 -> check username/password or AK/SK
• Namespace error -> verify the namespace ID is correct

Additional Profile Operations

For multiple Nacos servers, use named profiles:

nacos-cli profile set dev server=<host>:<port> auth-type=<auth-type> namespace=<namespace>
nacos-cli --profile dev skill-list

If the user wants a named profile to become the default when --profile is omitted:

nacos-cli profile switch dev

For inspection and maintenance:

nacos-cli profile list
nacos-cli profile get dev
nacos-cli profile edit dev
nacos-cli profile delete dev

Use profile delete only when the user explicitly asks to remove a profile.

Step 3: Understand What They Need

When a user asks for help, identify:

1. The domain (e.g., code review, testing, deployment, documentation)
2. The specific task (e.g., writing tests, reviewing PRs, generating docs)
3. Whether this is a common enough task that a skill likely exists in Nacos

Step 4: Search for Skills

List all skills:

nacos-cli skill-list

Filter by name (supports wildcard *):

nacos-cli skill-list --name "creator"

With pagination:

nacos-cli skill-list --page 2 --size 10

For example:

• User asks "can you help me review code?" -> nacos-cli skill-list --name review
• User asks "is there a skill for testing?" -> nacos-cli skill-list --name test
• User asks "what skills do we have?" -> nacos-cli skill-list

The command returns results in this format:

Skill List (Page: 1/1, Total: N)
-------------------------------------------------------------------------------
  1. <skill-name> - <description>
     latest=<version>  editing=<version-or->  reviewing=<version-or->  online=<count>  status=enabled
     scope=<scope>  owner=<owner>  updated=<yyyy-mm-dd hh:mm:ss>  downloads=<count>
  ...

For scripts or exact verification, use JSON output:

nacos-cli skill-list --name <skill-name> --output json
nacos-cli skill-describe <skill-name> --output json

Step 5: Present Options to the User

When you find relevant skills, present them clearly:

1. Summarize what skills were found
2. Highlight the most relevant skill(s) based on user's needs
3. Provide the install command

Example response:

I found N skills in Nacos. The most relevant one for your needs is:
 
**<skill-name>** - <description>
 
To install it:
nacos-cli skill-get <skill-name>
 
This will download the skill to ~/.skills/ and make it available immediately.
Would you like me to install it?

Step 6: Install the Skill

Download and install a skill:

nacos-cli skill-get <skill-name>

Download multiple skills at once:

nacos-cli skill-get skill-a skill-b skill-c

Download a specific version:

nacos-cli skill-get <skill-name> --version v2

Download via route label (e.g., latest, stable):

nacos-cli skill-get <skill-name> --label stable

Download to a custom directory (default is ~/.skills):

nacos-cli skill-get <skill-name> -o ~/my-skills

After installation, confirm the skill is available:

ls ~/.skills/<skill-name>/SKILL.md

Step 7: Keep Skills Synchronized Across Agents (Optional)