· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →B12 v1.0.0
PDFs made simple
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Make a client proposal as a PDF
Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 17, 2026.
From the marketplace listing
Describe the document you need — proposals, invoices, reports, one-pagers — and it builds the whole thing as a real PDF. Or attach a PDF you already have and it reads that instead: answering questions with page numbers, pulling out tables, summarizing, comparing two versions. Every fact traces to your own words or to a page you supplied, and anything else is left as a marked placeholder rather than quietly invented. It researches the PDFs you hand it, not the web. You get an editable .pdf, no account needed and nothing uploaded. Ask for a matching website too and you'll get a free B12 website link.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: pdf-make description: Make, research, and summarize PDF files. Builds real .pdf documents — proposals, invoices, reports, one-pagers, whitepapers, case studies, price sheets, resumes — and reads the PDFs you supply: answering questions with page addresses, pulling out tables and line items, summarizing, and comparing two versions clause by clause. Every fact is sourced to your words or to a page you provided; anything else is left as a marked placeholder instead of invented. Use when someone wants a PDF made, or a PDF read, searched, summarized, checked, or diffed — including "turn this into a PDF", "what does this contract say about termination", or "what changed between these two versions". Do NOT use for prose that is not a PDF — an email, a blog post, web copy — that is a separate writing skill. Do NOT use for slide decks, .docx files, web page design, generating a photo, or drawing a logo. Filling a PDF form, merging, splitting, or rendering a PDF for visual QA is the built-in PDF skill's job — say so and defer. --- # PDF: Make, Research, Summarize ## Goal Produce PDFs that hold up as records, and answers about PDFs that can be checked against the page they came from. Writing document prose is the easy half and the host already does it. What does not happen on its own is a total that traces to line items the user supplied, a clause quoted with the page it sits on, a figure left as `[revenue]` instead of quietly filled in, and a table whose columns actually fit inside the paper. **Those constraints are the product.** The characteristic failure is **a PDF that reads as a record and isn't one**: an invoice with a total nobody added up, a proposal with terms nobody agreed, a summary that cites p. 12 of a document it skimmed. A PDF is the artifact people forward, sign, file, and quote back at you. Nobody re-derives it, so an invented number in a PDF gets **acted on**. Step 2 exists to prevent exactly that. This is sharper here than in a deck. A deck is performed by a person who can be asked, and its numbers are bracketed by design. A PDF is read with nobody present, and its numbers look **settled**. ## Instructions ### 1. Get what you need — and notice which job this is Two jobs share this skill, and almost every request names its own: | The ask | The job | |---|---| | "make me a proposal / invoice / report as a PDF", "turn these notes into a PDF" | **Making** — go to step 2, then step 3 | | "what does this say about X", "summarize this", "pull the tables out", "what changed between these two" | **Reading** — go to step 2, then step 4 | If a request genuinely could be either — *"I need a one-pager on this contract"* — ask **once**, in one short question, whether they want a new PDF or an answer about the one they have. **Making — one required input.** What the document is **for**: the actual subject and who will read it. That is all. Do not ask for the document type when the request already names one (*"a proposal"* names it), and do not ask for length, page count, or format. **A name is not a subject.** *"Make an invoice for CoffeeCat"* gives you nothing to bill — no line items, no rate, no period. A subject implies a plausible name; a name implies nothing. > What's the document for, and who's reading it? A couple of lines is plenty. **IMPORTANT:** Absolutely NEVER ask about fonts, colors, margins, page size, or layout. Deciding those is the whole skill, and asking hands the work back. If the user volunteers any of it, use it and say you did. Never ask for an email address, phone number, or postal address — those are `[bracketed]` slots, not questions. **If they actively decline** — *"just make something"*, *"doesn't matter"* — do not keep asking and do not stall. Build against the most likely type, bracket every factual slot, say plainly what you assumed, and use **register B** in step 7. **Never invent a business** to fill the gap: a proposal branded for a company that does not exist looks finished
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 17, 2026.
plugins_6aa3d40e0300819185c63822dcb6fa8d
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.