CtrlK
BlogDocsLog inGet started
Tessl Logo

multi-version-compliance

Apply or review multi-version support compliance for first-party Nx plugins. Primary entry point: a Linear task ID (NXC-XXXX) from the "Multi-version supported across plugins" milestone — the task carries the resolved support window, findings, and "Needs human decision" items. Falls back to self-discovery when no task exists. Use when asked to "fix multi-version compliance for @nx/X", "do NXC-XXXX", "review this compliance PR", or when working on a branch / PR titled "multi-version support compliance for @nx/X". Covers the canonical shape (assertSupportedPackageVersion, all-generators-enforce-floor.spec.ts, peer dep alignment, requires-gate auditing, user-pin preservation, executor / inferred-plugin feature gating).

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 well-structured, highly actionable skill body: exact commands and MCP signatures, a sequenced six-phase workflow with validation gates and checklists, and clean one-level-deep reference disclosure. The only soft spot is minor reinforcement duplication of critical rules across sections.

Suggestions

Consolidate the 'don't expand scope beyond the task's Findings' rule into one canonical location (e.g., Critical rules) and cross-reference it from the Linear protocol and Phase 3 rather than restating it three times.

In Phase 5, make the test-failure feedback loop explicit (e.g., 'if a test fails: fix the code, re-run the same --testPathPattern, only proceed when green') instead of leaving retry as an implicit footgun warning.

Consider folding the 'Reference PRs' list and the 'Source-of-truth split' table into a reference file or trimming, since they are context-heavy and date-stale by the skill's own admission.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explaining what Nx or peer deps are), with every section earning its place, but a few critical rules are restated across sections — e.g., "don't expand scope beyond the task's Findings" appears in the Linear-fetching protocol, Phase 3 step 12, and Critical rule 1b — which could be trimmed. It is above the 3 anchor (no padding or unnecessary concept explanation) but not fully lean given the reinforcement duplication.

4 / 5

Actionability

Provides copy-paste-ready, executable guidance throughout: exact MCP call signatures (mcp__linear-server__get_issue id="NXC-XXXX"), concrete gh commands (gh pr view <N> --repo nrwl/nx --json state), and specific test commands (npx nx test <plugin> --testPathPattern="all-generators-enforce-floor") plus named spec files. Not the 4 anchor because the examples cover the common cases with no real gaps.

5 / 5

Workflow Clarity

Six sequenced phases with an explicit User OK gate before edits, Phase 1–2 never-writes rule, Phase 5 local verification (test + format), footgun warnings, and the A–F verification checklist. The destructive/batch cap does not apply because validation checkpoints are present, so this clears the 4 anchor with explicit validation and checklists.

5 / 5

Progressive Disclosure

SKILL.md is an overview/workflow that points one level deep to real bundle files (references/canonical-shape.md, anti-patterns.md, gotchas.md, examples.md — all present), with a per-mode "Which references to load" table and an explicit injunction not to pull all of them. Not the 4 anchor because references are clearly signaled and content is appropriately split with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

100%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 strong, third-person description that concretely names the domain and coverage areas, supplies multiple natural trigger phrases, and explicitly answers both what and when. It is distinctive and unlikely to trigger for the wrong skill.

DimensionReasoningScore

Specificity

Names the domain (first-party Nx plugins) and lists multiple concrete coverage areas — "peer dep alignment, requires-gate auditing, user-pin preservation, executor / inferred-plugin feature gating" plus specific symbols like assertSupportedPackageVersion and all-generators-enforce-floor.spec.ts, giving comprehensive coverage. It is not the 4 anchor because there are no minor gaps; the enumeration is broad and item-specific.

5 / 5

Completeness

Explicitly answers both what ("Apply or review multi-version support compliance... Covers the canonical shape (...)") and when ("Use when asked to...") with concrete trigger phrases. Not the 4 anchor because the 'when' is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Provides natural phrases users would actually say — "fix multi-version compliance for @nx/X", "do NXC-XXXX", "review this compliance PR" — plus a branch/PR-title variant, covering synonyms and the NXC task-ID form. Not the 4 anchor because the natural-term coverage is comprehensive rather than missing a few terms.

5 / 5

Distinctiveness Conflict Risk

A clear niche — multi-version compliance for first-party Nx plugins tied to NXC-XXXX tasks and specific reference PRs — with distinct triggers and minimal overlap with other skills. Not the 4 anchor because overlap risk with closely related skills is essentially nil given the highly specific entry points.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
nrwl/nx
Reviewed

Table of Contents

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.