From job-hunt-toolkit
Use when the user asks to "scrub PDF metadata", "clean the PDF", "strip CV metadata", "remove author from PDF", "sanitize PDF", "wipe PDF info", "clear PDF properties", "clean up before sending", "remove creation date", or after exporting a PDF that will be sent to a recruiter. Strips Author, Title, Producer, Creator, CreationDate, ModifyDate, XMP, and custom metadata fields using exiftool, then sets a clean Author field back. Called automatically by export-pdf as its final step.
How this skill is triggered — by the user, by Claude, or both
Slash command
/job-hunt-toolkit:scrub-pdf-metadata <pdf-file> [--author="Full Name"]<pdf-file> [--author="Full Name"]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Some PDF metadata can leak export tools, suspicious timestamps, source HTML filenames, and device names. Strip it with `exiftool`, then reset a clean Author.
Some PDF metadata can leak export tools, suspicious timestamps, source HTML filenames, and device names. Strip it with exiftool, then reset a clean Author.
export-pdf runs and before prepare-to-send declares the file ready.--author=): name to set as the clean Author. Infer from memory/context (user's name as it appears on the CV). If unclear, ask the user via AskUserQuestion before proceeding.command -v exiftool >/dev/null 2>&1
If missing:
ERROR: exiftool is not installed. Install it:
brew install exiftool
We don't fall back to other scrubbers — different tools handle different
metadata fields, and partial scrubbing is worse than no scrubbing because
it creates false confidence.
Show the user what's in the PDF right now:
exiftool "$pdf"
Specifically highlight any of these that are non-empty:
TitleAuthorProducerCreatorCreationDateModifyDateKeywordsSubjectCreator ToolXMP custom fieldsfile:// or absolute path fragmentsexiftool -all= -overwrite_original "$pdf"
-all= removes all metadata, including Author; re-set it next. -overwrite_original skips creating a .pdf_original backup alongside the PDF.
exiftool \
-Author="<Clean Author Name>" \
-Title="CV" \
-overwrite_original \
"$pdf"
Use Title = "CV"; do not include company, role, or date.
exiftool "$pdf" | grep -Ei 'author|title|producer|creator|date|keywords|subject'
Confirm:
Author = the clean name you setTitle = "CV"Producer / Creator — should be empty OR only show generic "exiftool" (acceptable; recruiters don't pattern-match on exiftool)Create Date / Modify Date — after stripping, these often become the time of the scrub. That's acceptable (time-of-send timestamp is normal). If you want to eliminate them entirely:exiftool -CreateDate= -ModifyDate= -MetadataDate= -overwrite_original "$pdf"
Metadata scrub does not cover PDF content. Use Read, then scan extracted text for:
file:/Users//home/C:\Documents$(basename "${JOB_HUNT_WORKSPACE:-$HOME/Documents/job_seeking}")).htmlIf any hits: the HTML template probably renders a path in a header/footer via @page CSS. Fix the HTML, re-export, re-scrub. Do NOT send the PDF.
✓ Scrubbed: <pdf-filename>
Author: <clean name>
Title: CV
CreateDate: <new timestamp or removed>
Producer / Creator: empty
Content scan: no path leaks detected
Ready for sending. Run $job-hunt-toolkit:prepare-to-send for the full pre-send checklist.
-all= first, then set Author/Title. If you only set Author, the other fields (Producer, CreationDate) stick around.Recruiters and hiring managers sometimes open File → Properties on a PDF. ATS tools routinely parse PDF metadata. If your Title says "__CV_Tailored_for_OpenAI_v3" and you apply to Anthropic, that's a rejection waiting to happen.
exiftool -all= strips Author too. Step 3 (Set clean Author + Title) is mandatory; see references/exiftool-commands.md for commands.@page paths render into PDF text and survive metadata stripping. exiftool cannot remove visible header/footer text, so always run Step 5 after a clean report.references/exiftool-commands.md — full command reference with common patternsnpx claudepluginhub alex-kopylov/zweihander --plugin job-hunt-toolkitGuides reception of code review feedback: verify before implementing, avoid performative agreement, push back with technical reasoning when needed.
Design banners for social media, ads, website heroes, and print with multiple art direction options and AI-generated visuals.