// Security & Compliance

Document Release Leak Verifier

Verify a final PDF or DOCX for named sensitive terms, hidden text, metadata, comments, revisions, attachments, forms, and embedded content before owner release.

Get it on Agensi Find another skill $19 one-time

What problem does Document Release Leak Verifier solve?

A document can look redacted while searchable text, metadata, comments, tracked changes, embedded files, or prior revisions still expose sensitive information.

Use it to

Verify a legal or public-records PDF after redaction
Check a client deliverable for comments, tracked changes, and hidden text
Hash and independently review the exact release candidate
Block a release when parsing or covered-surface verification is incomplete

What it returns

Surface-specific findings CSV
JSON release gate with SHA-256 file identity
Review memo listing tested and unverified surfaces
Owner-release checklist for residual manual review

A representative input and result

fixture-backed sample

input Manifest names 'Project Lark' and two email addresses as sensitive. Final PDF looks redacted but contains the project name in extracted text and an embedded attachment.

result Gate: BLOCK. Critical: named sensitive term remains in extracted content. High: embedded attachment requires removal and independent re-verification. SHA-256 identifies the tested file.

Access and approval boundaries

Read access to a user-supplied manifest and final local PDF or DOCX.
Write access only to the selected local audit output directory.
No browser, network, credential, office application, or environment-variable access is required.

Known limitations

Version 1 does not OCR image-only pages, interpret arbitrary images, or support every proprietary document format.
Encrypted, malformed, unsupported, or incompletely parsed files block verification rather than being treated as clean.
VERIFIED_FOR_OWNER_RELEASE_REVIEW is not legal authorization and cannot prove that unnamed sensitive concepts are absent.

// choose with context

Is Document Release Leak Verifier the right skill?

Best fit

A document can look redacted while searchable text, metadata, comments, tracked changes, embedded files, or prior revisions still expose sensitive information.

It returns

Surface-specific findings CSV. JSON release gate with SHA-256 file identity.

Do not use it as

It does not redact, sanitize, alter, transmit, or authorize release of a document.

Compatibility, access, version, and licence

Reads or accesses: Declared local scope: release-input/**, release-audit/**, *.pdf, *.docx.
Compatibility: PDF files readable by pypdf 5 or 6. Standard unencrypted DOCX packages. Python 3 with the documented pypdf dependency for PDF verification.
Version: 1.0.0
Licence: Review the package licence and seller terms at the linked destination.

What happens next

The Agensi listing opens at the current offer. Complete purchase there, inspect SKILL.md and its bundled files, then add the complete folder to your agent.

Questions

Does it redact the document?

No. It independently verifies the final artifact and never changes it.

Which formats are supported?

Version 1 supports standard PDF and unencrypted DOCX files.

Does it inspect hidden information?

Yes. Covered surfaces include metadata, comments, revisions, forms, annotations, attachments, active content, embedded objects, and extracted or raw text.

Does it use OCR?

No. Image-only pages require a separate authorized OCR and visual review.

Why is a SHA-256 hash included?

It binds the report to the exact file reviewed so later changes are detectable.

Does a verified result authorize release?

No. A responsible owner and any required legal or privacy reviewer must still approve release.