Agent skill · data analytics · borghei
pdf-toolkit
Audit PDF files for metadata leakage, page count, encryption, JavaScript, embedded files, and version. Use before sending a PDF externally, when redacting sensitive metadata, or running a PDF security review.
Why this skill is useful
Provides a specialized tool for auditing PDF files that includes niche commands and workflows not commonly known.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
PDF Toolkit Audit .pdf files for metadata, page count, encryption status, embedded JavaScript, embedded files, and PDF version — using the standard library only. --- Table of Contents Keywords Quick Start Core Workflows Tools Reference Guides Templates Best Practices --- Keywords pdf, pdf audit, pdf metadata, pdf review, pdf leakage, pdf security, redaction, document handoff --- Clarify First Before running the audit, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Audit purpose (pre-handoff metadata scrub, inbound security triage, or bulk outbound check) — selects which of the 3 workflows and which fields you act on [ ] Recipient / handling context (external party, managed laptop) — sets what counts as a leak or a threat worth quarantining [ ] Expected legitimate metadata (who the author/title should be) — without it you can't distinguish a leak from expected data Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Quick Start Outputs: PDF version, page count, file size, metadata (Author, Title, Producer, Creator, dates), encryption status, embedded JavaScript indicators, embedded file indicators. --- Core Workflows Workflow 1: Pre-Handoff PDF Metadata Audit Goal: Stop leaking author identity, prior client names, or document history when handing a PDF to an external party. Steps: 1. Run: python scripts/pdfauditor.py document.pdf 2. Review metadata fields: Author matches the sender (not "Bob's intern" from a prior project) Title matches the document, not a leftover working title Producer doesn't reveal an internal-only PDF tool CreationDate and ModDate are reasonable for the deal 3. If metadata leaks, re-export from source with cleaned properties (or use a redaction tool) Time Estimate: 2-3 minutes per document. Workflow 2: PDF Security Triage Goal: Decide whether a received PDF can be opened safely on a managed laptop. Steps: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/pdf-toolkit