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

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/logical-properties/SKILL.md

Quality

Content

65%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 well-structured and uses progressive disclosure effectively via a single real reference file, but it is held back by code/mappings deferred entirely to the reference and a lack of explicit sequencing and verification steps in the body itself.

Suggestions

Add a minimal in-body conversion table or 1-2 inline code examples (e.g. margin-left → margin-inline-start) so the skill is actionable without opening the reference.

Make the workflow explicit with numbered steps (Check → Fix → Verify) and pull the verification guidance from references/rule.md into a short 'Verify' checkpoint in the body.

Trim the intro paragraph and Quick Reference to avoid duplicating the 'Why It Matters' content already in references/rule.md.

Dimension	Reasoning	Score
Conciseness	The body is lean with short, well-delimited sections and assumes Claude's competence; the only over-explanation is the intro paragraph and Quick Reference, which partly duplicate content already present in references/rule.md.	4 / 5
Actionability	The Check section lists specific physical properties to find (margin-left, padding-right, border-left, left/right), which is concrete, but the actual conversion mappings and executable code examples live only in references/rule.md rather than the body itself.	3 / 5
Workflow Clarity	A rough Check → Fix → Explain → Code Review sequence is implied, but there are no explicit numbered steps and no validation/verification checkpoint in the body; because converting CSS properties is a batch/refactor operation, the missing validation caps this at 3.	3 / 5
Progressive Disclosure	The body is a clear overview with well-signaled one-level-deep navigation ('see references/rule.md', which exists) and the rule-page URL; content is appropriately split between overview and the single reference file.	5 / 5
	Total	15 / 20 Passed

Description

70%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 targets a niche (CSS logical properties for RTL/i18n) with a present 'Use when' trigger and several natural keywords. Its main weaknesses are an awkwardly embedded rule title, slightly narrow trigger phrasing, and non-comprehensive action coverage.

Suggestions

Reword 'related to Use CSS logical properties for i18n and RTL support' to remove the duplicated rule-title phrasing, e.g. 'related to CSS logical properties for i18n and RTL support'.

Broaden the 'when' clause with additional natural triggers users might say, such as 'Use when adding RTL/i18n support, auditing stylesheets for physical properties, or fixing right-to-left layout bugs'.

Add 1-2 more concrete actions (e.g. 'convert margin/padding/border physical properties to inline/block equivalents') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (reviewing stylesheets, component styles, responsive behavior for CSS logical properties/RTL) and a couple concrete actions ('Check the rendered layout across breakpoints and interaction states before proposing a fix'), but coverage is not comprehensive and the embedded rule-title phrasing is awkward.	3 / 5
Completeness	Explicitly answers 'when' via 'Use when reviewing stylesheets, component styles, and responsive behavior...' and states 'what' (review/fix logical-property usage), but the 'when' is tied to a single review scenario rather than broader trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms a user would say — 'stylesheets', 'component styles', 'responsive behavior', 'RTL', 'i18n', 'breakpoints', 'interaction states' — with only minor synonyms missing (e.g. no .css extension or 'right-to-left').	4 / 5
Distinctiveness Conflict Risk	The CSS logical properties / i18n / RTL niche is clearly distinguishable from other skills with minimal conflict risk, though the opening 'reviewing stylesheets, component styles, and responsive behavior' is somewhat broad before being narrowed.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/logical-properties/SKILL.md
Commit: 30756a7

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.