nacos Skill
What it does
an easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category Automation and agents
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/alibaba-nacos)Similar Skills
Same kind of work, ordered like the Skills list
| This one nacos | skills | anatomy | leon | ian-xiaohei-illustrations | |
|---|---|---|---|---|---|
| Maker | alibaba | vercel-labs | wheresryan22 | leon-ai | helloianneo |
| Skills | 1 | 1 | – | 1 | 1 |
| GitHub stars | 33,524 | 39,504 | 27,478 | 17,671 | 13,224 |
| Last code change | Nov 13, 2026 | Nov 13, 2026 | Oct 19, 2026 | Nov 13, 2026 | Oct 27, 2026 |
| License | Apache-2.0 | MIT | MIT | MIT | MIT |
1 skills (instruction sets) by alibaba that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor
Install
Is it safe?
- Who made it
GitHub account alibaba (organization), 14 years old
- Use and upkeep
★ 33,524 stars · code last changed Nov 13, 2026
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit f56069e (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Files are byte-for-byte the same as on GitHub at commit f56069e · View on GitHub ↗
Plain text files, no programs
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
Look inside before downloading
All 2 files · 34 KB
SKILL.md23 KBLICENSE11 KB
Download nacos-skill-registry.zip
Open Skills on claude.ai and upload
+Create skillUpload a skillpick nacos-skill-registry.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /nacos-skill-registry or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alibaba/nacos.git /tmp/popnx-skill-alibaba-nacos-f56069e && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-alibaba-nacos-f56069e/skills/nacos-skill-registry' ~/.claude/skills/nacos-skill-registryRestart Claude Code, then type /nacos-skill-registry or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the nacos-skill-registry folder at ~/.agents/skills/nacos-skill-registry
~ is your home folder ($HOME)
Without Terminal: download the ZIP, unzip it and move the nacos-skill-registry folder to ~/.agents/skills
Download nacos-skill-registry.zip
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alibaba/nacos.git /tmp/popnx-skill-alibaba-nacos-f56069e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-alibaba-nacos-f56069e/skills/nacos-skill-registry' ~/.agents/skills/nacos-skill-registry
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alibaba/nacos.git /tmp/popnx-skill-alibaba-nacos-f56069e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-alibaba-nacos-f56069e/skills/nacos-skill-registry' ~/.agents/skills/nacos-skill-registryRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick nacos-skill-registry
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/alibaba/nacos.git /tmp/popnx-skill-alibaba-nacos-f56069e && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-alibaba-nacos-f56069e/skills/nacos-skill-registry' ~/.cursor/skills/nacos-skill-registryIn Cursor’s Agent chat, type / and pick nacos-skill-registry
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: nacos-skill-registry
description: Discover, install, update, merge, and publish AI skills with Nacos for personal or team skill registries.
---
# Nacos Skill Registry
This skill helps you discover, install, update, merge, and publish 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 skills across agents, machines, teammates, or execution environments
- 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 edit|show [name]` — Manage connection profiles
- `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:
```bash
nacos-cli -v
nacos-cli --help
```
Use the command contract that matches the installed version:
| Installed CLI | Skill publish workflow | Notes |
| :--- | :--- | :--- |
| `1.0.4` | `skill-upload` -> `skill-review` -> wait for approval -> `skill-release` | Current lifecycle. `skill-publish` is deprecated and only runs upload + review for compatibility. |
| Any other version | Inspect `nacos-cli --help` and command-specific help | Do not hard-code old behavior. Follow the commands actually present in the installed CLI. |
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:
```bash
which nacos-cli
```
If not found, install it using the official installer script:
**Linux / macOS:**
```bash
curl -fsSL https://nacos.io/nacos-installer.sh | sudo bash -s -- --cli
```
**Windows (PowerShell):**
```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`).
Before asking the user to create or edit a profile, check whether the environment already provides a complete
`sts-hiclaw` setup:
```bash
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:
```bash
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, check if a default profile already exists:
```bash
nacos-cli profile show
```
**If a profile exists** (the command prints config content), proceed to Step 3. The default profile requires no extra flags:
```bash
nacos-cli skill-list
```
To use a named profile:
```bash
nacos-cli --profile dev skill-list
```
**If no profile exists** (the command reports an error or shows empty/default values), 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`
4. **Namespace** (optional): the Nacos namespace ID to use. Leave empty for the default public namespace.
Once the user provides the info, create the local profile file on their machine:
```bash
mkdir -p ~/.nacos-cli
${EDITOR:-vi} ~/.nacos-cli/default.conf
```
Tell the user to fill in only their local connection values: host, port, auth type, credentials when the selected auth type needs them, and namespace.
Do not include concrete usernames, passwords, access keys, or secret keys in shared docs or skill examples.
For `sts-hiclaw`, the profile should set `authType: sts-hiclaw`; do not store STS credentials in the profile. 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 config, verify it works:
```bash
nacos-cli profile show
```
Then do a quick connectivity test:
```bash
nacos-cli skill-list
```
If the connection succeeds, tell the user:
```text
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
#### Creating Additional Profiles
If the user needs to connect to multiple Nacos servers (e.g., dev and prod), they can create named profiles:
```bash
# Create or edit a named profile locally (e.g., "dev")
mkdir -p ~/.nacos-cli
${EDITOR:-vi} ~/.nacos-cli/dev.conf
```
Do not hard-code real credentials in shared docs, repositories, or skill examples. Fill the local profile with the
actual host, auth type, username, password, and namespace only on the user's machine.
Then use it with `--profile`:
```bash
nacos-cli --profile dev skill-list
```
### Step 3: Understand What They Need
When a user asks for help, identify:
1. The domain (e.g., code review, testing, depDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 33,524
- Maker
- alibaba
- License
- Apache-2.0
- Last code change
- Nov 13, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- a2a-registry, agent, ai-registry, configuration-management, distributed-configuration, dubbo, istio, kubernetes, mcp, mcp-management, mcp-registry, microservices
- Repo
- alibaba/nacos