OmegaOS PDF generator
Use omega pdf. Do not substitute ReportLab, LaTeX, browser print scripts, or another PDF library.
Workflow
Choose the template:
whitepaperfor long-form reports with sections and a table of contents.auditfor a score, domains, findings, evidence, and an action plan.marketingfor personas, KPIs, channels, and recommendations.docfor an editorial Markdown document.
Read
~/.omega/skills/pdfgen/lib/schemas.tswhen constructing custom JSON. Use only fields accepted by the selected template.Keep the source JSON in the project deliverable directory. Exclude credentials, tokens, private keys, and hidden reasoning.
Validate the source with
jq empty <data.json>.Render with:
omega pdf --template=<whitepaper|audit|marketing|doc> \ --data=<data.json> \ --out=<report.pdf> \ --send \ --caption="<short Telegram caption>"Omit
--sendonly when the user explicitly declines Telegram delivery.Treat a render error or Telegram error as a failure. Do not claim delivery from a local file alone.
Verify the result with
file,pdfinfo, andpdftotext. Inspect representative pages as images when the report is visual or long.Report the output path, byte size, page count, and Telegram delivery result.
Quality gates
- Use a reader-facing title, date, author, document ID, and OmegaOS brand.
- Cite load-bearing audit or research claims in the PDF.
- Keep every requested section in the source data and confirm it survives text extraction.
- Avoid em and en dash punctuation in user-facing copy.
- Never include secrets or direct personal identifiers in the PDF or Telegram caption.