CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-ux-enhancements

Automated UX review rules optimized for AI-driven design evaluations, addressing gaps in usability and user empowerment. Complementary to laws-of-ux skill, focusing on efficiency, control, cognitive workload, learnability, and personalization.

58

Quality

68%

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 ./skills/ai-ux-enhancements/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-structured, actionable set of 12 automated UX-review rules with concrete tooling, measurable thresholds, and clear implementation guidance. It is efficient and well-organized, with only minor room to tighten the Background section and consider offloading the rule catalog to a reference file.

DimensionReasoningScore

Conciseness

Each of the 12 rules uses a compact Check/Automation-ideas/Fail-message format that earns its tokens; the Background & Scope section has minor padding that could be trimmed, matching the 4 anchor rather than a clean 5.

4 / 5

Actionability

Rules cite concrete tools (axe-core, Lighthouse, DOM/CSS parsers, NLP similarity) and measurable thresholds (>=80%, <=3 clicks, >20 rows, >90% similarity); as an instruction-only skill the guidance is actionable with minor gaps, fitting anchor 4.

4 / 5

Workflow Clarity

The Implementation Guidance section sequences work (priority order, scoring scheme, tool-to-rule mapping, skip conditions); this is a review/reporting skill rather than a destructive or batch operation, so the validation cap does not apply, and it fits anchor 4.

4 / 5

Progressive Disclosure

The body is a single well-organized file with clear section headers and no nested references (no bundle files present); structure is good and self-contained, though the ~116 lines of detailed rules could arguably be split into a reference file, matching anchor 4.

4 / 5

Total

16

/

20

Passed

Description

61%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 clearly conveys the skill's purpose and distinct niche as an AI-automated complement to existing UX heuristics, but it lacks an explicit 'Use when...' trigger clause, capping completeness. Natural keyword coverage is good though a few synonyms are missing.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when running automated UX/design reviews, accessibility checks, or AI-driven UI audits') to lift completeness above 3.

Include natural synonym trigger terms like 'heuristics' and 'linting' to broaden trigger-term coverage.

Name one or two concrete actions (e.g., 'audits', 'flags', 'scores') instead of only focus areas to raise specificity.

DimensionReasoningScore

Specificity

Names the UX-review domain and lists concrete focus areas (efficiency, control, cognitive workload, learnability, personalization) but does not name concrete actions like 'extract' or 'audit'; sits between anchors 2 and 3, closer to 3.

3 / 5

Completeness

Clearly states what the skill does, but provides no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3; the 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Includes natural phrases a user would say ('Automated UX review', 'AI-driven design evaluations', 'usability', 'user empowerment') with good coverage; a few common synonyms like 'heuristics' are absent, matching the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

Explicitly positions itself as 'Complementary to laws-of-ux skill' with a distinct AI-automation niche, but retains some overlap risk with general UX-review skills, fitting the 4 anchor.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
RoleModel/rolemodel-skills
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.