CtrlK
BlogDocsLog inGet started
Tessl Logo

direction-attribute

Use when reviewing templates, rendered HTML, or shared components related to Set text direction for RTL languages. Validate the final browser-facing markup, not just the source framework abstraction.

66

Quality

80%

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/direction-attribute/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

The body is a well-organized, lean overview that appropriately defers detail to a real references file, with a clear check/fix workflow and checklist. It is held back by a slightly padded motivational opener and the absence of complete copy-paste HTML examples in the body itself.

Suggestions

Trim or remove the motivational opener explaining why RTL matters; Claude already knows this, and the 'Check' section conveys the same need more concretely.

Add one or two complete copy-paste HTML snippets (e.g., `<html lang="ar" dir="rtl">` and a `<bdi>` usage) so the Fix section is executable rather than prose-only.

Consolidate the overlapping inspection guidance between 'Check' and 'Code Review' to reduce redundancy and tighten the workflow.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete Quick Reference bullets, but the motivational opener 'Without proper dir attributes, RTL text displays incorrectly...' and overlap between the 'Check' and 'Code Review' sections could be tightened.

2 / 3

Actionability

Concrete guidance is present (dir values 'ltr'/'rtl'/'auto', <html> and <bdi> elements, CSS logical properties), but no complete copy-paste HTML markup examples appear in the body itself.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence with a Quick Reference checklist is clear and unambiguous for a simple review skill; no destructive/batch feedback loop is required here.

3 / 3

Progressive Disclosure

The body is a concise overview split into clear sections and points to the real one-level-deep 'references/rule.md' for full implementation details, well-signaled at the end.

3 / 3

Total

10

/

12

Passed

Description

90%

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 strong: it pairs an explicit 'Use when' trigger with a concrete validation action and natural frontend terminology for a distinct RTL niche. It is only slightly limited on specificity, naming two actions rather than a comprehensive set.

DimensionReasoningScore

Specificity

Quotes 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup' name the domain and a couple of actions, but only two distinct verbs (review, validate) are present, so it is not a comprehensive action list.

2 / 3

Completeness

It explicitly answers when with 'Use when reviewing templates...' and what with 'Validate the final browser-facing markup, not just the source framework abstraction', satisfying both halves.

3 / 3

Trigger Term Quality

Natural frontend terms users would say are well covered: 'templates, rendered HTML, or shared components', 'RTL languages', and 'text direction'.

3 / 3

Distinctiveness Conflict Risk

The RTL text-direction / rendered-markup-validation niche is specific with distinct triggers unlikely to overlap with unrelated skills.

3 / 3

Total

11

/

12

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
thedaviddias/Front-End-Checklist
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.