CtrlK
BlogDocsLog inGet started
Tessl Logo

update-cnw-templates

Update the CNW (create-nx-workspace) template repos (nrwl/empty-template, nrwl/react-template, etc.) to a target nx version via nx migrate, verify each repo, and open a PR per repo. Clones repos it needs - assumes no local checkout. Use when asked to "update the CNW templates", "migrate the templates to nx X", "bump the template repos", or given a version like "update templates to 23.2.0".

74

Quality

93%

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

85%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 strong, highly actionable body: exact commands, liveness/cleanliness gates, revert-and-report feedback loops, and a well-sequenced procedure with draft-PR safety rails. Its one real defect is a missing bundle file — run-all-templates.sh is referenced as 'bundled next to this file' but is absent, breaking step 6 — plus minor redundancy around the no-local-checkout assumption.

Suggestions

Ship the referenced run-all-templates.sh in a scripts/ directory (or remove the step): the body says it is 'bundled next to this file' but no such file exists in the bundle, so the post-merge sanity check cannot be executed.

Trim the repeated no-local-checkout framing — 'This skill makes no assumption that the repos are checked out locally. It clones what it needs. Anyone on the team can run it from a fresh machine' restates what step 2's clone commands already show.

Move the 12-row template table into a reference file (e.g. references/templates.md) with a one-line pointer, keeping SKILL.md as a lean overview; the table is the largest block of static data in the body and is flagged as subject to change.

DimensionReasoningScore

Conciseness

Largely dense command blocks plus non-obvious project facts ('a force-push to main skips PR CI entirely (how the react template broke)', 'single "Initial commit"'), but the no-local-checkout idea is repeated ('This skill makes **no assumption that the repos are checked out locally.** ... Anyone on the team can run it from a fresh machine') alongside an already-explicit clone step — minor trim candidates that keep it below the 5-anchor's 'every token earns its place'.

4 / 5

Actionability

Fully executable throughout: copy-paste bash with exact env flags ('CI=true', 'NX_NO_CLOUD=true NX_DAEMON=false ... --skip-nx-cache'), a ready GitHub API curl with JSON body for the draft PR, exact liveness check URLs, and a concrete report table — matching the 5-anchor, well above the 4-anchor.

5 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced with explicit validation checkpoints and feedback loops for this batch operation: 404 → 'report it', 'git status --porcelain # MUST be empty; if dirty, skip this repo and report', 'If any target fails, **revert that repo (git checkout .) and report** - never open a red PR', plus a post-merge scaffolding sanity check — matching the 5-anchor; the batch-operation cap at 3 does not apply since validation is present.

5 / 5

Progressive Disclosure

Sections are well organized, but section 6 references a bundle file — '`run-all-templates.sh` (bundled next to this file)' — that does not exist in the bundle (no scripts/, references/, or assets/ directories are present), a dangling reference that makes step 6 unrunnable. This is more than the 4-anchor's 'minor organization gaps', fitting the 3-anchor's structural/navigation deficiency.

3 / 5

Total

17

/

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.

The description is exemplary: third-person voice, concrete actions with named tooling, and an explicit 'Use when...' clause with four natural trigger phrases including a version example. It fully answers both what the skill does and when to use it with no vague padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named tooling — 'Update the CNW (create-nx-workspace) template repos ... to a target nx version via nx migrate, verify each repo, and open a PR per repo. Clones repos it needs' — covering what the skill does comprehensively, matching the 5-anchor; it clearly exceeds the 4-anchor since no capability is left out.

5 / 5

Completeness

Explicitly answers both 'what' (update via nx migrate, verify, open a PR per repo, clone as needed) and 'when' ('Use when asked to...' with four concrete trigger phrases), matching the 5-anchor example's shape exactly; not the 4-anchor since the 'when' clause is fully explicit with triggers.

5 / 5

Trigger Term Quality

Covers natural user phrasings with synonyms — 'update the CNW templates', 'migrate the templates to nx X', 'bump the template repos', and a concrete version example 'update templates to 23.2.0' — comprehensive synonym coverage matching the 5-anchor rather than the 4-anchor's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

A clear niche — CNW template repos under nrwl bumped to a specific nx version — with distinct trigger phrasing, so overlap risk with other skills is minimal; matches the 5-anchor, not the 4-anchor which requires residual overlap with closely related skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

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.