Nestjs Best Practices
rolling-scopes/rsschool-app
NestJS best practices and architecture patterns for building production-ready applications.
Defines nestia benchmark fixture integrity, result reporting, and publication safeguards.
Install Benchmark
$ npx skills add samchon/nestia --skill benchmark -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install samchon/nestia benchmark --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/benchmark .claude/skills/benchmark && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "benchmark" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/benchmark into .claude/skills/benchmark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/samchon/nestia/tree/master/.agents/skills/benchmarkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add samchon/nestia --skill benchmark -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install samchon/nestia benchmark --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/benchmark .agents/skills/benchmark && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "benchmark" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/benchmark into .agents/skills/benchmark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samchon/nestia --skill benchmark -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install samchon/nestia benchmark --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/benchmark .cursor/skills/benchmark && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "benchmark" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/benchmark into .cursor/skills/benchmark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/samchon/nestia.git --path .agents/skills/benchmark--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add samchon/nestia --skill benchmark -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install samchon/nestia benchmark --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/benchmark .gemini/skills/benchmark && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "benchmark" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/benchmark into .gemini/skills/benchmark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install samchon/nestia benchmarkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add samchon/nestia --skill benchmark -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/benchmark .github/skills/benchmark && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "benchmark" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/benchmark into .github/skills/benchmark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samchon/nestia --skill benchmark -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install samchon/nestia benchmark --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samchon/nestia.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/benchmark .opencode/skills/benchmark && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "benchmark" agent skill from https://github.com/samchon/nestia/tree/master/.agents/skills/benchmark into .opencode/skills/benchmark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
benchmark- GitHub stars
- 2.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 734 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Defines nestia benchmark fixture integrity, result reporting, and publication safeguards.
- Works in 3 steps: Run pnpm generate from benchmark/, which… → Confirm every comparator receives the… → Review the generated-program diff. A…
- AI & LLM Engineering work in your project
- SKILL.md covers Measurement Integrity, Fixture Changes, Report Results and Campaign Batching, plus 1 more section
- Calls git and pnpm
What it does
Benchmark is an agent skill from samchon/nestia. Defines nestia benchmark fixture integrity, result reporting, and publication safeguards. Use before running or modifying the benchmark workspace, changing a structure fixture or generated program, or publishing benchmark results.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `performance.md`).
It sits in AI & LLM Engineering. It works with NestJS. The repository describes itself as: NestJS Helper + AI Chatbot Development. The licence is MIT.
When your agent uses it
- AI & LLM Engineering work in your project
Example prompts
- “Use the benchmark skill to define nestia benchmark fixture integrity, result reporting, and publication safeguards”
- “/benchmark”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run pnpm generate from benchmark/, which regenerates the programs, formats them, and rebuilds the package.
- Confirm every comparator receives the same structure and input for the measured row.
- Review the generated-program diff. A stale or inconsistent generated program contaminates every later run.
What it can do on your machine
Read from SKILL.md and the folder at commit d3627e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Benchmark loads about 1.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 734 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from samchon/nestia at commit d3627e8, republished under its MIT licence (© samchon). 734 words, ~1,430 tokens.
Download SKILL.mdSave it as
.claude/skills/benchmark/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- benchmark
- description
- Defines nestia benchmark fixture integrity, result reporting, and publication safeguards. Use before running or modifying the benchmark workspace, changing a structure fixture or generated program, or publishing benchmark results.
Benchmark
This repository owns one benchmark system. Read its procedure in full before acting:
- performance.md:
@samchon/nestia-benchmarkthroughput of@nestia/coreagainst stock NestJS, including generated programs, structure fixtures, and the per-CPU result archive.
Do not confuse it with the published @nestia/benchmark package under packages/benchmark. That package is a product — a load-test runner that drives @nestia/e2e functions and emits markdown reports for a user's own server — and changes to it follow the development skill, not this one. The benchmark/ workspace at the repository root is the measurement system this skill governs.
Measurement Integrity
- Measure the real product. Do not add benchmark-only branches, fixture-name checks, expected-answer checks, monkey patches, or agent restrictions that would be wrong for an unmeasured repository.
- Give every comparator the setup its own documentation prescribes. The NestJS comparator is meant to be an idiomatic
class-validator/class-transformerapplication on the same adapter; measuring a deliberately underconfigured competitor invalidates the comparison. - Keep the adapter axis honest. Every category runs Express and Fastify for both nestia and stock NestJS. A row that compares nestia on one adapter against NestJS on the other measures the adapter, not the library.
- Preserve the workload defined by the selected procedure. A faster result obtained by validating, serializing, or serving less input is not an optimization.
- Treat a surprising result as evidence that the change is not yet understood. Inspect the raw report or the generated program before accepting, explaining away, or patching around it.
Fixture Changes
benchmark/src/programs/ holds generated leaf programs plus hand-maintained server helpers. Edit generated benchmark-*.ts files through the generators under benchmark/src/generate/; edit the createNest*Program.ts helpers under programs/*/servers/ and the DTO shapes under benchmark/src/structures/ in place.
Both structure trees are one contract. structures/pure/ holds the plain TypeScript DTOs that @nestia/core consumes, and structures/class-validator/ holds the decorated twins the NestJS comparator consumes. They must describe the same shape; a property present in one and missing from the other silently changes the measured payload.
Finish every fixture change before publishing it:
- Run
pnpm generatefrombenchmark/, which regenerates the programs, formats them, and rebuilds the package. - Confirm every comparator receives the same structure and input for the measured row.
- Review the generated-program diff. A stale or inconsistent generated program contaminates every later run.
Benchmark prose follows AGENTS.md ## Maintenance and the documentation skill.
Report Results
Every result table reported in chat or committed to the result archive must be preserved for the active pull request. When the user has authorized PR updates under the pull-request skill, maintain one sticky comment beginning with <!-- nestia-benchmark-results -->; update it with the latest table, report paths, and known invalid or missing categories.
If no pull request exists or no update is authorized, keep the result in the final report and mark the comment as pending. Post it only after the user creates or authorizes updating the pull request.
Show full SKILL.md (266 more words)Show less
Campaign Batching
When benchmark findings produce multiple implementation issues, load the issue-campaign skill and use its planning and claim procedure unchanged for the dependency DAG, claim freeze, and official GitHub createdAt-to-mergedAt duration: Plan One Cycle Pull Request for a solo campaign, or Plan And Claim A Pull Request Wave with its batch admission test, merge pressure, and grouping and split ledger when the user explicitly requested a parallel campaign. This benchmark skill continues to own workload, fixture, measurement, result, and publication integrity; do not redefine pull-request batching here.
Campaign Cleanup
When a benchmark campaign uses a disposable worktree or an isolated measurement root, finish cleanup before marking that assignment complete. Preserve the committed result archive and compact command evidence, but remove every disposable worktree and its assigned mutable roots: GOCACHE, GOTMPDIR, TTSC_CACHE_DIR, generated-program scratch tree, dependency install tree, and temporary consumer or report staging tree. Go temporary assets are never reusable campaign evidence.
- Record the measured commit, command, result paths and hashes, environment, and any retained published result archive.
- Confirm the worktree and mutable roots contain no unreported source or result artifact.
- Remove the mutable roots and, for an assigned disposable worktree, run
git worktree remove --force <path>for its exact path. - Verify every removed root and, when applicable, worktree path no longer exists, run
git worktree prune, delete the associated disposable local topic branch when one was created, and confirm no worktree registration remains.
If a measurement is abandoned or invalid, retain only the diagnostic record needed to explain it; remove its worktree and Go temporary assets by the same procedure.
© samchon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/benchmark of samchon/nestia.
- SKILL.md
- performance.md
Open the folder on GitHubat commit d3627e8
Compare with similar skills
Benchmark next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Benchmark this skillsamchon/nestia | 2.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Nestjs Best Practicesrolling-scopes/rsschool-app | 10k | 6 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Twenty Syncable Entity Validationtwentyhq/twenty | 58k | — | ~3.3k | Automated safety check: Pass | Custom licence | |
| Nestjs Trpctrycompai/crm | 11k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Evolutionary Modular Architecturetech-leads-club/agent-skills | 7k | — | ~3.7k | Automated safety check: Pass | CC-BY-4.0 | |
| Twenty Syncable Entity Wiringtwentyhq/twenty | 58k | — | ~2.9k | Automated safety check: Pass | Custom licence |
Similar skills
Twenty Syncable Entity Validation
twentyhq/twenty
Contributor guide for step three of adding a syncable entity to the Twenty server: write the validator, the migration action builder and the orchestrator wiring.
Nestjs Trpc
trycompai/crm
Build end-to-end type-safe tRPC APIs inside NestJS using the nestjs-trpc adapter — @Router/@Query/@Mutation/@Subscription decorators, TRPCModule.forRoot, injectable middlewares and context, Zod…
Evolutionary Modular Architecture
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
Twenty Syncable Entity Wiring
twentyhq/twenty
Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.
AI Model Nodejs
TencentCloudBase/CloudBase-AI-Toolkit
A skill your agent uses for Node.js backend AI via @cloudbase/node-sdk (=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration.
More from samchon/nestia
All 10 skills in this repoProject
samchon/nestia
Defines the nestia product contract, workspace layout, package boundaries, the Go plugin composition model, and canonical commands.
Contracts
samchon/nestia
Defines self-acknowledgments for production declarations and tests.
Issue Campaign
samchon/nestia
Defines the default solo repository-wide issue campaign for nestia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo…
Pull Request
samchon/nestia
Defines nestia branch, commit, pull-request, check, and merge workflows.
Review
samchon/nestia
Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia.
Development
samchon/nestia
Defines nestia implementation rules, testing standards, validation, consequence analysis, and change integrity.
Related
Works with
Categories
Questions about Benchmark
What does Benchmark do?
Defines nestia benchmark fixture integrity, result reporting, and publication safeguards. Benchmark is an agent skill from samchon/nestia. Defines nestia benchmark fixture integrity, result reporting, and publication safeguards.
When should I use Benchmark?
Benchmark fits situations like: AI & LLM Engineering work in your project.
How do I install Benchmark in Claude Code?
Run `npx skills add samchon/nestia --skill benchmark -a claude-code`. Or copy the skill folder (.agents/skills/benchmark in samchon/nestia) into .claude/skills/benchmark in your project. Claude Code loads it when a task matches its description.
How do I install Benchmark in Codex?
Run `npx skills add samchon/nestia --skill benchmark -a codex`. Or copy the skill folder (.agents/skills/benchmark in samchon/nestia) into .agents/skills/benchmark in your project. Codex loads it when a task matches its description.
Can I use Benchmark in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add samchon/nestia --skill benchmark -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/benchmark, .gemini/skills/benchmark, .github/skills/benchmark and .opencode/skills/benchmark in your project.
What does Benchmark need to run?
Going by SKILL.md and its folder, Benchmark needs the command-line tools its instructions call (git and pnpm).
Does Benchmark access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Benchmark safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Benchmark use?
Benchmark is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Benchmark use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Benchmark?
Skills that share tags, products or a category with Benchmark: Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Twenty Syncable Entity Validation (twentyhq/twenty, 58k stars), Nestjs Trpc (trycompai/crm, 11k stars) and Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Benchmark?
samchon (a GitHub user) maintains it in samchon/nestia, which has 2,179 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: samchon/nestia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.