CtrlK
BlogDocsLog inGet started
Tessl Logo

industrial-brutalist-ui

Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.

62

Quality

73%

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/brutalist-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 specification with concrete CSS values and clear sectioning, weakened mainly by grandiose padding that inflates the token budget without adding guidance.

Suggestions

Trim dramatic editorial language ('absolute mastery', 'uncompromising', 'deliberately discarding') to reduce token overhead.

Add one minimal copy-paste starter snippet that assembles a basic grid + typography + color scaffold to lift actionability to fully executable.

Consider moving the font catalogs and hex palettes into a reference file to improve progressive disclosure and keep SKILL.md as an overview.

DimensionReasoningScore

Conciseness

Concrete specs (font names, hex codes, CSS values) are efficient, but dramatic padding like 'absolute mastery', 'uncompromising', and 'deliberately discarding conventional consumer UI patterns' could be trimmed.

3 / 5

Actionability

Provides concrete, mostly-executable guidance — specific fonts, hex colors, clamp() values, and CSS snippets like 'display: grid; gap: 1px' — with only minor gaps and no full copy-paste assembly example.

4 / 5

Workflow Clarity

The numbered sections progress logically (archetypes → typography → color → layout → components → effects → engineering) with clear 'pick ONE' decision points, though no explicit validation checkpoints exist.

4 / 5

Progressive Disclosure

Well-organized into 8 clearly-headed sections in a single self-contained file with no nested references, though at ~90 lines some reference material (typography/color catalogs) could be split out.

4 / 5

Total

15

/

20

Passed

Description

78%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, specific description with a clear niche and natural trigger terms; it explicitly covers both what and when, though the 'when' could be made more explicit with a 'Use when...' phrasing.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when building data-heavy dashboards, portfolios, or editorial sites...') to make the trigger unambiguous.

Reframe key features as concrete actions (e.g., 'Applies rigid grids, extreme type-scale contrast, and analog degradation effects') to strengthen specificity.

DimensionReasoningScore

Specificity

Lists several concrete features — 'Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects' — but expresses them as attributes rather than verb-driven actions, leaving minor coverage gaps.

4 / 5

Completeness

It states what ('Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics') and when ('For data-heavy dashboards, portfolios, or editorial sites'), but the trigger uses 'For...' rather than an explicit 'Use when...' clause.

4 / 5

Trigger Term Quality

Natural user-facing terms like 'data-heavy dashboards, portfolios, or editorial sites' are present, with good coverage though a few synonyms or stylistic variants are missing.

4 / 5

Distinctiveness Conflict Risk

The 'Swiss typographic print with military terminal aesthetics' niche is highly specific with distinct triggers and minimal overlap with other skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Leonxlnx/taste-skill
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.