Skip to content

hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-report

hyper-report

Verified

Use this skill when the user asks for a report as a finished document rather than a chat answer: a briefing, business or research report, proposal, status or analysis write-up, or one-page summary. It fixes audience and decision up front, keeps every number and claim traceable to a source, and renders one authored Markdown source into HTML, print PDF, per-page PNG/JPG images, DOCX, or Markdown, with tables and figures where they carry the reader. Do not use it for slide decks, spreadsheet workbooks, single generated images, or reports that only need to live in chat.

rules/checks.md

View on GitHub
# Pre-delivery checks

Run these in order after the last render. The first section blocks delivery; the second is a judgement call the author makes and records.

## 1. Blocking checks

Every one of these must pass before the report is called done. Each has an observable test, not a feeling.

| Check | Test | Failure means |
|---|---|---|
| Source exists and parses | The render report is valid JSON with `status` set | The source or the pipeline broke before layout |
| Pages rendered | `layout.pages >= 1` | Nothing reached the page; usually an empty body or a broken template |
| No overflow | `layout.overflow` is empty | Content was clipped off the bottom of a page |
| No over-wide block | `layout.wide` is empty | A table or image is wider than the text column |
| Images loaded | every entry in `layout.images` has `ok: true` | An image path is wrong or the file is missing |
| PDF page count matches | `pdfPages == pages` | The print engine reflowed the paginated DOM |
| Requested formats exist | every non-null entry in `outputs` is a file on disk | A render step failed silently |
| Citations resolve | every `[Sn]` marker has a source-list row, and vice versa | A claim has no traceable source |
| Conclusion present | the first page contains the recommendation | The report opens with background |

The render report carries all of the layout checks as `errors[]` entries, so reading it is the check.

## 2. Judgement checks

These have no mechanical test. The author answers each one in the delivery note.

- **Does the first page answer the brief's decision?** Read only page 1; if the answer is not there, the structure is wrong.
- **Does every section open with its claim?** Scan the first sentence of each section; a section starting with setup is a section to rewrite.
- **Is every table comparing something?** A table whose rows share no column of meaning is prose in a box.
- **Does every figure have a caption that interprets?** A caption naming the axis is a label, not a caption.
- **Is the page count what the brief allowed?** Over budget means cut content, not shrink type.
- **Does the summary compress rather than truncate?** A summary that is the conclusion copied verbatim adds nothing.

## 3. The read-back

Open the delivered artifact and read it as the audience would. For a PDF, open the PDF. For images, look at each page. For HTML, open it in a browser at the printed width.

Reading the source instead of the artifact does not count: the artifact is what the reader gets, and layout breaks are invisible in the source.

Confirm during read-back:

- The footer page count reads `n / total` and the last page says `total / total`.
- The table of contents page numbers match where the sections actually are.
- No heading sits alone at the bottom of a page with its body on the next.
- Korean text has no broken glyphs, and Latin identifiers inside Korean sentences are not hyphenated.
- Table column alignment survived: numbers right, text left.

## 4. The delivery note

Report these, briefly:

- Absolute paths of every file produced.
- Page count and the format list.
- Which checks passed, and any advisory finding kept.
- Anything the brief assumed that the user should confirm.
- Any format that could not be produced, and why.

A delivery note that says "done" without paths is not a delivery.

## Sources

> Checked 2026-11-13.

| Claim | Source |
|---|---|
| Reading the rendered surface rather than the source as completion evidence | `instructions/validation/index.md` |
| Risk-matched verification depth and the inspected-result requirement | `instructions/validation/index.md` |
| The layout checks themselves (`overflow`, `wide`, `images`, page-count agreement) | This package's `assets/runtime/report.js`, verified on 2026-11-13 |
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 197kUpdated Claude CodeCodexVerifiedInstall