CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

corner-diagonals

Apply diagonal-cut corners and chamfered edges to buttons, cards, panels, and container shells. Use when a design needs precise geometric framing, sci-fi UI surfaces, clipped-corner controls, or engineered sharp containers instead of rounded pills or plain rectangles.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, highly actionable reference: executable code throughout, sensible design tokens, and useful guardrails (Avoid, Quick Checks). The main improvement levers are deduplicating the repeated polygon definitions and tightening the slight redundancy across Scope, Visual Target, and Recommended Patterns.

Suggestions

Extract the repeated clip-path polygon into one shared utility (or reference the .cut-all/.cut-shell class) instead of duplicating it in each button variant, saving tokens and guaranteeing consistency.

Trim overlap between Scope, Visual Target, and Recommended Patterns, which restate the same consistency and motif guidance three times.

Add a one-line ordering cue at the top (tokens → shape → pattern → checks) to make the implicit workflow explicit for agents applying this to a component set.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of clip-path or CSS basics), but the identical clip-path polygon is repeated verbatim four times across .cut-all, .cut-shell, .cut-button, and .cut-button-secondary where a shared class would do — minor padding that keeps it just below anchor 5.

4 / 5

Actionability

Every example is copy-paste-ready CSS/HTML with design tokens, three cut-size variants, hover and focus-visible states, and patterns spanning buttons, bordered shells, and panels — fully executable and covering the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Content follows a clear progression (tokens → core shapes → bordered shell → buttons → tuning → checks) and the "Quick Checks" section plus 44px/focus guidance act as quality checkpoints, but there is no explicit step sequence or validation loop; anchor 4 fits since the skill exceeds the under-50-line simple-skill exception.

4 / 5

Progressive Disclosure

A single self-contained SKILL.md with well-organized section headers and no bundle files to navigate; all content is appropriately inline for its size, though the secondary-button and shell variants could plausibly live in a references file — anchor 4 rather than 5.

4 / 5

Total

17

/

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 with a clear niche, explicit what-and-when structure, and concrete natural-language triggers. Its only gaps are a single action verb rather than a list of distinct capabilities and a few missing synonyms for corner-cut styling.

Suggestions

Enumerate a couple of distinct actions beyond "apply" (e.g., tuning cut sizes per component scale, or building bordered clip-path shells) to strengthen capability coverage.

Add common synonyms such as "beveled" or "cut corners" to the trigger phrase list to catch more user phrasings.

DimensionReasoningScore

Specificity

"Apply diagonal-cut corners and chamfered edges to buttons, cards, panels, and container shells" names concrete techniques and multiple target component types, but offers essentially one action verb rather than the multiple specific actions of anchor 5.

4 / 5

Completeness

It explicitly answers "what" (apply diagonal-cut corners and chamfered edges to named component types) and "when" ("Use when a design needs precise geometric framing, sci-fi UI surfaces, clipped-corner controls, or engineered sharp containers") with concrete trigger phrases — a direct match for anchor 5, not anchor 4 whose when-clause is less specific.

5 / 5

Trigger Term Quality

Natural user phrases like "clipped-corner controls", "sci-fi UI surfaces", and "rounded pills" are present, but a few common synonyms (e.g., "beveled corners", "cut corners") are missing, matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Triggers like "chamfered edges" and "clipped-corner controls" carve a clear niche, but broader phrases ("precise geometric framing", "sci-fi UI surfaces") create minor overlap risk with general UI-design skills, fitting anchor 4 rather than anchor 5's minimal-conflict bar.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MengTo/Skills

Path

agent-skills/web-design/corner-diagonals/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.