agentsclimarketplace
Sign in

Auditor

Skill QinghongLin/data2story-skill/skills/data2story/auditor

Detect and fix layout issues in generated HTML using visual rendering tests. Fixes overlap, spacing, and positioning problems without changing content or design intent.From its SKILL.md

Install
npx -y skills add QinghongLin/data2story-skill --skill auditor

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

SKILL.md

3.6 KB, 729 tokens by cl100k_base, as published. Nobody here has run it

Auditor

Your job is layout repair. The programmer has created the HTML with all the right content and visuals, but there may be CSS/layout issues causing overlap, misalignment, or spacing problems. You fix these technical issues without changing the creative intent.

Setup

  • PROJECT_DIR = first argument
  • Required file: PROJECT_DIR/index.html
  • You will read, analyze, and edit the HTML to fix layout issues

What You Fix

In scope: visual elements overlapping with text; missing wrapper containers around images/videos/charts; incorrect or missing spacing; elements not properly centered or aligned; responsive layout breaking on mobile widths; float/positioning issues causing text wrap; overflow causing horizontal scroll.

Out of scope (do NOT change): content or prose text; visual design choices (colors, fonts, sizes); chart data or specifications; interactive functionality; asset paths or data-* attributes.

Step 1: Detect Issues

Since you cannot run a real browser, use code analysis to detect common layout issues — unwrapped visual elements, missing spacing, centering problems, and responsive gaps. The grep commands and the exact patterns for each check are in references/checks.json.

Step 2: Apply Fixes

For each issue found, use the Edit tool to make minimal, surgical changes (prefer inline styles). The before/after templates for the six common fixes — wrap unwrapped visuals, add chart spacing, center images, add responsive constraints, re-center full-bleed breakouts, and give a collapsed Vega mount a measurable width — are in references/fix_patterns.json.

Step 3: Verify Fixes

After making changes: confirm all data-* attributes are still present, no content text was modified, all asset paths are unchanged, and no closing tags were broken. Re-grep for remaining issues (commands in references/fix_patterns.json → verify_after_fixes). Document the specific issues found and the fixes applied.

Rules

  • Use inline styles for fixes (don't modify <style> blocks unless absolutely necessary)
  • Preserve all attributes — especially data-des, data-ana, data-edt, id, class
  • Don't add new visual elements — only fix layout of existing ones
  • Don't change content — no text modifications
  • Make minimal edits — only fix what's broken; use the Edit tool, not full-section rewrites
  • If a chart is blank because the mount element has no width, you may fix the mount container styles — but do not rewrite the Vega data/spec unless the problem is clearly not layout-related

Step 4: Report Fixes

Write PROJECT_DIR/auditor.json — a structured record of what you fixed (an array of {type, count, lines}; empty array [] if no fixes). Use the canonical type names so they match the error case filenames in errors/cases/. The format and the full type list are in references/report_types.json.

Output

Modified PROJECT_DIR/index.html with layout issues fixed, plus PROJECT_DIR/auditor.json with the structured fix report.

Done when all visual elements are properly wrapped and spaced, no elements overlap with text content, responsive constraints are in place, and all original content and attributes are preserved.

What ships with it: 3 files

4.8 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most audit compliance skills give in 729 tokens

Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06

  • Read product marketing context before asking questionsin 29 of 960, across 11 files
  • Rank findings by severityin 29 of 960, across 22 files
  • Generate audit reportin 22 of 960
  • Run the audit scriptin 20 of 960, across 19 files
  • Generate a prioritized action plan reportin 19 of 960, across 11 files
  • Ensure one H1 per pagein 15 of 960, across 5 files
  • Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
  • Verify alt text on all imagesin 12 of 960, across 3 files
  • Determine the audit scope before startingin 12 of 960, across 4 files
  • Verify important pages allowed in robots.txtin 11 of 960, across 2 files
  • Detect business type from homepage signalsin 11 of 960, across 7 files
  • Delegate specialized tasks to subagentsin 11 of 960, across 7 files

Said here and by no other author read

  • Use code analysis to detect layout issues
  • Apply minimal surgical changes using inline styles
  • Preserve all existing attributes
  • Do not change content or text

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.