Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Inicia sesión con Google para escribir reseñas.Prototipo · se actualiza cada 30 min
PopNx MCPServidores MCP para quienes usan IA · en palabras sencillas

nodejs-cli-apps-best-practices Skill

de lirantal★ 41431 skills

Instalar

What it does

The largest Node.js CLI Apps best practices list ✨

  • Connects Instruction files the AI reads; connects to nothing
  • Account or key No key needed
  • Category Otros
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.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/lirantal-nodejs-cli-apps-best-practices.svg)](https://mcp.popnx.com/en/skills/lirantal-nodejs-cli-apps-best-practices)

Skills parecidas

Mismo tipo de trabajo, ordenadas como la lista de Skills

Comparado con otros parecidos
Este
nodejs-cli-apps-best-practices
llmfitclaude-videoVideoCaptionerpatent-disclosure-skill
AutorlirantalAlexsJonesbradautomatesWEIFENG2333handsomestWei
Skills11111
Estrellas de GitHub414339.00420.88916.53913.468
Último cambio de código9 jul 202612 nov 202625 sept 202612 sept 202615 nov 2026
LicenciaCC-BY-SA-4.0MITMITGPL-3.0MIT

1 skills (conjuntos de instrucciones) de lirantal 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 lirantal (person), 16 years old

  • Use and upkeep

    ★ 4143 stars · code last changed 9 jul 2026

  • Any scripts?

    3 scripts that can run on a computer: evals/fixtures/arg-injection.js, evals/fixtures/bad-cli-clean.js, evals/fixtures/bad-cli.js

  • Uses the internet?

    Scripts that go online: evals/fixtures/bad-cli-clean.js, evals/fixtures/bad-cli.js

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit e6374e4 (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)

  1. Download from GitHub

    This skill uses the CC-BY-SA-4.0 license, which is not on the list we redistribute, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier

    Download from GitHub (whole repo) ↗

    Unzip it, then zip only the skills/nodejs-cli-best-practices folder again. The ZIP must have a nodejs-cli-best-practices folder with SKILL.md at the top level, no loose files

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick nodejs-cli-best-practices.zip

    Open claude.ai/customize/skills ↗

  3. 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

Where to install
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) for all my projects, at ~/.claude/skills/nodejs-cli-best-practices. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) into the project this chat is open in (at .claude/skills/nodejs-cli-best-practices). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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 /nodejs-cli-best-practices, 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.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. 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/lirantal/nodejs-cli-apps-best-practices.git /tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4/skills/nodejs-cli-best-practices' ~/.claude/skills/nodejs-cli-best-practices
  3. Vuelve a abrir Claude Code y escribe /nodejs-cli-best-practices, o pide una tarea relacionada y Claude lo usará

Las skills que instalas tú funcionan en la app de escritorio de ChatGPT, en Codex CLI y en la extensión de Codex para el IDE · ChatGPT en la web y el móvil no puede usar skills instaladas por ti, solo las que vienen con un plugin del directorio

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

Where to install
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) for all my projects, at ~/.agents/skills/nodejs-cli-best-practices. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) into the project this chat is open in (at .agents/skills/nodejs-cli-best-practices). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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 nodejs-cli-best-practices en ~/.agents/skills/nodejs-cli-best-practices

~ es tu carpeta de inicio ($HOME)

For Terminal users

Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. 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/lirantal/nodejs-cli-apps-best-practices.git /tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4/skills/nodejs-cli-best-practices' ~/.agents/skills/nodejs-cli-best-practices

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

Where to install
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) for all my projects, at ~/.agents/skills/nodejs-cli-best-practices. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) into the project this chat is open in (at .agents/skills/nodejs-cli-best-practices). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. 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/lirantal/nodejs-cli-apps-best-practices.git /tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4/skills/nodejs-cli-best-practices' ~/.agents/skills/nodejs-cli-best-practices
  3. Vuelve 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

Where to install
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) for all my projects, at ~/.cursor/skills/nodejs-cli-best-practices. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) into the project this chat is open in (at .cursor/skills/nodejs-cli-best-practices). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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 nodejs-cli-best-practices

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.

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba

  2. 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/lirantal/nodejs-cli-apps-best-practices.git /tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-lirantal-nodejs-cli-apps-best-practices-e6374e4/skills/nodejs-cli-best-practices' ~/.cursor/skills/nodejs-cli-best-practices
  3. En el chat Agent de Cursor escribe / y elige nodejs-cli-best-practices

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

