Conciseness

The body is lean — concrete setup steps, executable commands, example outputs, and a compact troubleshooting table — with only minor trimmable content, e.g., the '## API Reference (curl)' section largely duplicates what the bundled Python script already does. This matches the score-4 anchor 'Efficient; minor instances of over-explanation that could be trimmed'; it is not 5 because of that curl duplication, and not 3 because there is no padding or explanation of concepts Claude already knows.

Actionability

Everything is copy-paste ready: numbered token-generation steps ('Account → Settings ... + New Access Token'), exact env-var block, runnable commands ('$CANVAS list_assignments 12345 --order-by due_at'), concrete JSON output examples, and curl equivalents. This matches the score-5 anchor 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'. It is not 4 because there are no gaps — even edge cases (empty course list, wrong institution) are covered in Troubleshooting.

Workflow Clarity

The single-purpose read-only workflow is unambiguous: a numbered setup sequence, an explicit first-use validation checkpoint ('On first use, verify auth by running $CANVAS list_courses — if it fails with 401, guide the user through setup'), and error-recovery guidance in the Troubleshooting table. This matches the score-5 anchor 'Clear sequence with explicit validation steps; feedback loops for error recovery'. It is not 4 because validation and recovery paths are explicit, not merely implied.

Progressive Disclosure

The body is a clear, well-sectioned overview; the 160-line implementation is correctly externalized to 'scripts/canvas_api.py', which exists in the bundle and is accurately described ('Python CLI for Canvas API calls'); no buried or nested references. This matches the score-5 anchor 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'. It is not 4 because there are no organization gaps — every inline section (setup, usage, output, rules, troubleshooting) belongs inline at this skill's size.

Specificity

"Fetch Canvas LMS courses and assignments via API token" names the domain (Canvas LMS) and two concrete actions (fetch courses, fetch assignments), matching the score-3 anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not 4 because only two actions are listed with no breadth of coverage (e.g., no mention of filtering, due dates, or pagination), and not 2 because the actions are concrete rather than generic.

Completeness

The 'what' is clear ("Fetch Canvas LMS courses and assignments via API token") but there is no 'when' / 'Use when...' clause or equivalent trigger guidance anywhere in the description, which per the judging guidelines caps completeness at 3 ('Has a clear what but when is missing or only weakly implied'). It is not 4 because no usage context is even implicitly suggested, and not 2 because the 'what' is specific and unambiguous.

Trigger Term Quality

The description contains relevant natural keywords — "Canvas LMS", "courses", "assignments" — but misses common variations users would actually say (e.g., "homework", "class", "grades", "Instructure", "syllabus"), matching the score-3 anchor 'Some relevant keywords but missing common variations or synonyms'. It is not 4 because several natural trigger phrases are absent, and not 2 because the terms present are domain-specific rather than generic.

Distinctiveness Conflict Risk

"Canvas LMS" is a clearly named, narrow niche with distinct triggers (courses/assignments of a specific LMS platform), so conflict with other skills is minimal — matching the score-5 anchor 'Clear niche with distinct triggers; minimal conflict risk'. It is not 4 because the domain identifier is unambiguous rather than merely 'mostly distinct'.