Conciseness

The body is a five-line lean stub — "Refer to stream skill and follow its platform routing. Use the skill for the app's platform, with `stream-react` as the default..." — with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the top anchor.

Actionability

It provides an executable command ("Install a missing skill with `getstream skills <name>`") and a concrete default ("`stream-react` as the default for web or generic app work"), which is mostly executable guidance. It stops short of anchor 5 because the command needs a placeholder substituted and platform-detection guidance is delegated to the referenced skill rather than specified.

Workflow Clarity

This is a simple, single-purpose skill under 50 lines whose single action — route to the platform skill, defaulting to stream-react, installing if missing, then following it — is unambiguous and logically sequenced. The simple-skill exception applies, and no destructive or batch operations exist to require validation checkpoints.

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, and assets/ are absent) and no need for external references; the well-organized single heading plus delegation to the stream skill is appropriately minimal, matching the under-50-lines guideline for a top score.

Specificity

The description names the domain ("Compatibility entrypoint for requests naming stream-builder") and one concrete action ("Routes app work to the appropriate platform skill"), matching the anchor for domain plus 1-2 concrete actions without comprehensive coverage. It falls below anchor 4 because there is only a single action and "appropriate platform skill" leaves which skills unspecified, and above anchor 2 because a concrete routing action is stated rather than generic naming.

Completeness

It answers both what ("Compatibility entrypoint... Routes app work to the appropriate platform skill") and when ("for requests naming stream-builder"), an explicit trigger clause equivalent to "Use when...", so the missing-trigger cap of 3 does not apply. It falls short of anchor 5 because the "what" is thin ("appropriate platform skill" is vague) and there are no concrete trigger phrases beyond the single product name.

Trigger Term Quality

It contains one specific, relevant keyword ("stream-builder") but no natural variations or synonyms (e.g., chat builder, GetStream, messaging UI), matching the "some relevant keywords but missing common variations" anchor. It is above anchor 2 because the keyword is a specific product name users would actually say, and below anchor 4 because natural companion terms are entirely absent.

Distinctiveness Conflict Risk

The trigger "stream-builder" is a clear, distinct niche keyword unlikely to fire for unrelated skills, matching "mostly distinct; minor overlap risk". It is not a 5 because the skill deliberately overlaps with the closely related "stream" skill it forwards to, and "Routes app work" is broad phrasing that could collide with sibling platform skills.