Where to install
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) for all my projects, at ~/.claude/skills/nodejs-cli-best-practices (in Codex use ~/.agents/skills/nodejs-cli-best-practices, in Cursor ~/.cursor/skills/nodejs-cli-best-practices). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill nodejs-cli-best-practices from https://github.com/lirantal/nodejs-cli-apps-best-practices folder skills/nodejs-cli-best-practices (commit e6374e4) into the project this chat is open in (at .claude/skills/nodejs-cli-best-practices; in Codex use .agents/skills/nodejs-cli-best-practices, in Cursor .cursor/skills/nodejs-cli-best-practices). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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.

Ver en GitHub ↗

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: nodejs-cli-best-practices
description: Guide and audit Node.js CLI application development against 41 established best practices covering UX, distribution, interoperability, accessibility, testing, error handling, development setup, analytics, versioning, and security. Use this skill when building, extending, reviewing, or scaffolding a Node.js CLI — including when someone says "audit my CLI", "review my CLI code", "I'm building a CLI tool", or asks about adding argument parsing, help output, shell completion/autocomplete, error handling, color output, STDIN, --json flags, exit codes, --version flags, or npm publishing. Applies even when best practices are not explicitly mentioned. Also trigger for "how should I implement X in my CLI" or "what's the right way to do Y in a Node.js CLI". Do NOT use for Node.js backend or API development with no CLI entry point.
metadata:
  version: 1.0.0
  category: nodejs
  tags: [nodejs, cli, best-practices, audit, command-line]
---

This skill operates in two modes — **audit** for reviewing existing CLI code and **development guide** for building new features or tools.

## Critical

Always read `references/best-practices.md` before producing any output. It contains the complete reference for all 41 practices with code examples and recommended packages. It is the source of truth for both modes — do not rely on general knowledge alone, as several practices (specific package recommendations, §X.X numbering, configuration precedence order) are specific to this guide.

## Determining the mode

| Trigger | Mode | Action |
|---------|------|--------|
| User provides existing CLI code or files to review | **Audit** | Produce a structured audit report |
| User asks how to build or implement something | **Development guide** | Surface relevant practices with examples |
| User says "review and help me improve" | **Both** | Audit first, then provide concrete guidance for each failing practice |

---

## Audit mode

Systematically compare the provided code against the practices in `references/best-practices.md`. Focus on what is verifiable from the code. Use judgment to mark practices as not applicable (➖) when there's genuinely no way to assess them from static analysis (e.g., Docker support when the project shows no distribution intent).

**Prioritize by user impact** — a missing exit code (§6.4) or absent `--version` flag (§9.1) affects every user and every CI pipeline; missing Docker image (§4.1) is low priority for most projects.

### Audit report format

```
## Node.js CLI Best Practices Audit

### Summary
✅ N practices followed  ⚠️ N need attention  ❌ N not implemented  ➖ N not applicable

---

### 1. Command Line Experience
| # | Practice | Status | Finding |
|---|----------|--------|---------|
| 1.1 | Respect POSIX args | ✅ | Uses yargs with proper short/long aliases |
| 1.2 | Build empathic CLIs | ❌ | No interactive fallback when required args absent |
...

[Repeat for each section with applicable practices]

---

### Priority recommendations

**High priority** (user-facing or CI-breaking):
- **§6.4 Exit codes** — `process.exit()` called without a code
  ```js
  // Fix
  process.exit(1); // on error
  process.exit(0); // on success
  ```

**Medium priority**:
- ...

**Low priority / nice to have**:
- ...
```

Keep findings concise and tied to specific code patterns. Always include a concrete fix with code for each ❌.

---

## Development guide mode

When building a new CLI feature or tool, don't wait to be asked — surface relevant best practices immediately based on what the user is building.

**For a "building a CLI from scratch" request**, organize guidance by development phase:

1. **Project setup** (§7.1, §7.3, §4.4, §2.2): bin object, shebang, files field, shrinkwrap
2. **Argument design** (§1.1, §1.2, §1.7, §1.9, §3.4): POSIX compliance, empathic fallbacks, zero-config, help output, config precedence
3. **I/O and interoperability** (§3.1, §3.2, §3.5, §3.6, §3.7, §4.2): STDIN, structured output, gated interactivity, STDOUT/STDERR separation, shell completion, graceful degradation
4. **Error handling** (§6.1–§6.5): trackable codes, actionable messages, debug mode, exit codes
5. **UX polish** (§1.4, §1.5, §1.6): colors, rich interactions, hyperlinks
6. **Versioning** (§9.1–§9.7): `--version` flag, semver, changelog
7. **Security** (§10.1): argument injection

**For a targeted feature request** (e.g., "add error handling", "add a --json flag"), surface only the directly relevant practices.

### Development guidance format

```
## Node.js CLI best practices for [feature/topic]

### Checklist
- [ ] §X.Y Practice name — one-line explanation of why it matters

### Implementation
[Concrete, copy-pasteable code]

### Recommended packages
- `package-name` — when and why to use it
  npm install package-name

### Common mistakes
- What not to do → why it breaks → what to do instead
```

---

## Quick reference: which section applies

| Topic | Sections |
|-------|----------|
| Argument parsing / flags | §1.1, §1.7, §1.9, §3.4 |
| Help / usage output | §1.9 |
| Shell completion / autocomplete | §3.7 |
| Prompts / interactivity | §1.2, §1.5, §3.5 |
| Colors / styling | §1.4, §4.2 |
| STDIN / piping | §3.1, §3.5, §3.6 |
| STDOUT / STDERR | §3.6 |
| JSON / structured output | §3.2, §3.6, §4.2 |
| Cross-platform issues | §3.3, §7.2 |
| Error messages | §3.6, §6.1, §6.2 |
| Exit codes | §6.4 |
| Debug / verbose mode | §3.6, §6.3 |
| `--version` flag | §9.1, §9.3 |
| package.json setup | §7.1, §7.3, §9.3 |
| npm publishing / distribution | §2.1, §2.2, §9.6 |
| Security / user input | §10.1 |
| Configuration persistence | §1.3, §2.3 |
| Node.js version targeting | §4.3 |
| Analytics / telemetry | §8.1 |

---

## Examples

### Example 1: Audit mode

**User says:** "Audit my Node.js CLI against best practices. Here's my entry file and package.json."

**Actions:**
1. Read `references/best-practices.md`
2. Examine the provided files against each applicable practice
3. Produce the structured audit report with per-section table and priority recommendations

---

### Example 2: Development guide mode (new CLI from scratch)

**User says:** "I'm building a Node.js CLI that parses log files and outputs a summary table. It needs to work cross-platform and I want to publish it on npm."

**Actions:**
1. Read `references/best-practices.md`
2. Identify all practices relevant to this CLI type (cross-platform, npm-published, table output)
3. Organize guidance by development phase (project setup → argument design → I/O → errors → UX → versioning → security)

---

### Example 3: Development guide mode (targeted feature)

**User says:** "My CLI is crashing and just dumping stack traces. How do I add proper error handling?"

**Actions:**
1. Read `references/best-practices.md` sections §6.1–§6.5
2. Surface only the directly relevant practices
3. Provide a concrete, copy-pasteable error handling wrapper

---

## Common mistakes to avoid

| Mistake | Why it matters | Correct approach |
|---------|---------------|------------------|
| Marking §4.1 (Docker) as ❌ for a small personal CLI | Docker is rarely needed; not applicable is honest | Use ➖ when the practice genuinely doesn't fit the project's scope |
| Only auditing the entry file, ignoring package.json | Several high-impact violations (§7.1, §7.3, §2.1, §4.3) live in package.json | Always audit both the entry file and package.json when both are provided |
| Recommending `package-lock.json` for §2.2 | The practice specifically calls for `npm-shrinkwrap.json` for published CLIs | Reference `references/best-practices.md` for the exact requirement |
| Skipping the priority grouping in audit reports | Users need to know what to fix first, not just what's wrong | Always include High / Medium / Low priority sections with concrete fixes |
| Providing a development guide without code examples | Prose guidance alone is not actionable | Every recommended practice should include at least one copy-paste

Conversació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.

Inicia sesión para publicar

Desde GitHub

Estrellas en GitHub
4143
Autor
lirantal
Licencia
CC-BY-SA-4.0
Último cambio de código
9 jul 2026
Archivos SKILL.md del repo (con traducciones y plantillas)
1
Temas
awesome, awesome-list, best-practices, cli, command-line, node, nodejs, nodejs-cli