Conciseness

Every sentence adds operational information Claude would not know — the MCP server name, its setup command, 'never run `lowdefy dev` yourself or choose a port', the `directory` parameter, the HTTP fallback routes, and exact tool names. There is no padding or explanation of known concepts, matching the 5 anchor ('every token earns its place').

Actionability

The body names concrete, directly callable tools (`lowdefy_list_types`, `lowdefy_get_schema`, `lowdefy_get_examples`, `lowdefy_get_doc`, `lowdefy_search_docs`) and exact HTTP routes (`GET /lowdefy-docs/blocks`, `/lowdefy-docs/schema/{kind}/{type}`, `/lowdefy-docs/examples/{type}`). Per the rubric's scoring notes, an instruction-only skill without code is not penalized when the guidance is this executable; it matches the 5 anchor.

Workflow Clarity

A clear numbered lookup sequence (list types → get schema → get examples → get doc/search) with unambiguous, named steps. It sits above the 3 anchor (sequence present, checkpoints implicit — here 'Never guess type names' acts as an explicit guardrail) but below the 5 anchor, which expects an explicit validation checkpoint such as verifying written config against the fetched schema before finishing. The operation is read-only lookup, so the destructive/batch cap does not apply.

Progressive Disclosure

The skill is under 50 lines, has no bundle files (no references/, scripts/, or assets/ exist), and all detailed documentation is sourced at runtime from the MCP tools rather than inlined. Per the rubric guideline, skills under 50 lines with no need for external references can score 5 with well-organized sections, which this numbered-list structure provides.

Specificity

The description enumerates multiple concrete actions — 'writing or editing Lowdefy YAML config — pages, blocks, operators, actions, connections, or requests' and 'Looks up exact type names, schemas, and examples' — with comprehensive coverage of its domain. It clearly matches the 5 anchor rather than 4, since no meaningful action in the niche is left unlisted.

Completeness

It explicitly answers 'when' ('Use when writing or editing Lowdefy YAML config — pages, blocks, operators, actions, connections, or requests') and 'what' ('Looks up exact type names, schemas, and examples from the running dev server instead of guessing') with concrete trigger phrases, in third person. This matches the 5 anchor exactly rather than 4, where the 'when' would be less specific.

Trigger Term Quality

Natural terms a user would say — 'Lowdefy', 'YAML config', 'pages', 'blocks', 'operators', 'actions', 'connections', 'requests' — are well covered, but synonyms and file-name/extension variants (e.g., 'lowdefy.yaml', '.yaml') are absent. This sits between the 4 anchor (good coverage, a few natural terms missing) and the 5 anchor (synonyms and extensions included), landing at 4.

Distinctiveness Conflict Risk

'Lowdefy' names a clear niche with distinct, domain-specific triggers and near-zero overlap risk with other skills. It matches the 5 anchor ('clear niche with distinct triggers; minimal conflict risk').