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

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%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.

The body is a well-organized, highly concrete design spec with directly applicable CSS values and strong, unambiguous decision rules. Its weaknesses are minor: the opening meta section is redundant with the frontmatter, code appears as fragments rather than complete components, and the long inline spec could benefit from splitting some parameter detail into reference files.

Suggestions

Trim or remove Section 1's 'Skill Meta' block, which duplicates the frontmatter description in padded prose.

Add one complete copy-paste component example (e.g. a telemetry dashboard tile) so the CSS fragments assemble into a runnable whole.

Consider moving the detailed font lists, full color palettes, and effect recipes into a reference file referenced from SKILL.md to reduce inline length and aid discovery.

Dimension	Reasoning	Score
Conciseness	The body is largely dense and directive-driven with concrete parameters and minimal explanation of concepts Claude already knows; the main trim opportunity is Section 1's 'Skill Meta' prose, which restates the frontmatter description in expanded, somewhat florid form.	4 / 5
Actionability	It supplies concrete, directly applicable values throughout (clamp() ranges, em/leading figures, exact hex codes, 'display: grid; gap: 1px;', a full repeating-linear-gradient, and specific semantic tags), though the CSS appears as fragments rather than a complete copy-paste component example.	4 / 5
Workflow Clarity	The guidance is unambiguous with strong gating rules ('Pick ONE per project and commit', 'CRITICAL: Choose ONE substrate palette', 'Absolute rejection of border-radius'), but the body is organized by design dimension rather than as a sequenced build workflow, so it reads as a spec with decision gates rather than a numbered procedure with checkpoints.	4 / 5
Progressive Disclosure	The content is well-structured into eight numbered, clearly headed sections and is self-contained with no bundle files to navigate; it sits just under the top anchor because the ~117-line spec could optionally split detailed parameter tables (font lists, full palettes, effect recipes) into reference files.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

The description is specific, distinctive, and answers both what the skill produces and when to apply it, with a clear niche and good keyword coverage. The main gap is that capabilities are framed as aesthetic attributes rather than concrete actions, and the 'when' clause lists contexts rather than explicit user trigger phrases.

Suggestions

Lead with a concrete action verb (e.g. 'Generate web interfaces that fuse...') so capabilities read as actions rather than attribute lists.

Strengthen the 'when' clause to mirror user utterances, e.g. 'Use when the user asks for industrial-brutalist, tactical-telemetry, or Swiss-industrial interfaces for dashboards, portfolios, or editorial sites.'

Add one or two common synonyms (e.g. 'neo-brutalism', 'brutalist web design') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics') and lists four concrete visual attributes (rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects), but frames them as characteristics rather than concrete actions, so it sits at the domain-plus-attributes level rather than comprehensive capability coverage.	3 / 5
Completeness	It states a clear 'what' (raw mechanical interfaces with the listed aesthetic properties) and an explicit 'when' clause ('For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints'), but the 'when' lists application contexts rather than user-uttered trigger phrases, keeping it just below the top anchor.	4 / 5
Trigger Term Quality	It surfaces several natural terms a user might say ('Swiss typographic print', 'military terminal', 'data-heavy dashboards', 'portfolios', 'editorial sites', 'declassified blueprints'), giving good keyword coverage, though a few common variations (e.g. 'neo-brutalism', 'brutalist web') are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined ('industrial brutalist', 'Swiss typographic print fused with military terminal aesthetics', 'declassified blueprints') with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/brutalist-skill/SKILL.md
Commit: f580271

Reviewed: about 17 hours 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.