Creates print-ready documents such as reports, letters, resumes, and guides. It distinguishes flowing text across standard pages from fixed-size single-page designs, with guidance for readable typography, page breaks, tables, and captions.
Page-style document, printable out of the box
Run score Not tested
See how to installmake-a-doc creates documents intended for printing, including reports, resumes, memos, letters, and guides. It distinguishes between text that flows across Letter or A4 sheets and designs that fit one page of specified dimensions, such as posters or certificates. It also arranges text size, line spacing, heading levels, table borders, and short captions for figures and code.
Use it when you want long text to be readable in print or need material to fit on a single sheet. It handles print layout details that are difficult to judge from the screen alone, including multiple text columns, tables spanning pages, and page breaks for chapters or appendices.
Flowing documents require an environment where copy_starter_component can retrieve doc_page.js. The content uses HTML and CSS. Fixed-size single-page designs use a separate approach, with pixel dimensions on the top-level element. Choose the final document shape first, because export methods differ.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 24, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Create a document (resume, one-pager, memo, letter, report, guide, paper). First decide which of two shapes the user wants — they export completely differently:
Flowing pages — text that pours onto standard sheets (Letter/A4)
and breaks wherever needed: reports, memos, letters, papers, guides.
START by calling copy_starter_component with
kind: "doc_page.js", then write the whole document as normal
flowing HTML inside <doc-page size="letter" margin="0.75in">.
The component owns the sheet, the desk background, and all print
geometry — do NOT write your own @page rule, body background,
page-card divs, break-after: page fake sheets, or
break-inside: avoid on items inside multi-column grids (a grid only
breaks between rows, so a kept row that doesn't fit leaves a blank band).
Print rules for flowing pages: multi-column text uses CSS columns
(column-count + column-gap; column-span: all on a heading
that spans; hyphens: auto in narrow columns — it needs lang
on the html element), never side-by-side
flex/grid columns — only real CSS columns flow and break across pages.
Use break-before: page on anything that must start a new page (a
chapter, an appendix); add custom kept-together blocks (callouts, stat
tiles, cards) to a break-inside: avoid rule and keep each shorter
than a page — the component already keeps headings with their content,
keeps figures/code/table rows whole, and suppresses orphans and widows
(extend orphans: 3; widows: 3 to custom text blocks). Long tables
get a <thead> so the header repeats on every page. No
position: fixed/sticky and no viewport units in content —
fixed elements stamp every printed page (running headers/footers go in
the component's slots) and 100vh mis-sizes at print.
Fixed sheet — a design that must fill exactly one page of fixed
dimensions: poster, infographic, social graphic, certificate. No
starter component — build it at its true pixel size with an explicit
px width (and height if fixed) on the top-level element; the
export sizes the PDF page to it automatically. Do not write any
@page rule for it.
Styling (both shapes): body type 14–16px with generous line-height (1.55–1.7); clear heading hierarchy; restrained palette. Tables get a header row and hairline borders; figures and code blocks each carry a short caption. Open with the document's own h1 as the first body element (use any header-shaped first line of pasted content as that h1 rather than rendering it as a separate masthead).
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a 3D object with three.js, inspect it from every angle in an interactive viewer, and download it as OBJ + MTL or GLB for use in other 3D applications.
Maintain a private task list with deadlines, next steps, waiting parties, and blockers. Update progress and dependencies, merge duplicate items, and archive closed tasks so ongoing commitments stay clear and easy to follow.
Coordinate a task from a verifiable goal through completion. Handle work directly or split independent tasks across separate agent sessions, track progress, verify results, and arrange pull request merging when included in the goal.
Create animated HTML pages with smooth scene transitions and playback controls. An editable timeline lets users adjust scene lengths and speeds, with fixed landscape or portrait layouts prepared for video export.
Review synced Apple Health records, including steps, heart rate, sleep, and workouts. Retrieve daily summaries or detailed samples for a chosen period, and check sync status and missing data before interpreting the results.
Create and edit Word documents and templates, reorganize text, replace images, and work with tracked changes or comments. Apply proper headings and lists, then render every page to check its appearance before delivery.