Conciseness

The body never explains concepts Claude already knows (no "what is n8n" or library intro) and every line states a rule, command, or verification gate. It matches the lean anchor 5; the dense packing of conditions is information, not padding, so it does not fall to 4.

Actionability

Fully executable commands appear throughout: `pnpm exec nx show project <project> --json`, the five-target lint/typecheck/test/build/check:pack block, `npx --yes @n8n/scan-community-package@beta <package>@<version>`, and `npm view <package>@<version> author maintainers --json`. Per the rubric's scoring note, the directive prose (secrets in password fields, preserve pairedItem) is instruction-type guidance that is specific and actionable, so nothing drops it below anchor 5.

Workflow Clarity

The phase sequence (route the task, audit before editing, implement deliberately, verify through Nx, post-publication scan) is clear and validation checkpoints are explicit (preflight targets, requiring the scanner's "has passed all security checks" output, editor confirmation, author.email match). It is not 5 because error-recovery loops — what to do when lint, the scanner, or the editor check fails and when to re-run — are implied ("Fix violations rather than disabling ... rules") rather than spelled out as validate-fix-retry steps.

Progressive Disclosure

The body is an overview that routes to two real, clearly signaled, one-level-deep reference files with explicit rules for when to read each or both ("For node fields ... read references/ux-checklist.md"; "Read both references for a verification preflight"). Both files exist and contain no further nested references, matching anchor 5 exactly.

Specificity

"Build, audit, improve, test, or prepare n8n community-node packages for npm and Creator Portal verification" lists multiple concrete actions tied to specific deliverables (npm packages, Creator Portal verification), matching the comprehensive-coverage anchor. It is not the 4 anchor because there are no minor coverage gaps: the verb list spans the full lifecycle of the skill's niche.

Completeness

It explicitly answers both questions: the "what" is the build/audit/improve/test/prepare verb list and the "when" is the explicit "Use for ... ; not for merely authoring or running an ordinary n8n workflow" clause with concrete trigger phrases plus a negative boundary. This matches the anchor-5 example structure exactly.

Trigger Term Quality

The trigger clause enumerates the domain's natural vocabulary — "n8n node UX, credentials, node properties, community-package metadata, scanners, local node development, and verified-node releases" — which is exactly what a user working on this task would say. It exceeds the 4 anchor because no commonly-used variation of the request is missing (build/publish/verify/scan/develop are all represented).

Distinctiveness Conflict Risk

The community-node packaging/verification niche is distinct and the explicit exclusion ("not for merely authoring or running an ordinary n8n workflow") prevents overlap with generic n8n workflow skills. Minimal conflict risk, matching anchor 5.