Conciseness

Every passage carries platform-specific, non-obvious contracts ("A name is not an id", "--output json writes to stdout; warnings and confirmations go to stderr", bounded comment reads, "What is never right is reading all nine because you are not sure"). No padding and no explanation of concepts Claude already knows; not 4 because there is no passage that could be trimmed without losing a real failure-mode warning.

Actionability

Concrete commands and flags throughout: "--output json", "multica <command> --help", "--roots-only --summary --compact", "--thread <thread-id> --tail 30", "comment add --steer", "multica workflow". Not 5 because no complete copy-paste-ready command example is given (e.g. a full `multica issue list --output json` invocation); not 3 because the guidance is executable and specific, not vague direction.

Workflow Clarity

Clear sequence: open the one reference the task needs, read before you write (run the read-only list/get first), and propose rather than make unrequested mutations, with error-recovery guidance (use --help when a command's shape is unclear; classify before concluding when behavior looks wrong). Not 5 because there is no explicit post-write verification loop; not 3 because the destructive-write validation checkpoint (read-only verification before any mutation) is explicitly present.

Progressive Disclosure

A routing table maps all nine existing, one-level-deep reference files to their domains (all verified present in references/ and covering the claimed topics), with explicit guidance on how many to open and a warning against reading all of them. Matches the anchor example exactly; not 4 because navigation and content split have no organization gaps.

Specificity

Enumerates ten concrete platform domains ("issue and PR contracts, sub-issues, charts and files in comments, mentions, agents, squads, autopilots, projects, runtimes, skill import") with near-comprehensive platform coverage. Not 5 because the list names domains/topics rather than the concrete actions performed on them (e.g. no "link a PR" or "create a squad"); not 3 because coverage goes well beyond 1-2 areas.

Completeness

Explicitly answers both: what ("Multica platform actions ... issue and PR contracts, sub-issues, ... skill import") and when ("Use for Multica platform actions the runtime brief does not fully cover ... Not for the product code you are working on"), with a bidirectional trigger clause and concrete trigger domains. Anchor 4's caveat that the 'when' could be more explicit does not apply.

Trigger Term Quality

Natural keywords users would say in this context are present: "issue", "PR", "comments", "mentions", "agents", "squads", "autopilots", "projects", "runtimes", "skill import". Not 5 because common synonyms and variations (e.g. "pull request", "webhooks", "workflows") are missing; not 3 because keyword coverage is broad, not partial.

Distinctiveness Conflict Risk

Clear niche ("Multica platform") with distinct triggers and an explicit exclusion clause ("Not for the product code you are working on") that separates it from adjacent coding skills. Minimal conflict risk; not 4 because there is no meaningful overlap with closely related skills.