mcpbeat

Visual Audit

pedrohcgs/visual-audit

Adversarial visual-layout audit of a Quarto `.qmd` or Beamer `.tex` deck. Flags overflow, font inconsistency, box fatigue, spacing, and alignment issues. Use when user says "visual audit", "check the layout", "does this overflow?", "look for visual issues", "audit the slides", or after reworking a deck's appearance. Does NOT check writing or pedagogy — pair with `/proofread` or `/pedagogy-review`.

396 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1440
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill visual-audit

The instruction itself

2 sections, as written by the author

Visual Audit of Slide Deck

Perform a thorough visual layout audit of a slide deck.

Steps

  • Read the slide file specified in $ARGUMENTS
  • For Quarto (.qmd) files:
  • Render with quarto render Quarto/$ARGUMENTS
  • Open in browser to inspect each slide
  • For Beamer (.tex) files:
  • Compile and check for overfull hbox warnings
  • Audit every slide for:

OVERFLOW: Content exceeding slide boundaries

FONT CONSISTENCY: Inline font-size overrides, inconsistent sizes

BOX FATIGUE: 2+ colored boxes on one slide, wrong box types

SPACING: Missing negative margins, missing fig-align

LAYOUT: Missing transitions, missing framing sentences, semantic colors

  • Produce a report organized by slide with severity and recommendations
  • Follow the spacing-first principle:
  • Reduce vertical spacing with negative margins
  • Consolidate lists
  • Move displayed equations inline
  • Reduce image/SVG size
  • Last resort: font size reduction (never below 0.85em)

How to use it

Copy the folder

Take pedrohcgs/visual-audit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.