Get the FREE Ultimate OpenClaw Setup Guide →

document-quality-standards

Scanned
npx machina-cli add skill belumume/claude-skills/document-quality-standards --openclaw
Files (1)
SKILL.md
5.3 KB

Document Quality Standards

Patterns that complement the official document-skills plugin. Apply these alongside xlsx, pdf, docx, and pptx skills.

Visual-First Verification

Core principle: Text extraction misses critical details. Always verify visually.

"Only do python printing as a last resort because you will miss important details with text extraction (e.g. figures, tables, diagrams)."

The Render-Inspect-Fix Loop

For ANY document operation (create, edit, convert):

1. Generate/modify document
2. Convert to PNG:
   pdftoppm -png -r 150 document.pdf output
3. Visually inspect the PNG at 100% zoom
4. Fix any issues found
5. REPEAT until clean

Never deliver a document without PNG verification. This catches:

  • Clipped or overlapping text
  • Broken tables
  • Missing figures
  • Formatting inconsistencies
  • Orphans/widows
  • Unreadable characters

Quick Conversion Commands

# DOCX → PDF → PNG
soffice --headless --convert-to pdf document.docx
pdftoppm -png -r 150 document.pdf page

# PDF → PNG directly
pdftoppm -png -r 150 document.pdf page

# PPTX → PDF → PNG
soffice --headless --convert-to pdf presentation.pptx
pdftoppm -png -r 150 presentation.pdf slide

Typography Hygiene

Hyphen Safety

Never use non-breaking hyphens (U+2011). They cause rendering failures in many viewers.

# WRONG - may render as boxes or break layouts
text = "co‑author"  # U+2011 non-breaking hyphen

# CORRECT - always use ASCII hyphen
text = "co-author"  # U+002D standard hyphen-minus

Detection and fix:

# Find problematic hyphens
import re
if '\u2011' in text:
    text = text.replace('\u2011', '-')

# Also watch for other non-ASCII dashes
text = text.replace('\u2013', '-')  # en-dash
text = text.replace('\u2014', '-')  # em-dash (if hyphen intended)

Citation Format

All citations must be human-readable in standard scholarly format:

  • No internal tool tokens (e.g., 【4:2†source】)
  • No malformed references
  • Include: Author, Title, Source, Date, URL (if applicable)
# WRONG
See source 【4:2†source】 for details.

# CORRECT
See Smith (2024), "Document Standards," Journal of Tech, p. 45.

Spreadsheet Formula Patterns

Complements the xlsx skill's color conventions with additional patterns.

Extended Color Codes

Beyond the standard 5 colors (blue inputs, black formulas, green cross-sheet, red external, yellow assumptions):

ColorMeaningUse Case
Gray textStatic constantsValues that never change (tax rates, conversion factors)
Orange backgroundReview/cautionCells needing verification or approval
Light red backgroundErrors/issuesKnown problems to fix

Formula Simplicity

Use helper cells instead of complex nested formulas.

# WRONG - hard to debug, audit, or modify
=IF(AND(B5>100,C5<50),B5*1.1*IF(D5="A",1.2,1),B5*0.9)

# CORRECT - use helper columns
E5: =B5>100           (Threshold check)
F5: =C5<50            (Secondary check)
G5: =IF(D5="A",1.2,1) (Category multiplier)
H5: =IF(AND(E5,F5),B5*1.1*G5,B5*0.9)  (Final calculation)

Benefits:

  • Each step is auditable
  • Errors are easier to trace
  • Business logic is visible
  • Modifications are safer

Avoid Dynamic Array Functions

For maximum compatibility, avoid:

  • FILTER() - not supported in older Excel
  • XLOOKUP() - Excel 365+ only
  • SORT() - dynamic array function
  • SEQUENCE() - dynamic array function
  • UNIQUE() - dynamic array function

Use classic equivalents:

  • FILTER()INDEX/MATCH with helper columns
  • XLOOKUP()INDEX/MATCH
  • SORT() → manual sorting or helper columns
  • SEQUENCE() → manually entered row numbers

