Agent skill

nx-workspace

Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT use for running tasks (use nx-run-tasks) or code generation with generators (use nx-generate).

tech-leads-clubgithub.com/tech-leads-clubGitHub ↗
claude-codecopilotcursorNOASSERTION
Install
npx skills add tech-leads-club/agent-skills --skill nx-workspace --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 4 KB
Bundled scripts: none
Path: packages/skills-catalog/skills/(tooling)/nx-workspace/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,983
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Nx Workspace Management ## Quick Start **Exploring workspace**: `nx show projects` and `nx show project <name> --json` **Running tasks**: `nx <target> <project>` (e.g., `nx build my-app`) **Affected analysis**: `nx show projects --affected` or `nx affected -t <target>` > **Note**: Prefix commands with `npx`/`pnpx`/`yarn` if nx isn't installed globally. ## Core Commands ### List and Explore Projects ```bash # List all projects nx show projects # Filter by type, pattern, or target nx show projects --type app nx show projects --projects "apps/*" nx show projects --withTarget build # Find affected projects nx show projects --affected --base=main ``` ### Get Project Information **Critical**: Always use `nx show project <name> --json` for full resolved configuration. Do NOT read `project.json` directly - it contains only partial configuration. ```bash # Get full configuration nx show project my-app --json # Extract targets nx show project my-app --json | jq '.targets | keys' ``` Configuration schemas: - Workspace: `node_modules/nx/schemas/nx-schema.json` - Project: `node_modules/nx/schemas/project-schema.json` ### Run Tasks ```bash # Run specific project nx build web --configuration=pr

What's inside
Steps it walks through
  1. Quick Start
  2. Core Commands
  3. List and Explore Projects
  4. Get Project Information
  5. Run Tasks
  6. Workspace Architecture
  7. Library Types
  8. Detailed Resources
  9. Common Workflows
  10. Quick Troubleshooting
Ships with 4 files
  • reference/best-practices.md
  • reference/ci-cd.md
  • reference/commands.md
  • reference/configuration.md
Commands it runs
List all projects
nx show projects
Filter by type, pattern, or target
nx show projects --type app
nx show projects --projects "apps/*"
nx show projects --withTarget build
Find affected projects
nx show projects --affected --base=main
Get full configuration
nx show project my-app --json
More from agent-skills
All skills →
About this skill
What does the nx-workspace skill do?

Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT use for running tasks (use nx-run-tasks) or code generation with generators (use nx-generate).

How do I install it?

Run `npx skills add tech-leads-club/agent-skills --skill nx-workspace --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going