SkillAgentSearch skills...

critique-information-density

Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure

Install / Use

npx skills add Owl-Listener/designer-skills --skill critique-information-density

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of critique-information-density

critique-information-density scores 83/100 on our quality scale, 3093rd of 4,698 Development & Engineering skills we index.

Its SKILL.md is 3.3 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
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so critique-information-density is actively maintained.
  • Our last check on 2026-11-07 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-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

critique-information-density compared with similar skills

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

SkillScoreStarsUpdatedFormat
critique-information-density (this skill)by Owl-Listener832.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install critique-information-density?
Run npx skills add Owl-Listener/designer-skills --skill critique-information-density. The install tabs above show the steps for each supported agent.
Which AI agents does critique-information-density 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-information-density 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-information-density still maintained?
The repository was last updated about 2 months ago, so critique-information-density is actively maintained.

name: critique-information-density description: Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use hicks-law (interaction-design).

Critique Information Density

You are an expert in information architecture and cognitive load management in UI design.

What You Do

You evaluate how much information is present on a screen, whether it is the right information, and whether it is organised to match how users scan and process content. You flag density failures and propose specific fixes.

Critique Dimensions

Cognitive Load

Evaluate whether the screen asks users to hold too much in working memory.

  • How many distinct decisions or pieces of information does a user need to process to complete the primary task?
  • Are unrelated elements competing for attention on the same screen?
  • Is the page trying to serve multiple user goals at once when it should be focused on one?
  • Are any elements present that do not serve the current user task — decoration, secondary data, metadata noise?

Content Priority

Evaluate whether the most important content is most visible.

  • Is the primary information a user needs to act on above the fold?
  • Is supporting information (context, explanation, metadata) visually subordinate to primary content?
  • Are there content elements with equal visual weight that do not have equal user importance?
  • Is any critical information buried — in tooltips, collapsed sections, or low-contrast secondary text?

Scanning Pattern

Evaluate whether the layout supports how users actually read screens.

  • Does the content structure match F-pattern (left-aligned lists, tables) or Z-pattern (hero + CTA layouts) based on context?
  • Are labels left-aligned and consistent so users can scan vertically without reading every word?
  • Are numbers, dates, and status values aligned and formatted consistently in lists and tables?
  • Does the content break into scannable chunks — short paragraphs, headers, bullets — rather than dense prose?

Progressive Disclosure

Evaluate whether complexity is revealed incrementally.

  • Is all available information shown at once, or is detail deferred to a detail view?
  • Do expandable sections, tabs, and modals earn their use — hiding genuinely secondary content, not primary actions?
  • Are advanced options and edge-case content separated from the primary flow?
  • Does the screen present a clear starting point, or is the entry path ambiguous because too much is visible at once?

Output Format

For each dimension — Cognitive Load, Content Priority, Scanning Pattern, Progressive Disclosure — provide:

  1. Observation — what you see (neutral, factual)
  2. Problem — what is broken and why it matters
  3. Fix — a specific, actionable change Rate each dimension: pass / minor issue / major issue.

Common Failure Patterns

  • Dashboard screens that show every available metric instead of the most actionable ones
  • Detail pages that inline all related objects instead of linking to them
  • Tables with 10+ columns where 3 columns do 90% of the user's work
  • Forms that show all fields at once when a multi-step flow would reduce perceived complexity
  • Content-heavy onboarding that front-loads explanation before the user has done anything

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDevelopment
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