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은 Claude Code, Codex, Cursor 같은 Agent Skills 지원 앱에서 써요
설치
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 1Claude 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
터미널 열기
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-registryClaude Code를 다시 열고 /nacos-skill-registry를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
ChatGPT 데스크톱 앱
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
Option 1ChatGPT에게 설치 맡기기
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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
터미널 열기
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만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Option 1Codex에게 설치 맡기기
이 문장을 복사해 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
터미널 열기
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-registryCodex를 다시 열고 관련 작업을 요청하면 Codex가 skill을 목록에 보여 줘요
Option 1Cursor에게 설치 맡기기
이 문장을 복사해 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가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
터미널 열기
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-registryCursor 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
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 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