nx-monorepo

1 stars 2 forks
17
B

Nx monorepo management skill for AI-native development. This skill should be used when working with Nx workspaces, project graphs, affected detection, code generation, and caching. Use when: analyzing dependencies, running affected commands, generating code, configuring Nx Cloud, or optimizing build performance. Invoke nx-mcp tools for documentation queries.

Also in: markdown

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install mjunaidca/mjs-agent-skills/nx-monorepo
skilz install mjunaidca/mjs-agent-skills/nx-monorepo --agent opencode
skilz install mjunaidca/mjs-agent-skills/nx-monorepo --agent codex
skilz install mjunaidca/mjs-agent-skills/nx-monorepo --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/mjunaidca/mjs-agent-skills
2. Copy the agent skill directory:
cp -r mjs-agent-skills/.claude/skills/nx-monorepo ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Stars
1
Forks
2
Type
Technical
Meta-Domain
development
Primary Domain
ci cd
Market Score
17

Agent Skill Grade

B
Score: 81/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
22/30
Ease of Use
22/25
Writing Style
9/10
Utility
18/20
Modifiers: -2

Areas to Improve

  • Missing TOC for 392-line file
  • No reference files despite length
  • Inconsistent workflow structure

Recommendations

  • Address 2 high-severity issues first
  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-24

Developer Feedback

Looking at how you've structured the Nx configuration patterns here—there's some solid fundamentals, though I'm curious about the decisions around workspace boundaries and dependency graph visualization, since that's where a lot of monorepo implementations stumble.

Links:

The TL;DR

You're at 81/100, solidly in B territory. This is graded against Anthropic's skill best practices, and your biggest strength is Writing Style (9/10)—the instructions are clear and direct. The biggest drag is Progressive Disclosure Architecture (22/30), where a 392-line file without a table of contents or reference files makes navigation tough.

What's Working Well

  • Concrete command examples: You're showing actual nx graph, nx test, and nx affected patterns rather than hand-wavy descriptions. That's the right call.
  • Clear trigger phrases: "Analyzing dependencies", "affected commands", "nx-mcp tools"—these map directly to what developers actually ask for.
  • Strong Python integration section: The uv workspace setup (lines 210-293) is detailed and addresses a real pain point that most Nx docs gloss over.
  • Objectivity throughout: No marketing fluff, just technical substance.

The Big One: File Size Without Navigation

Your skill is 392 lines in a single SKILL.md file, but there's no table of contents and no reference files. This matters because Progressive Disclosure Architecture (PDA) is about meeting developers where they are—quick answers up top, deeper dives available if needed.

The fix: Add a TOC right after the metadata block:

## Table of Contents
- [Overview](#overview)
- [MCP Tools](#mcp-tools-available)
- [Core CLI Commands](#core-cli-commands)
- [Python & uv Integration](#pytho...

Report Security Issue

Found a security vulnerability in this agent skill?