CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pick-ui-library

Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.

Quality

90%

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

The canonical home for this skill is pick-ui-library in emilkowalski/skills

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary lookup skill body: lean token-efficient tables with links, unambiguous recommendation procedure, explicit decision splits for ambiguous pairs, and concrete mismatch heuristics for catching hand-rolled alternatives. Nothing is padded, nothing needs external files, and every section is immediately actionable.

DimensionReasoningScore

Conciseness

The body is pure lookup tables and decision guidance — it explains nothing Claude already knows (no library tutorials, no concept explanations), and every prose note (e.g. "A simple hover or fade doesn't need it — plain CSS transitions are the right tool there") is decision-relevant, matching anchor 5's "every token earns its place".

5 / 5

Actionability

Concrete, executable guidance throughout: "Look at `package.json` first", "Recommend one library, state what it's for in one sentence", a named library with a link for every task, explicit split rules (Liveline vs recharts, clsx vs cva), and specific mismatch heuristics — for an instruction-only skill this fully covers the common cases (anchor 5).

5 / 5

Workflow Clarity

The simple-skill exception applies: the four-step procedure (identify task → check what's installed → recommend one → explicit fallback when uncovered) is unambiguous, includes a dependency-churn guardrail ("don't churn the dependency without being asked"), and involves no destructive or batch operations that would require validation checkpoints.

5 / 5

Progressive Disclosure

No bundle files exist or are needed — the ~80-line body is dense tabular lookup data that constitutes the skill's entire value, appropriately kept inline and organized into clear, navigable sections (UI components, motion, charts, interaction, state/styling, mismatches) with no buried references.

5 / 5

Total

20

/

20

Passed

Description

75%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 specific, well-scoped description that names a concrete action and enumerates the covered task domains in natural language, with explicit invocation guidance. It falls just short of top marks because the when-clause is mechanical rather than task-based and several natural trigger terms for covered tasks (animation, dialogs, theming) are absent.

Suggestions

Add the natural trigger terms for tasks the body already covers but the description omits — e.g. "animation", "dialogs/dropdowns", "dark mode/theming" — so users' phrasing matches the description (trigger_term_quality).

Add a task-based trigger clause alongside the invocation mechanics, e.g. "Use when the user asks which library to use for a frontend task like toasts, charts, or drag and drop" (completeness).

State the ecosystem the curated list targets (the picks are React-centric: cmdk, Sonner, dnd kit, zustand, next-themes) to sharpen distinctiveness against generic styling or charting skills (distinctiveness_conflict_risk).

DimensionReasoningScore

Specificity

"Pick the right library for a given frontend task" is a concrete action, and the description enumerates nine specific task domains ("numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling"), with "and more" conceding minor gaps — matching anchor 4 rather than 5's comprehensive multi-action coverage.

4 / 5

Completeness

The 'what' is clear (picking from a curated, opinionated list with enumerated domains) and a 'when' is explicitly stated ("Only runs when explicitly invoked; it does not trigger on its own"), but that when-clause describes invocation mechanics rather than task-based triggers, fitting anchor 4's "'when' could be more explicit or specific".

4 / 5

Trigger Term Quality

Natural user phrasing is well covered ("toasts", "drag and drop", "charts", "command menus", "virtualization", "OTP inputs"), but natural terms for tasks the skill covers — "animation", "dialogs/dropdowns", "dark mode/theming" — appear only in the body, so a few natural terms are missing (anchor 4, not 5).

4 / 5

Distinctiveness Conflict Risk

The curated-list framing and enumerated niche make it mostly distinct, and it never auto-triggers, but broad terms like "charts", "state", and "styling" carry minor overlap risk with closely related frontend skills — anchor 4 rather than 5's minimal conflict risk.

4 / 5

Total

16

/

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

englishstreetventures/osn

Path

.agents/skills/pick-ui-library/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.