CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

logical-properties

Use when reviewing stylesheets, component styles, and responsive behavior related to Use CSS logical properties for i18n and RTL support. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

77%

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/logical-properties/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured checklist body with a clearly signaled one-level-deep reference that carries the executable detail. Its weaknesses are a concept-explanation intro paragraph duplicated from the reference file and verification steps that are never surfaced in the body's own Check/Fix workflow.

Suggestions

Cut the intro paragraph (duplicated verbatim from references/rule.md's "Why It Matters") — the Quick Reference bullets already carry the needed context.

Surface a verification step in the body (e.g. after Fix: "Verify the rendered layout across breakpoints and both LTR/RTL directions per references/rule.md#verification") so the workflow's checkpoint isn't buried in the reference.

Inline one concrete conversion example in the Fix section (e.g. margin-left → margin-inline-start) so the body is actionable even before the reference is opened.

DimensionReasoningScore

Conciseness

The opening paragraph ("Physical CSS properties (margin-left, padding-right) are hardcoded to screen directions... Logical properties handle this automatically") explains a concept Claude already knows and is duplicated verbatim in references/rule.md's "Why It Matters". The rest (Quick Reference, Check, Fix) is lean, so this is mostly efficient with one padded section that could be trimmed.

3 / 5

Actionability

Concrete guidance: "Find all uses of margin-left, margin-right, padding-left, padding-right, border-left, border-right, left, right (as positioning)" gives exact search targets, and "Replace left/right margin and padding with inline-start/inline-end equivalents" gives the conversion pattern. Not a 5 because the Fix section itself ("Convert physical direction properties to their CSS logical property equivalents") is generic with no conversion example inline — the executable detail is delegated to the reference.

4 / 5

Workflow Clarity

The Check → Fix sequence plus the Code Review phase ("Flag exact selectors, declarations, or breakpoints that violate the rule in the rendered UI") forms a clear sequence, and validation does exist in the bundle (references/rule.md's Verification section). Not a 5 because no verification checkpoint is surfaced in the body itself — the reader must discover it in the reference.

4 / 5

Progressive Disclosure

The body is a concise overview and the single referenced file, references/rule.md, exists and holds the implementation details, code examples, full physical-to-logical mapping table, and verification steps. The reference is one level deep and clearly signaled ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), with content appropriately split between overview and detail.

5 / 5

Total

16

/

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 solid description with an explicit "Use when" trigger, domain-specific keywords, and concrete verification actions. Its main flaw is the mechanically embedded rule title ("related to Use CSS logical properties for i18n and RTL support"), which reads awkwardly and obscures the skill's core action, plus a few missing natural synonyms like "right-to-left" and "localization".

Suggestions

Rewrite the embedded title into a proper action, e.g. "Use when reviewing stylesheets, component styles, or responsive behavior to convert physical direction properties (margin-left, padding-right) to CSS logical properties for i18n and RTL support."

Add natural trigger synonyms such as "right-to-left", "RTL layouts", or "localization" so users phrasing the need differently still match.

State the core fix action explicitly (convert physical properties to logical equivalents) instead of implying it through the rule title.

DimensionReasoningScore

Specificity

Lists several concrete actions — "reviewing stylesheets, component styles, and responsive behavior", "Check the rendered layout across breakpoints and interaction states", "before proposing a fix" — but the core fix action is only conveyed via the awkwardly embedded rule title, leaving minor gaps rather than comprehensive coverage.

4 / 5

Completeness

Both are present: an explicit "Use when reviewing stylesheets..." trigger clause and a what of "Check the rendered layout across breakpoints and interaction states before proposing a fix". Not a 5 because the garbled "related to Use CSS logical properties" phrasing blurs the core capability rather than stating it clearly as an action.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("stylesheets", "responsive", "breakpoints", "interaction states", "RTL", "i18n") but misses common variations users would say, such as "right-to-left", "localization", or "internationalization" spelled out.

4 / 5

Distinctiveness Conflict Risk

"CSS logical properties for i18n and RTL support" is a clear niche with distinct triggers, though the broad leading clause "reviewing stylesheets, component styles, and responsive behavior" overlaps with closely related CSS/responsive-review skills.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/logical-properties/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.