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.

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/brutalist-skill/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable design-system spec with concrete values and executable CSS, held back by a redundant meta section, reference-style (rather than workflow-style) organization, and no progressive disclosure structure.

Suggestions

Remove the §1 Skill Meta block, which duplicates the YAML frontmatter description and adds tokens without new guidance.

Consider extracting the typography font lists and color/effect catalogs into a references file (e.g. REFERENCE.md) so SKILL.md stays a concise overview with one-level-deep pointers.

Add a short ordered 'How to apply this system' sequence (pick mode → set palette → apply typography → add effects → validate against directives) to make the workflow explicit.

Dimension	Reasoning	Score
Conciseness	The spec is largely lean and value-dense, but the §1 Skill Meta description redundantly restates the frontmatter and editorializing like 'deliberately discarding conventional consumer UI patterns' could be trimmed.	2 / 3
Actionability	It gives copy-paste-ready guidance: exact hex codes, named fonts, concrete clamp/em/line-height ranges, and executable CSS such as the scanline 'repeating-linear-gradient' and 'display: grid; gap: 1px'.	3 / 3
Workflow Clarity	Content is organized into logical sections with clear mode-selection directives ('Pick ONE per project'), but it is a reference spec rather than a sequenced workflow, with no checkpoints or validation steps.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a single 93-line monolithic file with no bundle files or one-level-deep references to split out the detailed font/color/effect catalogs.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 vivid, distinctive description with an explicit trigger clause, weakened only by its noun-heavy framing that lists characteristics rather than concrete actions and by a few non-natural trigger terms.

Suggestions

Lead with a concrete action verb, e.g. 'Designs and builds web interfaces that fuse...' so the capability is explicit, not just the aesthetic.

Add common user trigger terms such as 'brutalist UI', 'terminal/CRT dashboard', or 'tactical interface' alongside the evocative phrasing.

Dimension	Reasoning	Score
Specificity	The description names the domain and concrete visual characteristics ('Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects') but uses no verbs/actions, so it reads as an aesthetic descriptor rather than a statement of what the skill does.	2 / 3
Completeness	It states what the skill produces (the industrial/terminal aesthetic system) and provides an explicit when-clause ('For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints'), satisfying both what and when.	3 / 3
Trigger Term Quality	Natural terms like 'data-heavy dashboards, portfolios, or editorial sites' appear, but evocative phrases such as 'Swiss typographic print' and 'declassified blueprints' are less what a user would say, and common variations like 'brutalist UI' or 'terminal UI' are absent.	2 / 3
Distinctiveness Conflict Risk	The niche — fusing Swiss typographic print with military terminal aesthetics into declassified-blueprint interfaces — is highly specific and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Leonxlnx/taste-skill
Commit: b177427

Reviewed: 5 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.