agentsclimarketplace

Enforce scannable density

Skill jpoindexter/design-case-study-skills/skills/enforce-scannable-density

Evidence-backed UX and AI-agent case study skills for Codex and Claude

Install
npx -y skills add jpoindexter/design-case-study-skills --skill enforce-scannable-density

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Edit a portfolio case study for high signal, compact hierarchy, and fast scanning without losing evidence. Use when a draft is fluffy, repetitive, slow to navigate, paragraph-heavy, full of generic process language, or needs concise headings, key-value blocks, comparison matrices, captions, and technical spec blocks.

SKILL.md

2.0 KB, as published. Nobody here has run it

Enforce Scannable Density

Make complexity easier to find, not merely shorter. Apply the reduction, organization, and time-to-understand passes in references/density-pass.md.

Workflow

  1. Write the reader’s five highest-value questions.
  2. Measure whether the answer to each is visible in the title, summary, headings, captions, or first sentence of a section.
  3. Remove throat-clearing, repeated context, passive constructions, generic process claims, and unsupported praise.
  4. Group related evidence and give each section one job.
  5. Move the outcome, constraint, and pivotal decision earlier.
  6. Choose the lightest fitting form:
    • prose for causal explanation;
    • bullets for non-sequential factors;
    • key-value blocks for compact facts;
    • tables only for records with shared comparable fields;
    • monospace blocks only for commands, logs, or technical specifications.
  7. Preserve quantitative data, caveats, ownership, attribution, and evidence labels.
  8. Run a 30-second scan test and list any answer still difficult to locate.

Never manufacture density by shrinking type, stacking unrelated facts, turning prose into decorative tables, or deleting uncertainty.

Output

Return the revised structure and copy, a cut/move/convert ledger, the five-question scan result, and any evidence weakened by the edit.

Example

Input:

We were very excited to embark on a comprehensive process that involved looking at
many different approaches before ultimately deciding on a new approvals experience.

Expected outcome:

Decision — Replace blanket approvals with risk-based gates.
Evidence needed — alternatives considered, approval threshold, and measured effect.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.