# Add to your Claude Code skills
git clone https://github.com/nestjs/agent-skillsGuides for using ai agents skills like agent-skills.
See how agent-skills compares with popular alternatives.
agent-skills is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by nestjs. Agent skills for Nest framework (node.js) 🕵️♂️. It has 89 GitHub stars.
agent-skills's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/nestjs/agent-skills" and add it to your Claude Code skills directory (see the Installation section above).
agent-skills is primarily written in JavaScript. It is open-source under nestjs on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh agent-skills against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Official Agent Skills for building and extending NestJS applications with coding agents. They give an agent what its training data lacks:
@IsOptional() letting null through to a 500, a rate limiter that never sees the user, an event stream that outlives a revoked key, and many more.Each skill is a folder with a SKILL.md that holds its rules, plus references/ with longer recipes. Every recipe was run on the released packages. The skills work with any agent that reads the Agent Skills format: Claude Code, Codex, Cursor and others.
| Skill | Use when |
|---|---|
nestjs |
creating or extending a NestJS application: starting a project, layout, module system, where the docs are, common mistakes |
nestjs-feature |
adding or changing endpoints: where code goes, modules and providers, validation (Zod with @Body({ schema }) or class-validator), status codes, errors, HTTP options, Server-Sent Events |
nestjs-auth |
adding or changing authentication or authorization: @nestjs/authentication (passwords, sessions, tokens, API keys) and @nestjs/authorization (policies) |
nestjs-data |
adding or changing persistence: @nestjs/drizzle and @nestjs/typeorm, migrations, safe updates, paging, transactions |
nestjs-testing |
writing, running or fixing tests: unit, service and end-to-end tests, overriding providers and global guards, signing test users in |
nestjs-production |
preparing for production: configuration, logs, observability with NestJS Observe, health checks, rate limiting, OpenAPI, shutdown, deployment |
Agents load a skill when its description matches the task, so there's nothing to invoke by hand.
The skills live in skills/. Install them for one project (committed with the code, so everyone on the team gets them) or for your user account (every project on your machine).
npx @nestjs/skills add
copies every skill into .agents/skills/, which Codex and Cursor read. Choose where with --agent:
--agent |
Folder | Read by |
|---|---|---|
agents (default) |
.agents/skills/ |
Codex, Cursor and other Agent Skills readers |
claude |
.claude/skills/ |
Claude Code (and Cursor) |
cursor |
.cursor/skills/ |
Cursor |
all |
.agents/skills/ and .claude/skills/ |
Codex, Cursor and Claude Code at once (Cursor reads both folders) |
npx @nestjs/skills add --agent claude # Claude Code, this project
npx @nestjs/skills add --agent all # Codex, Cursor and Claude Code
npx @nestjs/skills add --agent agents --global # every project on your machine (~/.agents/skills)
npx @nestjs/skills add nestjs nestjs-auth # only some skills
npx @nestjs/skills list # what's in the package
npx @nestjs/skills remove # remove what it installed
--agent also takes several targets (--agent agents,claude or repeated). --dir <path> installs anywhere else. The installer only replaces or removes folders it installed itself (it leaves a .nestjs-skills marker in each); --force replaces a same-named folder that it didn't. Pin the version for the team with npm i -D @nestjs/skills and npx nestjs-skills add. Programmatic use: import { listSkills, skillsDir } from '@nestjs/skills'.
As a plugin, from this repository's marketplace:
claude plugin marketplace add nestjs/agent-skills
claude plugin install nestjs@nestjs
Or inside a session: /plugin marketplace add nestjs/agent-skills, then /plugin install nestjs@nestjs. Skills from the plugin are namespaced (nestjs:nestjs-auth).
Without the plugin: npx @nestjs/skills add --agent claude (add --global for ~/.claude/skills/).
To preconfigure a repository for your team, add this to its .claude/settings.json; each contributor still runs the install once:
{
"extraKnownMarketplaces": {
"nestjs": { "source": { "source": "github", "repo": "nestjs/agent-skills" } }
},
"enabledPlugins": { "nestjs@nestjs": true }
}
Codex reads skills from .agents/skills/ in the repository (and in parent folders up to the repository root) and from ~/.agents/skills/ for your user.
Cursor reads skills from .agents/skills/ and .cursor/skills/ in the project, and from ~/.agents/skills/ and ~/.cursor/skills/ for your user. It also loads .claude/skills/ and .codex/skills/.
Copy (or symlink) the skill folders to where your agent loads skills. .agents/skills/ covers Codex and Cursor at once:
git clone https://github.com/nestjs/agent-skills.git
mkdir -p .agents/skills && cp -R agent-skills/skills/* .agents/skills/
For every project on your machine, use ~/.agents/skills/ instead. A symlink (ln -s "$PWD/agent-skills/skills/nestjs-auth" ~/.agents/skills/) keeps a copy current with git pull.
Keep each folder whole: SKILL.md links to its references/ with relative paths, and the skills refer to each other by name.
claude plugin marketplace update nestjs, then claude plugin update nestjs@nestjs, or turn on auto-update for the marketplace in /plugin.npx @nestjs/skills@latest add again: it replaces the copies it installed, dropping files a skill no longer has.git pull and copy the folders again (symlinked folders update with the pull).Written for NestJS 12 (@nestjs/core 12.x) on Node.js 20 or later. The recipes were run on:
@nestjs/authentication 0.1.6 and @nestjs/authorization 0.1.4;@nestjs/drizzle 0.0.2 with Drizzle 1.0 rc, and @nestjs/typeorm 12.0.3 with TypeORM 1.1;@nestjs/throttler 6.8, @nestjs/swagger 12.1, @nestjs/terminus 12.2, @nestjs/config 12.1 and @nestjs/observe 0.3.The skills tell the agent to check the installed version and the documentation before relying on what it remembers.
Each SKILL.md follows the Agent Skills specification:
name matches the folder;description says when the skill applies, under 1,024 characters;name, description, license, compatibility), so the same files work in every agent and can be uploaded to the Claude apps.The repository is also a Claude Code plugin (.claude-plugin/plugin.json), its own marketplace (.claude-plugin/marketplace.json), and the npm package @nestjs/skills (the skills, the plugin manifests, and the nestjs-skills installer; no dependencies).
Keep SKILL.md files short: rules and pitfalls in the file, longer code in references/, one level deep. Before adding an API or a pitfall, check it against the docs and run it on a released version.
Validate the frontmatter, links and versions, and test the installer:
npm run validate
npm test
claude plugin validate --strict .
A release bumps version in both package.json and .claude-plugin/plugin.json (npm run validate checks they match), then npm publish, which runs the same checks first.