CtrlK
BlogDocsLog inGet started
Tessl Logo

split-layout-technical

Create a technical split-screen design system with dual panels, fine frame lines, mono metadata, quiet editorial typography, and premium inset surfaces.

55

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/split-layout-technical/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 gives concrete, actionable design-system direction without padding, but an empty Workflow heading and some cross-section repetition prevent it from being fully tight.

Suggestions

Remove or populate the empty '## Workflow' heading rather than leaving a placeholder section.

Deduplicate the framing vocabulary ('inset rules', 'corner markers', 'thin/fine frame lines') that repeats across Visual target, Implementation guidance, and Recommended patterns.

Replace the verbatim description repetition under 'Use When' with concrete triggering scenarios instead of restating the capability.

DimensionReasoningScore

Conciseness

The body assumes Claude's intelligence (no basic-concept explanations) and is mostly lean, but the description is repeated verbatim under 'Use When' and framing ideas ('inset rules', 'thin frame/fine frame lines', 'corner markers') recur across Visual target, Implementation guidance, and Recommended patterns, so not every token earns its place.

2 / 3

Actionability

Guidance is concrete and specific for an instruction-only design skill: named layout primitives ('flex-row', split columns, two-panel grid), named metadata treatments ('top rails, metadata strips, labels, coordinates, system markers'), and concrete defaults ('50/50 by default'); per the rubric's instruction-only note, absence of code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

Although this is a single-purpose design skill where a multi-step workflow is not strictly required, the '## Workflow' section heading is present but empty, leaving structure incomplete; the well-organized surrounding sections keep it above the lowest anchor but the empty workflow gap prevents a top score.

2 / 3

Progressive Disclosure

At under 50 lines with no bundle files and no need for external references, the skill is well-organized into clearly labeled sections (Scope, Visual target, Implementation guidance, Recommended patterns, Tuning knobs, Avoid), satisfying the rubric's simple-skills allowance for a top progressive-disclosure score on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

50%

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 specific about the design-system aesthetic it produces but is essentially a single action with no explicit 'when to use' trigger, which caps completeness and trigger quality at the mid level.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when building product pages, showcases, portfolios, or editorial-tech layouts that need a disciplined two-panel split-screen structure.'

Add concrete action verbs beyond 'Create' (e.g. 'Lay out... frame... label...') to reach the multi-action specificity anchor.

Include common user-facing variations of the trigger term ('split layout', 'two-panel layout', 'two-column design').

DimensionReasoningScore

Specificity

The description names a concrete domain ('technical split-screen design system') and several specific attributes ('dual panels, fine frame lines, mono metadata, quiet editorial typography, and premium inset surfaces'), but it is a single action verb ('Create') rather than the multiple distinct concrete actions (e.g. 'Extract... fill... merge') the top anchor requires.

2 / 3

Completeness

It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric guideline, a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

'split-screen' and 'dual panels' are reasonably natural design terms, but coverage of common variations a user would say is thin (no 'split layout', 'two-panel', 'two-column', '50/50 layout'), matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The 'technical split-screen' niche is fairly specific, but with no explicit triggers and broad overlap with general design-system / layout skills, it could still conflict with similar skills rather than occupying a clearly distinct niche.

2 / 3

Total

8

/

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.

Repository
MengTo/Skills
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.