Conciseness

The body is lean and assumes competence: it explains only OpenMAIC-specific contracts (the document model tree, op semantics, pointer escaping as ~1/~0, pagination via nextOffset, NFKC normalization behavior, the 2 KiB media placeholder) — none of which Claude would already know. Tables carry the bulk of the content compactly ('Tool vocabulary', 'Addressing', op table, routing table) and there is no padded prose or restatement of generic concepts, matching the 'every token earns its place' anchor.

Actionability

Guidance is highly concrete: exact path syntax ('path:/scenes/<order|sceneId>', '/scenes/3', '/content/questions/1/options/0/label'), a per-op field table, and literal workflow commands ('Read the target scene with detail:"source"'... 'Pass the returned nextOffset back as offset'). It stops short of a complete worked example of a full tool call or op payload, leaving a minor gap — 'mostly executable with minor gaps' (4) rather than fully copy-paste-ready (5).

Workflow Clarity

The 'Read before write' section gives an explicit 6-step sequence with validation checkpoints ('Read the same source path again and verify the stored value', 'use detail:"text" or grep_stage when the check is "no old copy remains"'), the patch section documents atomicity with a failure loop ('If op 2 fails, op 1 is not persisted'; a rejected batch 'changed nothing'), and rejected ops route to the matching reference chapter — a clear sequence with explicit validation, feedback loops, and a hard-rules checklist, matching the 5 anchor.

Progressive Disclosure

SKILL.md is an overview that routes by need via a one-level-deep table ('Quiz questions, options, answers, grading fields → references/quiz.md', etc.), and all four referenced files exist in the bundle (quiz.md, widget.md, actions.md, pbl.md, each a substantial single-chapter field reference). The slide-dsl material is delegated to the installed skill rather than duplicated. Clear overview, well-signaled one-level-deep references, easy navigation — the 5 anchor.

Specificity

The description lists multiple concrete, specific actions: 'reading and editing an OpenMAIC stage document with read_stage, patch_stage, and grep_stage', 'routes to field-level references for quizzes, interactive widgets, actions, and PBL projects', and explicitly scopes the slide-dsl skill as the slide canvas manual. This is comprehensive coverage of the skill's capabilities with named tools, matching the 'lists multiple specific concrete actions' anchor; no gaps found that would justify 4.

Completeness

The 'what' is explicit (map for reading/editing stage documents with the three named tools and routing to references) and the 'when' is explicit with concrete trigger conditions: 'Load it before patching a structure you have not patched before, when patch_stage rejects an operation, or whenever the path ... to the field you need is uncertain'. This matches the anchor for clearly answering both what AND when with concrete trigger phrases; not the 4 anchor where 'when' could be more specific.

Trigger Term Quality

Natural trigger words include 'patching a structure', 'path from a stage, outline, scene, content object, or action to the field you need', 'patch_stage rejects an operation', plus domain nouns like 'quizzes', 'interactive widgets', 'PBL projects'. Coverage is good but leans technical — a user saying 'edit a page' or 'fix a quiz question' would partially match, and a few natural synonyms are missing, which fits 'good keyword coverage; a few natural terms missing' rather than comprehensive 5.

Distinctiveness Conflict Risk

The niche is narrow (OpenMAIC stage document tooling) and the description explicitly disambiguates from the nearest competing skill: 'the installed slide-dsl skill remains the complete slide canvas manual'. Trigger conditions reference tool-specific events (patch_stage rejects an operation), minimizing wrong-skill triggers — a clear niche with distinct triggers per the 5 anchor.