Conciseness

The ~40-line body assumes Claude's competence, skips concept padding, and lets every line carry actionable guidance, matching the 'lean and efficient; every token earns its place' anchor; not a 2 because there is no unnecessary explanation to tighten.

Actionability

Provides fully executable agt CLI commands with a real shell-variable pattern (e.g., 'agt get workers ... -o json | jq -r ".team"' and 'agt worker ensure-ready --name <worker-name> --team "$TEAM_CR"'), matching the copy-paste-ready anchor; the <worker-name> placeholder is justified, not pseudocode.

Workflow Clarity

Clear sequence (resolve Team CR -> read CLI fields -> use room IDs -> lifecycle after checking files) with an explicit validation checkpoint ('If CLI output is missing a required room ID or Matrix ID, stop and report a metadata problem. Do not guess.'), matching the explicit-checkpoints anchor; not a 2 because validation is stated, not implicit.

Progressive Disclosure

Under 50 lines with no external references needed and well-organized sections (Source Of Truth, What To Read From CLI, Lifecycle), meeting the simple-skill allowance for a 3; no bundle files exist to verify against.

Specificity

Lists multiple concrete actions ('assigning tasks, sending cross-room messages, recovering projects, handling heartbeat, waking/sleeping workers') and specific state fields (room ID, Matrix ID, worker phase), matching the 'lists multiple specific concrete actions' anchor; not a 2 because coverage is comprehensive rather than partial.

Completeness

Two explicit trigger clauses ('Use before any Leader action that depends on...', 'Always use this skill when...') clearly answer when, and the enumerated actions and state fields answer what, meeting the explicit-both anchor; not a 2 because the 'when' is explicit rather than implied.

Trigger Term Quality

Trigger phrases like 'assigning tasks' and 'waking/sleeping workers' are natural for this system's users, but the description leans heavily on internal jargon ('Matrix ID', 'heartbeat', 'worker phase') and lacks common-variation breadth, so it sits at the 'some relevant keywords but missing common variations' level rather than full coverage.

Distinctiveness Conflict Risk

Triggers are tightly scoped to AgentTeams/Matrix organization management, giving it a clear niche that is unlikely to fire for unrelated skills; not a 2 because the specificity leaves little overlap with similar skills.