SkillAgentSearch skills...

critique-brand-consistency

Critique a rendered screen against mood.md, voice.md, and tokens.md

Install / Use

npx skills add Owl-Listener/designer-skills --skill critique-brand-consistency

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Category

Design

Supported Platforms

Universal

Our assessment of critique-brand-consistency

critique-brand-consistency scores 80/100 on our quality scale, 231st of 261 Design skills we index.

Its SKILL.md is 2.8 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so critique-brand-consistency is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

critique-brand-consistency compared with similar skills

All 4 of these similar skills score higher than critique-brand-consistency; compare them before choosing.

SkillScoreStarsUpdatedFormat
critique-brand-consistency (this skill)by Owl-Listener802.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
LocalAIby mudler10050.4ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md

Frequently asked questions

How do I install critique-brand-consistency?
Run npx skills add Owl-Listener/designer-skills --skill critique-brand-consistency. The install tabs above show the steps for each supported agent.
Which AI agents does critique-brand-consistency work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is critique-brand-consistency safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is critique-brand-consistency still maintained?
The repository was last updated about 2 months ago, so critique-brand-consistency is actively maintained.

name: critique-brand-consistency description: Critique a rendered screen against mood.md, voice.md, and tokens.md. Use when those brand files exist and you are checking compliance. For defining the visual language itself, use illustration-style (ui-design).

Critique Brand Consistency

You are an expert in brand expression and design system compliance.

What You Do

You check whether a screen faithfully expresses the brand by comparing it against three project reference files: mood.md (personality and aesthetic direction), voice.md (tone and language guidelines), and tokens.md (design token definitions). Flag every divergence and suggest the correct value or approach.

Reference Files

Before critiquing, locate and read these files from the project root (or wherever the designer specifies):

  • mood.md — Brand personality, aesthetic keywords, visual references, do/don't examples
  • voice.md — Tone of voice, language style, copy do/don't rules, vocabulary
  • tokens.md — Canonical colour, spacing, radius, shadow, and typography token values If a file is missing, note this and skip that dimension — do not invent brand rules.

Critique Dimensions

Mood Alignment

Compare the screen's aesthetic to the mood direction.

  • Does the visual language (imagery style, illustration, iconography, colour feel) match the brand personality keywords?
  • Are any elements tonally off — e.g., a playful brand using cold, corporate styling?
  • Does the overall emotional register of the screen match what the mood file prescribes?

Voice Alignment

Compare all visible copy to the voice guidelines.

  • Does the tone match (e.g., direct vs. conversational, formal vs. friendly)?
  • Are any prescribed vocabulary rules broken — forbidden words, required patterns?
  • Are CTAs, labels, error messages, and microcopy consistent with the voice?

Token Compliance

Compare every design value on screen to the token definitions.

  • Are hardcoded hex values used where a colour token should apply?
  • Are spacing, radius, or shadow values that deviate from tokens present?
  • Are typography tokens applied correctly, or are raw font-size/weight values used?
  • List every non-compliant value with its token equivalent.

Output Format

For each dimension — Mood, Voice, Token Compliance — provide:

  1. Observation — what you see (neutral, factual)
  2. Divergence — what conflicts with the reference file and why it matters
  3. Fix — the exact correction (preferred wording, correct token name, etc.) Rate each dimension: pass / minor issue / major issue.

Common Failure Patterns

  • Hardcoded values drifting from tokens over time
  • Copy written without consulting voice guidelines, defaulting to generic UI language
  • Imagery or illustration sourced outside the brand mood reference
  • Inconsistent radius or shadow values across components on the same screen

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDesign
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions