Conciseness

Lean imperative writing throughout ("The spec is the reference. Do not add a field, enum value, or endpoint that is not in the spec.") with no explanation of concepts Claude already knows (Zod, REST, npm, builds are never introduced). Version numbers (8.10/8.11, 0.0.93→0.0.94) are operational facts of this version-tree workflow, and the issue-#39752 note is a necessary currency guard, so no padding penalty applies.

Actionability

Fully executable guidance throughout: exact commands ("grep -n \"agent-instances\" zeebe/gateway-protocol/src/main/proto/v2/rest-api.yaml", "npm run build -w @camunda/camunda-api-zod-schemas", "gh workflow run publish-zod-schemas.yml --repo camunda/camunda --ref main -f dry_run=false"), exact file paths, a real PR diff, and copy-paste TypeScript/JSON snippets for endpoints, vite entries, and package exports.

Workflow Clarity

Nine explicitly sequenced procedures with numbered cross-references ("Do Procedure 7 and Procedure 8"). Procedure 8 is a dedicated validation pass (build, package typecheck, workspace typecheck, format, lint) with error-recovery feedback ("If a command shows errors, find the cause and remove it"; "If a consumer type error occurs, change the consumer code or the MSW mocks"). The irreversible publish is gated by an explicit safety checkpoint ("Do not start the workflow yourself") plus post-publish verification via "npm view @camunda/camunda-api-zod-schemas version" — so the destructive-operation cap does not apply.

Progressive Disclosure

The body is well organized (terms table, rules, numbered procedures, examples table) and its references to [reference.md](reference.md) are clearly signaled and one level deep. However, the actual bundle contains no reference.md (no references/ directory at all), so the offloaded "Spec to Zod" mapping table, "Names" table, and changelog template are unreachable — breaking navigation to content the procedures depend on. This is better than anchor 2 (nothing is inlined or buried) but the dangling reference caps it below anchor 4's "references mostly clear" placement.

Specificity

Enumerates comprehensive concrete operations ("add, change, or remove schemas, fields, enums, filters, sort fields, or endpoints", "align the package with the OpenAPI spec", "add a module or a release-line version tree", "increase the package version and prepare a release"), matching the anchor-5 example; however, the rubric penalizes second-person voice ("Use when you add...") by one point on this dimension, lowering it to 4.

Completeness

The "when" is explicit and multi-condition (anchor-5 quality), but the "what" exists only implicitly inside the trigger clauses — no statement of what the skill provides (procedures/rules for changing the package). It sits between anchors 4 and 5: stronger than anchor 4 (whose weakness is an under-explicit "when") but not clearly answering "what" the way anchor 5 requires.

Trigger Term Quality

Comprehensive natural trigger terms for the niche: the package name "@camunda/camunda-api-zod-schemas", "schemas", "fields", "enums", "filters", "sort fields", "endpoints", "OpenAPI spec", "module", "release-line version tree", "package version", and "release", with add/change/remove synonyms covering variations.

Distinctiveness Conflict Risk

Names a specific package, its monorepo path ("webapp/client/packages/camunda-api-zod-schemas/"), and the spec directory — a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.