nx-gradle-plugin-version-bump

Bump the dev.nx.gradle.project-graph plugin version. Use when updating the Gradle project graph plugin version across the codebase, creating the migration files, and updating migrations.json.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly effective operational skill: precise inputs, five concrete file-level steps with executable templates, explicit verification commands, and a final safety check that halts work if the diff deviates from the previous bump PR. The only slack is a few sentences of rationale about deprecated migrations.json keys and dist paths that could be cut or moved to a reference file.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — file paths, exact templates, and commands with almost no explanation of concepts Claude already knows. Minor over-explanation could be trimmed, e.g. 'The paths are dist-prefixed because the published package ships only dist/' and the aside about deprecated 'cli' and 'factory' keys in older migrations.json entries, which keeps it at the score-4 anchor rather than the fully lean score-5 anchor.	4 / 5
Actionability	Every step gives exact file paths and copy-paste-ready templates ('export const gradleProjectGraphVersion = NEW_VERSION', the full migration TS template, the migrations.json entry), plus concrete commands ('nx run-many -t test,build,lint -p gradle') and a literal commit message format. This is fully executable guidance covering the common case, matching the score-5 anchor.	5 / 5
Workflow Clarity	The five steps are clearly sequenced, inputs are collected up front with worked examples (OLD_VERSION => NEW_VERSION), and there are two explicit validation stages: the 'Verification' test/build/lint command and 'Final Verification' with a compare-to-last-PR check and a stop-and-ask error-recovery loop ('If you do, ask for more information and stop all changes'). This matches the score-5 anchor's explicit validation and feedback loops, which matters because this is a batch operation across 5 files.	5 / 5
Progressive Disclosure	The skill is self-contained with no bundle files (no references/, scripts/, or assets/ exist), well-organized into Required Inputs / Steps / Verification / Commit Convention sections, and its one external reference to the author-migration skill is clearly signaled and one level deep. At ~150 lines with two full templates inlined, it sits between the score-4 anchor (good structure, minor organization gaps — the templates could live in a references/ file) and the score-5 anchor, which the sub-50-line exception would only reach for a shorter skill.	4 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, well-formed description: it states a single concrete action in the what-clause and enumerates explicit triggering scenarios in the when-clause, all anchored by a uniquely named plugin. Third-person imperative voice is correct and there is no fluff.

Dimension	Reasoning	Score
Specificity	The description names the exact plugin ('dev.nx.gradle.project-graph') and lists several concrete actions — bumping the version, 'creating the migration files, and updating migrations.json' — with only minor coverage gaps (it omits the build.gradle.kts/versions.ts edits). It lists several specific actions but is not fully comprehensive, matching the score-4 anchor rather than the score-5 anchor's complete coverage.	4 / 5
Completeness	It explicitly answers both what ('Bump the dev.nx.gradle.project-graph plugin version') and when ('Use when updating the Gradle project graph plugin version across the codebase, creating the migration files, and updating migrations.json') with concrete trigger phrases. This matches the score-5 anchor; the score-4 anchor's 'when could be more explicit' does not apply since the when-clause enumerates the specific triggering scenarios.	5 / 5
Trigger Term Quality	Natural user phrasings are present: 'bump', 'Gradle', 'plugin version', 'migration files', 'migrations.json'. These cover how a user would request this task well, though common synonyms like 'upgrade' or 'project-graph plugin' as a bare phrase are missing, placing it just below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The fully qualified plugin name 'dev.nx.gradle.project-graph' and 'migrations.json' give it a clear niche with distinct triggers and minimal conflict risk against any other skill. It is far more specific than the score-4 anchor ('minor overlap risk with closely related skills').	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: nrwl/nx
Path: .claude/skills/nx-gradle-plugin-version-bump/SKILL.md
Commit: ab845a8

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.