CtrlK
BlogDocsLog inGet started
Tessl Logo

direction-picker

Optional 3-5 direction picker for users who explicitly ask to compare visual directions.

62

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/atoms/direction-picker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is tight, well-structured, and assumes Claude's competence while delivering concrete behavior for an explicit-trigger UI atom. A small schema or example of the direction-cards question form would push actionability to fully executable.

Suggestions

Add a minimal example or field spec of the direction-cards question form (e.g. the shape of the submitted direction id) to make the guidance fully copy-paste ready.

State an explicit validation/checkpoint on the returned form answer (e.g. confirm it contains a known direction id before locking) to strengthen the convergence workflow.

DimensionReasoningScore

Conciseness

Lean and efficient with no over-explanation of concepts Claude already knows; every line adds non-obvious information about the atom's trigger, completion, and anti-patterns.

5 / 5

Actionability

Gives concrete, executable guidance — 'emit one inline <question-form> with a direction-cards question' and 'lock onto that direction' — but lacks a literal copy-paste snippet or schema of the question form, leaving minor gaps.

4 / 5

Workflow Clarity

The convergence flow is clearly sequenced — emit picker, receive submitted direction id, lock onto it, with backtracking forcing a fresh devloop iteration — with an implicit checkpoint on submission, though no explicit validation step on the returned value.

4 / 5

Progressive Disclosure

A short single-purpose skill with no external references needed and well-organized sections (Convergence, Anti-patterns), which the simple-skill guidance rewards with a top score.

5 / 5

Total

18

/

20

Passed

Description

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

The description is concise and clearly states both what the skill does and the explicit trigger condition, avoiding proactive invocation. It would benefit from a few more natural trigger synonyms and slightly broader action coverage.

Suggestions

Add concrete trigger phrases a user might say, e.g. 'Use when the user asks to compare directions, explore options, or pick between design directions.'

Name a couple more concrete actions (e.g. 'renders direction cards in an inline question form, captures the chosen direction id') to broaden specificity.

DimensionReasoningScore

Specificity

Describes concrete actions — 'present 3-5 distinct visual / structural / tonal directions' and 'emit one inline <question-form> with a direction-cards question' — but coverage is narrow around a single UI mechanism rather than multiple distinct actions.

4 / 5

Completeness

States both what it does (3-5 direction picker) and when to use it (explicit request to compare directions), but the 'when' is a single clause rather than multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

The trigger 'when the user explicitly asks to see or compare direction options' is relevant but uses one phrasing without synonyms or common variations a user might say.

3 / 5

Distinctiveness Conflict Risk

A fairly specific niche (explicit direction comparison) with distinct triggers; minor overlap risk with general planning/design skills but unlikely to fire for the wrong skill.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.