Conciseness

In ~96 lines it covers a 9-group CLI with zero explanation of concepts Claude already knows: prerequisites are two install lines, capabilities live in a compact table, and every section is commands. The reappearance of `app snapshot`/`session set-var` across the orientation section and the workflow serves distinct purposes (explanation vs. sequence), so every token earns its place — anchor 5 rather than anchor 4's 'minor instances that could be trimmed'.

Actionability

Fully executable, copy-paste-ready commands cover the common agent cases: `cli-anything-iterm2 --json app snapshot`, `app current`, `session send "git status"`, `session scrollback --tail 200 --strip`, `session split --vertical --use-as-context`, and labeled `session set-var user.role` examples. Matches anchor 5; not 4 because there is no missing key detail for the shown cases.

Workflow Clarity

The 'Typical Agent Workflow' is a clear 4-step numbered sequence (orient → establish context → interact → create workspace) with a built-in send→read-scrollback feedback step, matching anchor 4. Not 5 because there are no explicit validation/error checkpoints (e.g., what to do if context isn't set or a sent command fails); not 3 because the sequence is coherent and verification via reading output is present, if implicit.

Progressive Disclosure

The body is a clean overview with a 'Reference Files' table that signals exactly when to read each of 12 one-level-deep reference files ('Read only what the task requires — each file is a single narrow concern'); all 12 listed files exist in references/ with no nested cross-references, and detail is appropriately deferred. Matches anchor 5's well-signaled, easy-navigation structure.

Specificity

Enumerates many concrete actions ('send text to iTerm2 sessions, read live terminal output and scrollback history, manage windows/tabs/split panes, run tmux -CC workflows, broadcast to multiple panes'), but opens with the over-claim 'the only way to actually send text to iTerm2 sessions' — AppleScript or the bundled it2 utility are alternatives — which the rubric's over-claim penalty drops below the comprehensive anchor 5.

Completeness

Explicitly answers both: what ('Provides the cli-anything-iterm2 commands — the only way to actually send text... read/write iTerm2 preferences') and when ('Read this skill... whenever the user wants to DO something with iTerm2: orient..., send a command, check what's running, read output...'). Written in third person, mirroring the anchor-5 example structure; not score 4 since the 'when' is fully explicit rather than improvable.

Trigger Term Quality

Natural user phrasings are comprehensively covered with synonyms: 'orient in an existing workspace, send a command, check what's running, read output, set up a layout, use tmux through iTerm2, automate panes, or configure preferences', plus 'iTerm2 shell integration or scrollback'. This matches the comprehensive-synonyms anchor rather than anchor 4's 'a few natural terms missing'.

Distinctiveness Conflict Risk

The iTerm2 niche is distinct with iTerm2-named triggers throughout, but phrases like 'use tmux through iTerm2', 'show macOS dialogs', and 'automate panes' carry minor overlap risk with generic tmux, terminal-automation, or macOS-automation skills — fitting anchor 4's 'minor overlap risk with closely related skills' rather than anchor 5's minimal conflict risk.