Finance-Specific Formatting

Additional to xlsx skill standards:

# Hide gridlines for cleaner appearance
sheet.sheet_view.showGridLines = False

# Add borders above totals (not around every cell)
from openpyxl.styles import Border, Side
thin_top = Border(top=Side(style='thin'))
total_cell.border = thin_top

# Cite sources in cell comments, not adjacent cells
from openpyxl.comments import Comment
cell.comment = Comment("Source: 10-K FY2024, p.45", "Analyst")

Quality Checklist

Before delivering any document:

  • PNG verification completed at 100% zoom
  • No clipped or overlapping text
  • Tables render correctly
  • Figures/images display properly
  • No U+2011 or problematic Unicode
  • Citations are human-readable
  • Formulas use helper cells where complex
  • No Excel formula errors (#REF!, #DIV/0!, etc.)
  • Professional, client-ready appearance

Integration with Official Skills

This skill adds patterns on top of the document-skills plugin:

Official SkillThis Skill Adds
xlsxHelper cells, extended colors, dynamic array warnings
pdfVisual-first philosophy, render-inspect-fix loop
docxTypography hygiene, PNG verification emphasis
pptxSame verification workflow

Always read both this skill AND the relevant official skill when working with documents.

Source

git clone https://github.com/belumume/claude-skills/blob/main/web-desktop-exports/document-quality-standards/SKILL.mdView on GitHub

Overview

Document Quality Standards provide visual verification, typography hygiene, and formula patterns to ensure DOCX, PDF, XLSX, and PPTX outputs look professional. The framework complements the official document-skills plugin and emphasizes a Render-Inspect-Fix loop to catch issues that plain text extraction may miss.

How This Skill Works

For every document operation, generate or modify the document, convert to PNG for verification, inspect at 100% zoom, fix issues, and repeat until clean. Never deliver without PNG verification, which catches clipped text, broken tables, missing figures, and formatting issues. Use the conversion commands DOCX to PDF to PNG with soffice and pdftoppm, PDF to PNG directly, and PPTX to PDF to PNG as shown.

When to Use It

  • When creating or editing professional DOCX, PDF, XLSX, or PPTX documents for client deliverables or publication.
  • When you must surface visual issues that text extraction misses, such as clipped text, broken tables, or missing figures.
  • When converting between formats (DOCX→PDF→PNG or PPTX→PDF→PNG) to validate layout integrity across viewers.
  • When typography hygiene matters, including hyphen safety and proper citation formatting.
  • When spreadsheet work requires clear, auditable formulas and readable presentation with extended color codes.

Quick Start

  1. Step 1: Generate or modify the document (DOCX, XLSX, PDF, or PPTX) to meet the task requirements.
  2. Step 2: Convert to PNG for verification (DOCX/PDF→PNG, PPTX→PDF→PNG, etc.) and open at 100% zoom.
  3. Step 3: Fix any issues found and repeat the verification loop until the document is clean and publication-ready.

Best Practices

  • Always generate/modify the document, then convert to PNG and inspect at 100% zoom before delivery.
  • Never deliver a document without PNG verification to catch layout and readability issues.
  • Use ASCII hyphens for hyphen safety and replace non-breaking hyphens (U+2011) and other non-ASCII dashes.
  • Ensure citations follow standard scholarly format (author, title, source, date, URL) and avoid internal tokens.
  • In spreadsheets, apply helper cells and color codes (gray text, orange for review, light red for errors) and avoid complex nested formulas or dynamic array functions; prefer classic equivalents.

Example Use Cases

  • A marketing deck in PPTX with precise typography and embedded figures that must render correctly after export.
  • A quarterly financial report in PDF with complex tables verified using PNG renders to ensure no cut-off lines.
  • A product specification in DOCX with properly formatted citations and consistent hyphenation.
  • An XLSX budget model using helper columns for auditability and color cues for review steps.
  • An academic slide deck that requires human-readable citations and error-free layout across viewers.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers