Nodejs
Node.js server-side JavaScript runtime with npm ecosystem. Use for backend development.From its SKILL.md
npx -y skills add G1Joshi/Agent-Skills --skill nodejsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, 396 tokens by cl100k_base, as published. Nobody here has run it
Node.js
Node.js is a cross-platform JavaScript runtime environment. Node.js 22 (LTS 2025) brings native TypeScript support (experimental), a built-in Test Runner, and a native WebSocket client.
When to Use
- Real-time Apps: Chat, Gaming, Collaboration (WebSockets).
- API Servers: High concurrency with non-blocking I/O.
- Tooling: The foundation of modern frontend toolchains (Vite, Next.js).
Quick Start (Native Features)
// Native Test Runner (No Jest needed)
import { test, assert } from "node:test";
test("synchronous passing test", (t) => {
assert.strictEqual(1, 1);
});
// Native WebSocket
const ws = new WebSocket("ws://example.com/socket");
ws.onopen = () => console.log("Connected");
Core Concepts
Event Loop
Single-threaded, non-blocking I/O. Heavy CPU tasks block the loop (bad), but I/O tasks are offloaded to OS (good).
Streams
Process huge files piece-by-piece without loading them into memory.
Native APIs (2025)
Node now has fetch, test, watch, and .env support built-in. You need fewer dependencies than in 2020.
Best Practices (2025)
Do:
- Use
node:test: Drop Jest/Mocha for simple projects. - Use
node --env-file: Dropdotenvdependency. - Use Async/Await: Callbacks are dead. Long live Promises.
Don't:
- Don't block the Event Loop: Don't run Crypto or Image processing on the main thread. Use Worker Threads.
- Don't use
require: New projects should use ESM (import).
References
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most data backend skills give in 396 tokens
Counted across 229 of the 229 authors here whose files we hold, read 2026-08-07
- Separate business logic into service layersin 22 of 229, across 15 files
- Retry failures with exponential backoffin 21 of 229, across 14 files
- Select only needed database columnsin 20 of 229, across 13 files
- Abstract data access into repository classesin 19 of 229, across 12 files
- Use centralized error handlersin 17 of 229, across 10 files
- Use AsNoTracking for read-only queriesin 16 of 229, across 4 files
- Use async/await for all I/O operationshere, and in 16 of 229, across 5 files
- Implement structured loggingin 15 of 229, across 4 files
- Use dependency injection for all servicesin 14 of 229, across 2 files
- Use resource-based URLs for REST APIsin 13 of 229, across 7 files
- Invalidate cache after data changesin 13 of 229, across 9 files
- Use a dependency injection containerin 12 of 229, across 4 files
Said here and by no other author read
- use the native node test runner
- use the native node env-file support
- use esm imports in new projects
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.