Lean table-driven reference (actions, quadrant mapping, NL→action mapping, inference rules) with no padding or explanation of concepts Claude already knows; every section earns its tokens.

Gives an executable curl template, a parameter-complete action table, and a concrete copy-paste bulk-create JSON payload, rather than pseudocode or abstract direction.

The single POST endpoint is unambiguous, but destructive (delete, complete) and batch (bulk-create) operations lack any validation or verification checkpoint, which caps this at 2 per the rubric note.

Sections are well organized, but bundle files (references/setup-guide.md, scripts/quadrants-cli.sh) exist yet are never linked or signaled from the body, and the inline API reference is content that could live in a separate file.

Lists multiple concrete actions — "create, view, complete, or organize tasks" and "listing projects, adding tasks (single or bulk), viewing priority tasks, completing tasks, and getting project overviews" — matching the multiple-specific-actions anchor, not the partial domain-only level below.

Both halves are explicit: the 'what' (manage tasks on the Eisenhower matrix with enumerated capabilities) and the 'when' (a 'Use when...' clause plus a 'Triggers on...' clause), so it is not capped at 2 for a missing trigger clause.

"Triggers on mentions of 'quadrants', 'tasks', 'to-do', 'eisenhower', 'priority matrix', or task management requests" covers natural phrasings a user would actually say, rather than only technical jargon.

Distinctive triggers like 'quadrants', 'eisenhower', and 'priority matrix' carve a clear niche unlikely to collide with other skills, rather than the overlapping level below.