When should you use it?
- You copy the same client, vendor or employee details into PDF forms several times a week
- A supplier, bank or agency only accepts its own PDF and the file has no clickable fields
- You want a visual proof of each filled page before anything is signed or uploaded
Not for: Forms that must be signed with a certified digital signature; the skill places text, it does not sign; Government or tax filings you have not reviewed line by line yourself; Web forms in a browser, which need a browsing agent rather than a PDF tool
What do you need, and what do you get?
You need
- Claude with skills enabled (claude.ai, Claude Code or Claude Cowork) and the pdf skill installed
- The blank PDF form
- The answers, as a short list, a spreadsheet row or an earlier completed form
You get
- A filled copy of the PDF, with the original left untouched
- A field map that pairs each answer with the box it went into
- Page images of the filled form for a quick visual check
- A list of any boxes it could not place or answers it did not have
How does it work, step by step?
- Install the skillAdd the pdf skill from Anthropic's public skills repository, or confirm it is already enabled in your Claude workspace.
- Hand over form and answersUpload the blank form and the details to enter, and say which answers are optional so it does not invent them.
- Let it pick the routeThe skill first tests for real form fields. With fields it fills by field ID; without them it reads label positions, or the page image for scans, to place text.
- Read the field mapBefore it writes the file, review the list of fields and values. Fix any wrong pairing here, where it takes seconds.
- Check the page imagesLook at the rendered pages for overlaps, cut-off text and unticked boxes, then sign or send only after your own read-through.
The prompt
Our adapted version, written to work in Claude, Claude Code and Claude Cowork. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Use the pdf skill to fill {form_name} (attached). Answers: {answers}. First tell me whether the form has fillable fields. Then show me a table of every field with the value you plan to put in it, and leave blank any field I did not give you an answer for. Never guess dates, ID numbers or amounts; list them as gaps instead. After I confirm the table, write a new filled copy, render each page as an image, and point out anything that overlaps, is cut off or did not land on its line.
The original skill is published by Anthropic on Anthropic. Open it there to install or import it; the prompt above is our own adaptation.
What can go wrong?
- Scanned forms rely on visual estimation, so text can sit slightly off the line. Always open the page images before you send the file.
- Checkboxes and radio buttons need the exact value the form expects. If a box shows empty, ask Claude to list the allowed values for that field.
- The skill fills what you give it. Missing answers should come back as a gap list, so tell it never to guess a date, ID number or amount.
- Personal data such as tax IDs and bank details goes into Claude's working files. Use a workspace your firm has approved for that information.
Our take
PDF forms are one of the most stubborn bits of office busywork, because the file looks like a document but behaves like a database only some of the time. What makes Anthropic's pdf skill worth installing is that it does not pretend every form is the same. It checks first whether real fields exist, and only falls back to placing text by position when they do not, which is where most quick scripts and chat attempts go wrong. The validation step that refuses unknown field IDs and the bounding-box check that catches overlapping text are small details that prevent the most common bad output: a form that looks filled but is not. We would add two habits of our own. Ask for the field map before the file, since a wrong pairing is far easier to spot in a list than on the page. And keep a short gap list in every request, so a missing birth date comes back as a question rather than a guess. In our dry run with a fictional vendor setup form, the skill route filled nine fields, flagged a missing tax ID and placed a checkbox correctly on a flat copy of the same form.
Where the time goes back: Recurring paperwork such as vendor setup, onboarding packets and client intake forms goes from retyping every box to reviewing a field map and a page preview.
FAQ
What if the PDF has no fillable fields?
Is the skill free to use and adapt?
Does it only fill forms?
Source and credit
This playbook is based on work by Anthropic. We summarize it and link to it and write our own adapted prompt.
- Original
- pdf skill (anthropics/skills)
- Creator
- Anthropic
- Published on
- Anthropic
- License
- Apache-2.0
- Originally for
- Claude
- AI dry run
- Nov 9, 2026: passed. Dry-run tested by our AI test agent on sample input. Both routes worked on synthetic forms: 9 fields filled, missing tax ID reported as a gap, checkbox placed correctly on the flat copy, page image checked.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 9, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
The original is licensed under Apache-2.0 by Anthropic. Modified: our adapted prompt and summary are our own wording; the original skill {"was unchanged at the source when we snapshotted it (live source later removed)" if src_removed(s) else "is unchanged at the source link"}.
Are you the creator? Claim or correct this page.