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 Automatización y agentes
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/alibaba-nacos)Skills parecidas
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este nacos | skills | anatomy | leon | ian-xiaohei-illustrations | |
|---|---|---|---|---|---|
| Autor | alibaba | vercel-labs | wheresryan22 | leon-ai | helloianneo |
| Skills | 1 | 1 | – | 1 | 1 |
| Estrellas de GitHub | 33.524 | 39.504 | 27.478 | 17.671 | 13.224 |
| Último cambio de código | 13 nov 2026 | 13 nov 2026 | 19 oct 2026 | 13 nov 2026 | 27 oct 2026 |
| Licencia | Apache-2.0 | MIT | MIT | MIT | MIT |
1 skills (conjuntos de instrucciones) de alibaba que la IA lee y sigue · no es un MCP server
En qué se diferencia un Skill de MCP
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Funciona con
El autor no lo indica · los skills con SKILL.md funcionan en apps compatibles con Agent Skills, como Claude Code, Codex y Cursor
Instalar
Is it safe?
- Who made it
GitHub account alibaba (organization), 14 years old
- Use and upkeep
★ 33.524 stars · code last changed 13 nov 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
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
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 12 nov 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Deja que Claude Code lo instale
Copia esta frase y pégala en un chat de 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
Vuelve a abrir Claude Code y escribe /nacos-skill-registry, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.claude/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-registryVuelve a abrir Claude Code y escribe /nacos-skill-registry, o pide una tarea relacionada y Claude lo usará
App de escritorio de ChatGPT
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Option 1Deja que ChatGPT lo instale
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el 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 2Coloca la carpeta tú mismo
Coloca la carpeta nacos-skill-registry en ~/.agents/skills/nacos-skill-registry
~ es tu carpeta de inicio ($HOME)
Sin Terminal: descarga el ZIP, descomprímelo y mueve la carpeta nacos-skill-registry a ~/.agents/skills
Descargar nacos-skill-registry.zip
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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
Después de instalar
- App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
- Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
- Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
ChatGPT en la web y el móvil
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Option 1Deja que Codex lo instale
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del 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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-registryVuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill
Option 1Deja que Cursor lo instale
Copia esta frase y pégala en un chat de 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
En el chat Agent de Cursor escribe / y elige nacos-skill-registry
Checked against official docs 12 nov 2026 · Source: cursor.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.cursor/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-registryEn el chat Agent de Cursor escribe / y elige nacos-skill-registry
Option 1Let the AI install it
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu 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 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 16 nov 2026
Ver el SKILL.md original
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en 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, depConversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Desde GitHub
- Estrellas en GitHub
- 33.524
- Autor
- alibaba
- Licencia
- Apache-2.0
- Último cambio de código
- 13 nov 2026
- Archivos SKILL.md del repo (con traducciones y plantillas)
- 1
- Temas
- a2a-registry, agent, ai-registry, configuration-management, distributed-configuration, dubbo, istio, kubernetes, mcp, mcp-management, mcp-registry, microservices
- Repo
- alibaba/nacos