Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.
86
83%
Does it follow best practices?
Impact
90%
1.40xAverage score across 3 eval scenarios
Passed
No known issues
Build target audit script
Uses nx show project --json
100%
100%
Does NOT read project.json directly
100%
100%
Uses --json flag for structured output
53%
100%
Uses jq for programmatic processing
80%
100%
Uses --withTarget filter
0%
100%
target-audit.json has target names per project
100%
100%
target-audit.json has summary by target
100%
100%
Library dependency impact report
Uses nx graph --print
70%
100%
Uses jq to find dependents
0%
100%
Uses jq to find library's own deps
0%
100%
Uses --json for structured output
50%
50%
Checks package manager / uses npx prefix
100%
66%
dependency-report.json has consumers
100%
100%
dependency-report.json has library deps
100%
100%
CI affected scope calculator
Uses --affected flag
100%
100%
Uses --base flag
100%
100%
Excludes e2e projects with --exclude
0%
100%
Uses tag filter syntax
25%
0%
Uses --json flag for programmatic output
100%
100%
ci-scope.json has affected_projects
100%
100%
ci-scope.json has publishable_affected
100%
100%
76a3678
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.