CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

accessible-canvas-workflows

Review Excalidraw UI changes for accessible keyboard, focus, dialog, shortcut, and announcement behavior. Use as one lens in a code review run.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured review-lens skill: an unambiguous trace procedure, explicit report/do-not-report thresholds, and reporting format guidance, all with zero padding. The only improvement space is making the referenced "nearby Excalidraw pattern" guidance concrete, for example via a short reference file listing existing dialog, focus, and shortcut patterns.

DimensionReasoningScore

Conciseness

The body is lean and dense — Scope bullets enumerate checks without padding, and it never explains concepts Claude already knows (what accessibility or Excalidraw is); every section earns its tokens.

5 / 5

Actionability

As an instruction-only skill it gives concrete, executable direction — a specific trace procedure ("Trace how it is reached, how focus enters and leaves it, how keyboard events are handled…") and explicit report/withhold thresholds — but leaves minor gaps: "the nearby Excalidraw pattern to follow" points nowhere specific, and no example violations are given.

4 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action is unambiguous: start at the changed control, trace the listed aspects, apply the Threshold decision criteria, and report in the stated format; the Threshold section functions as an explicit checkpoint (and the operation is read-only review, so no validation cap applies).

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the content is well organized into clearly labeled Scope, Method, Threshold, and Reporting sections with no buried or dangling references (no bundle files exist, and none are referenced).

5 / 5

Total

19

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, lean description that names a distinct niche and enumerates concrete review areas without padding. Its main weaknesses are the thin 'when' clause (usage context without explicit trigger phrases) and missing common accessibility synonyms that users might naturally say.

Suggestions

Rewrite the usage clause with explicit trigger phrases, e.g., "Use when reviewing changes to Excalidraw canvas UI, dialogs, toolbar actions, or keyboard shortcuts" instead of the more abstract "Use as one lens in a code review run".

Add natural synonyms such as "a11y", "screen reader", or "accessibility" so the description triggers when users use those terms instead of "accessible".

Consider naming one or two additional concrete actions beyond "review" (e.g., identify the nearby Excalidraw pattern to follow) to round out capability coverage.

DimensionReasoningScore

Specificity

The description names a specific domain and enumerates five concrete review targets ("accessible keyboard, focus, dialog, shortcut, and announcement behavior"), but relies on a single action verb ("Review") rather than listing multiple distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is explicit and concrete, and a usage clause is present ("Use as one lens in a code review run"), but the 'when' lacks concrete trigger phrases (e.g., 'when reviewing changes to Excalidraw dialogs or shortcuts'), so it matches the 4 anchor rather than 5.

4 / 5

Trigger Term Quality

It includes natural terms users would say — "Excalidraw", "UI changes", "accessible", "keyboard", "shortcut", "code review" — but omits common synonyms and variations such as "a11y", "screen reader", "accessibility", or "ARIA".

4 / 5

Distinctiveness Conflict Risk

"Excalidraw" pins the skill to a single named application and a specific review niche (pointer-free access and focus behavior), giving it a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

guypod/excalidraw-factory

Path

review-lenses/accessible-canvas-workflows/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.