
Minimax Pdf
Produce print-ready, designed PDFs—new reports, filled forms, or restyled existing docs—when visual quality matters more than a quick export.
Overview
minimax-pdf is an agent skill most often used in Build (also Validate, Grow) that generates, fills, or reformats print-ready PDFs using a token-based design system and scripted render pipeline.
Install
npx skills add https://github.com/modelscope.cn --skill minimax-pdfWhat is this skill?
- Three routed tasks: CREATE (generate), FILL (form fields), REFORMAT (apply design to existing content)
- Token-based design system: color, typography, and spacing flow from document type across pages
- CREATE pipeline: palette.py → cover.py → render_cover.js → render_body.py → merge.py
- FILL flow: fill_inspect.py then fill_write.py for existing PDF forms
- Requires reading design/design.md before CREATE or REFORMAT for consistent client-ready output
- 3 routed tasks: CREATE, FILL, REFORMAT
- 5-step CREATE script chain before merge
Adoption & trust: 721 installs on skills.sh; trending (+100% hot-view momentum).
What problem does it solve?
You can export a PDF quickly but proposals, resumes, and client docs look generic or inconsistent across cover, body, and form fills.
Who is it for?
Indie founders and freelancers shipping proposals, reports, resumes, or filled government and contract PDFs where layout and cover design matter.
Skip if: Cases where a one-click plain export is enough or you need interactive PDF features beyond form field fill.
When should I use this skill?
User wants make/generate/create a PDF, fill form fields, reformat or re-style a document, or asks for beautiful, professional, client-ready, or print-ready PDF output.
What do I get? / Deliverables
You get routed CREATE, FILL, or REFORMAT runs that yield polished, print-ready PDFs with design tokens applied end-to-end.
- Print-ready merged PDF
- Completed form-field PDF after FILL
- Reformatted document matching the skill design system
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build docs because the skill’s core output is professional documents, proposals, and resumes via a scripted CREATE/FILL/REFORMAT pipeline. Docs subphase matches structured deliverables (reports, proposals, resumes) rather than app UI or backend APIs.
Where it fits
Turn a validated offer one-pager into a designed PDF for email signups or investor sends.
Generate a technical report with cover, body styles, and merged pages from the CREATE script chain.
Reformat an existing Markdown case study into a styled PDF for downloads or sales follow-up.
Fill an RFP or intake PDF form after inspect identifies field names and types.
How it compares
Choose this designed document generator over generic 'print to PDF' or unstyled Markdown converters when client-ready appearance is the goal.
Common Questions / FAQ
Who is minimax-pdf for?
Solo builders, freelancers, and small teams who need branded-looking PDF deliverables and optional form completion without manual InDesign work.
When should I use minimax-pdf?
During Validate for proposals and pricing PDFs; in Build for specs and resumes; at Grow for polished outreach or lifecycle documents; whenever user intent matches create, fill, or reformat language from the skill.
Is minimax-pdf safe to install?
Scripts touch local files and may run shell tooling; review source scripts, form data handling, and the Security Audits panel on this Prism page before processing sensitive PDFs.
SKILL.md
READMESKILL.md - Minimax Pdf
# minimax-pdf Three tasks. One skill. ## Read `design/design.md` before any CREATE or REFORMAT work. --- ## Route table | User intent | Route | Scripts used | |---|---|---| | Generate a new PDF from scratch | **CREATE** | `palette.py` → `cover.py` → `render_cover.js` → `render_body.py` → `merge.py` | | Fill / complete form fields in an existing PDF | **FILL** | `fill_inspect.py` → `fill_write.py` | | Reformat / re-style an existing document | **REFORMAT** | `reformat_parse.py` → then full CREATE pipeline | **Rule:** when in doubt between CREATE and REFORMAT, ask whether the user has an existing document to start from. If yes → REFORMAT. If no → CREATE. --- ## Route A: CREATE Full pipeline — content → design tokens → cover → body → merged PDF. ```bash bash scripts/make.sh run \ --title "Q3 Strategy Review" --type proposal \ --author "Strategy Team" --date "October 2025" \ --accent "#2D5F8A" \ --content content.json --out report.pdf ``` **Doc types:** `report` · `proposal` · `resume` · `portfolio` · `academic` · `general` · `minimal` · `stripe` · `diagonal` · `frame` · `editorial` · `magazine` · `darkroom` · `terminal` · `poster` | Type | Cover pattern | Visual identity | |---|---|---| | `report` | `fullbleed` | Dark bg, dot grid, Playfair Display | | `proposal` | `split` | Left panel + right geometric, Syne | | `resume` | `typographic` | Oversized first-word, DM Serif Display | | `portfolio` | `atmospheric` | Near-black, radial glow, Fraunces | | `academic` | `typographic` | Light bg, classical serif, EB Garamond | | `general` | `fullbleed` | Dark slate, Outfit | | `minimal` | `minimal` | White + single 8px accent bar, Cormorant Garamond | | `stripe` | `stripe` | 3 bold horizontal color bands, Barlow Condensed | | `diagonal` | `diagonal` | SVG angled cut, dark/light halves, Montserrat | | `frame` | `frame` | Inset border, corner ornaments, Cormorant | | `editorial` | `editorial` | Ghost letter, all-caps title, Bebas Neue | | `magazine` | `magazine` | Warm cream bg, centered stack, hero image, Playfair Display | | `darkroom` | `darkroom` | Navy bg, centered stack, grayscale image, Playfair Display | | `terminal` | `terminal` | Near-black, grid lines, monospace, neon green | | `poster` | `poster` | White bg, thick sidebar, oversized title, Barlow Condensed | Cover extras (inject into tokens via `--abstract`, `--cover-image`): - `--abstract "text"` — abstract text block on the cover (magazine/darkroom) - `--cover-image "url"` — hero image URL/path (magazine, darkroom, poster) **Color overrides — always choose these based on document content:** - `--accent "#HEX"` — override the accent color; `accent_lt` is auto-derived by lightening toward white - `--cover-bg "#HEX"` — override the cover background color **Accent color selection guidance:** You have creative authority over the accent color. Pick it from the document's semantic context — title, industry, purpose, audience — not from generic "safe" choices. The accent appears on sectio