CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

arrange

Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

61

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 ./templates/skills/impeccable/arrange/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured, actionable design-guidance body with a clear assess-plan-improve-verify flow and concrete values and CSS patterns. Main weaknesses are duplicated sections that inflate token cost and a single external reference that does not resolve within this skill's bundle.

Suggestions

Deduplicate the spacing-scale guidance: 'Plan Layout Improvements' and 'Establish a Spacing System' repeat the same 'consistent scale (Tailwind, rem tokens, custom)' advice nearly verbatim — merge into one section; the same applies to the repeated squint-test and card-monotony points.

Fix the reference path: 'reference/spatial-design.md' is a file in another skill's bundle, not this one — either vendor a copy into this skill's references/ directory or reword to a plain instruction (e.g., 'see the frontend-design skill's spatial design reference') so the link doesn't dangle.

Add a short feedback loop after 'Verify Layout Improvements': instruct to fix any failed check and re-verify, and consider adding a compact complete CSS example (spacing tokens + a grid/flex pattern) to lift actionability to copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient bullet-style guidance, but there is real duplication: the spacing-scale advice appears nearly verbatim in both 'Plan Layout Improvements' and 'Establish a Spacing System', and the squint test, card-grid monotony, and 'left-aligned with asymmetry feels more designed' points each appear twice. Fits anchor 3 ('mostly efficient but could be tightened') better than anchor 4, where only minor trimming would be needed.

3 / 5

Actionability

Concrete throughout for an instruction-only skill: pixel ranges (8-12px siblings, 48-96px sections), 'repeat(auto-fit, minmax(280px, 1fr))', 'grid-template-areas', clamp(), semantic token names (--space-xs), and a z-index scale. Not 5 because there are no complete copy-paste-ready examples covering common cases; comfortably above anchor 3 since guidance is directly executable, not pseudocode.

4 / 5

Workflow Clarity

Clear sequence — mandatory preparation (/frontend-design, /teach-impeccable), Assess, Plan, Improve, Verify — ending in an explicit verification checklist. Not 5 because there is no fix-and-recheck feedback loop after the Verify step and no mid-process checkpoints; not 3 since the sequence and a final validation checklist are present. No destructive/batch cap applies.

4 / 5

Progressive Disclosure

Sections are well organized, but the body's only reference points outside this bundle ('reference/spatial-design.md' from the frontend-design skill) — it is not resolvable within this skill, which has no references/ directory — and all detail lives inline with duplicated material that could be split out. Fits anchor 3 ('some structure but references not clearly resolvable / could be better organized') more than anchor 4.

3 / 5

Total

14

/

20

Passed

Description

83%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 strong description: third-person, concise, with an explicit 'Use when...' clause covering natural trigger phrases. Minor improvements possible in trigger synonyms (whitespace, padding) and in naming more concrete capabilities.

DimensionReasoningScore

Specificity

"Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy" lists several concrete actions in third person, comparable to anchor 4's 'extracts text, fills forms, converts pages'. Not 5 because all actions stay at the 'improve/fix X' level without naming concrete techniques or deliverables; not 3 because coverage goes beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ("Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy") and when ("Use when the user mentions layout feeling off, spacing issues...") with concrete trigger phrases — a direct match to the anchor-5 example pattern.

5 / 5

Trigger Term Quality

"layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition" gives good natural-phrase coverage users would actually say. Not 5 because common synonyms like "whitespace", "padding/margin", "grid feels repetitive", or "arrangement" are missing; clearly above anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The layout/spacing/rhythm niche is fairly distinct with specific triggers (crowded UI, alignment, monotonous grids), but it overlaps with general frontend-design and general design-critique skills. Not 5 due to that overlap with closely related design skills; clearly more distinct than anchor 3's generic 'works with document files'.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

fengshao1227/ccg-workflow

Path

templates/skills/impeccable/arrange/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.