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 自动化与智能体
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/alibaba-nacos)相似的 Skill
同类工作,排序与 Skill 列表相同
| 本项 nacos | skills | anatomy | leon | ian-xiaohei-illustrations | |
|---|---|---|---|---|---|
| 作者 | alibaba | vercel-labs | wheresryan22 | leon-ai | helloianneo |
| Skill 数 | 1 | 1 | – | 1 | 1 |
| GitHub 星标 | 33,524 | 39,504 | 27,478 | 17,671 | 13,224 |
| 最近代码更新 | 2026年11月13日 | 2026年11月13日 | 2026年10月19日 | 2026年11月13日 | 2026年10月27日 |
| 许可证 | Apache-2.0 | MIT | MIT | MIT | MIT |
Skill 和 MCP 有什么不同
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
适用的应用
开发者未说明 · SKILL.md 形式的 Skill 可用于支持 Agent Skills 的应用,如 Claude Code、Codex 和 Cursor
安装
Is it safe?
- Who made it
GitHub account alibaba (organization), 14 years old
- Use and upkeep
★ 33,524 stars · code last changed 2026年11月13日
- 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
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
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 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1让 Claude Code 帮你安装
复制这句话,粘贴到 Claude Code 的对话中
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
重新打开 Claude Code,输入 /nacos-skill-registry,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.claude/skills
这条命令把 repo 下载到临时文件夹,只复制含 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-registry重新打开 Claude Code,输入 /nacos-skill-registry,或直接提出相关任务,Claude 会自动选用
ChatGPT 桌面应用
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
Option 1让 ChatGPT 帮你安装
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
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 2自己放入文件夹
把 nacos-skill-registry 文件夹放到 ~/.agents/skills/nacos-skill-registry
~ 是你的主文件夹($HOME)
不用终端:下载 ZIP,解压后把 nacos-skill-registry 文件夹移到 ~/.agents/skills
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 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
安装之后
- ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
- 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
- Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
网页版和手机版 ChatGPT
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1让 Codex 帮你安装
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
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 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 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重新打开 Codex 并提出相关任务,Codex 会列出这个 skill
Option 1让 Cursor 帮你安装
复制这句话,粘贴到 Cursor 的对话中
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
在 Cursor 的 Agent 聊天中输入 / 并选择 nacos-skill-registry
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.cursor/skills
这条命令把 repo 下载到临时文件夹,只复制含 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-registry在 Cursor 的 Agent 聊天中输入 / 并选择 nacos-skill-registry
Option 1Let the AI install it
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · 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 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月16日
查看原始 SKILL.md
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 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, dep讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
来自 GitHub
- GitHub 星标
- 33,524
- 开发者
- alibaba
- 许可证
- Apache-2.0
- 最近代码更新
- 2026年11月13日
- repo 中的 SKILL.md 文件(含译本和模板)
- 1
- 主题
- a2a-registry, agent, ai-registry, configuration-management, distributed-configuration, dubbo, istio, kubernetes, mcp, mcp-management, mcp-registry, microservices
- Repo
- alibaba/nacos