CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/rtl-rendering-tester

Build-an-X workflow for verifying RTL (right-to-left) layouts - runs the test suite under Arabic / Hebrew / Persian / Urdu locales, asserts the `dir="rtl"` attribute is set, verifies layout mirrors correctly (text alignment, icon positions, scrollbar location), uses logical CSS properties (`start`/`end` over `left`/`right`) per W3C guidance, captures per-locale screenshots for visual review. Use when the app supports RTL languages.

76

Quality

95%

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

Overview
Quality
Evals
Security
Files

Quality

Content

87%

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

An efficient, highly actionable skill body with executable code and a well-split supplementary reference. Its only meaningful gap is the absence of an explicit failure-feedback loop for the batch RTL test run, which caps workflow clarity.

Suggestions

Add an explicit validation/retry loop after running the suite: e.g. 'Run `npx playwright test`; if any RTL locale fails, fix the mirroring/logical-property issue and re-run until all locales pass' to lift workflow_clarity.

Make the per-locale coverage explicit in the body (e.g. a short checklist of the four locales x desktop/mobile) so the batch run's verification scope is unambiguous.

Add a one-line note on expected screenshots baseline location/management to tie Step 6's visual regression into the feedback loop.

DimensionReasoningScore

Conciseness

Lean body of executable code blocks with brief, purposeful prose and a tight anti-patterns table; no padding explaining concepts Claude already knows. Could not move below 3 as nearly every token earns its place.

3 / 3

Actionability

Each step ships fully executable Playwright TypeScript with real locators and assertions (e.g. `expect(page.locator('html')).toHaveAttribute('dir', 'rtl')`), plus a concrete fix column in the anti-patterns table.

3 / 3

Workflow Clarity

Six steps are clearly sequenced, but this batch test-running workflow across four locales lacks an explicit run→fail→fix→re-run feedback loop, so per the guidelines workflow_clarity is capped at 2. Not 1 because the sequence and per-step assertions are present; not 3 because checkpoints are implicit rather than explicit error-recovery.

2 / 3

Progressive Disclosure

Body is a concise overview; detailed screenshot/CI/dirname material is one level deep in a real, clearly signaled `references/rtl-checks.md`, with a References section listing sibling skills.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description that names concrete RTL verification actions, includes natural trigger terms and language names, and provides an explicit 'Use when' clause. It is clearly distinct from sibling i18n skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'runs the test suite under Arabic / Hebrew / Persian / Urdu locales', 'asserts the `dir="rtl"` attribute is set', 'verifies layout mirrors correctly (text alignment, icon positions, scrollbar location)', 'uses logical CSS properties (`start`/`end` over `left`/`right`)', 'captures per-locale screenshots'.

3 / 3

Completeness

Explicitly answers what (the enumerated verification actions) and when with the clause 'Use when the app supports RTL languages.'

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered — 'RTL', 'right-to-left layouts', and the language names 'Arabic / Hebrew / Persian / Urdu' — matching how users phrase RTL issues.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (RTL rendering verification across specific locales) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents