CtrlK
BlogDocsLog inGet started
Tessl Logo

neobrutalism

Modern take on brutalism with bold borders, vivid accent colors, and raw, high-contrast layouts on warm surfaces.

53

Quality

60%

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/neobrutalism/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 content is concise and well-structured with concrete foundations and a clear authoring workflow, but it stops short of worked examples and inline validation checkpoints. Adding one example guideline and explicit verify gates would raise actionability and workflow clarity.

Suggestions

Add one short worked example of a component rule (e.g. a Button anatomy with default/hover/focus-visible states tied to actual tokens) to make guidance copy-paste ready.

Insert explicit validation checkpoints inside the workflow — e.g. 'After step 3, verify each rule is anchored to a token or threshold before proceeding.'

Add a compact QA checklist with concrete, executable checks (contrast ratios, token-only values, all required states present) rather than only listing it as a section heading.

DimensionReasoningScore

Conciseness

The body is a lean, well-sectioned set of bullet lists (foundations, rules, workflow, output structure, quality gates) with no padding or explanation of concepts Claude already knows — every line earns its place.

3 / 3

Actionability

It gives concrete foundations (specific tokens, spacing scale 4/8/12/16/24/32, required states) and a clear output structure, but includes no worked example of actual guideline output, so guidance is actionable yet incomplete.

2 / 3

Workflow Clarity

The 'Guideline Authoring Workflow' lists a clean six-step sequence with a closing QA checklist and Quality Gates, but the steps lack inline validation checkpoints and there is no explicit validate→fix→retry feedback loop.

2 / 3

Progressive Disclosure

The skill is a self-contained single file with no external bundle and well-organized sections; with no need for external references, clear sectioning suffices for the top score.

3 / 3

Total

10

/

12

Passed

Description

47%

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 vividly defines the neobrutalism aesthetic but never states the skill's action or when to invoke it. Adding a verb-led capability clause and an explicit 'Use when...' trigger would lift specificity and completeness.

Suggestions

Lead with the action, e.g. 'Authors neobrutalism design-system guidelines with bold borders, vivid accent colors, and raw, high-contrast layouts on warm surfaces.'

Append an explicit trigger clause: 'Use when creating or applying neobrutalism design guidance, brutalist UI styling, or high-contrast bold-border layouts.'

Include the term 'neobrutalism' directly in the description rather than only in the name so it matches natural user phrasing.

DimensionReasoningScore

Specificity

The description contains no action verbs — it characterizes an aesthetic ('Modern take on brutalism with bold borders, vivid accent colors, and raw, high-contrast layouts on warm surfaces') rather than stating what the skill does, mirroring the 'Helps with documents' level of action-less abstraction.

1 / 3

Completeness

It conveys the 'what' indirectly (the design style the skill targets) but provides no 'Use when...' or equivalent trigger guidance, so per the rubric a missing explicit-when clause caps completeness at 2.

2 / 3

Trigger Term Quality

It surfaces some natural terms a user might say ('brutalism', 'bold borders', 'high-contrast', 'accent colors') but misses common variations and the most direct trigger 'neobrutalism' (which only appears in the name, not the description).

2 / 3

Distinctiveness Conflict Risk

The niche is sharply defined — neobrutalism with bold borders and vivid accents on warm surfaces — making it unlikely to trigger for unrelated design skills.

3 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bergside/awesome-design-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.