doc-redaction-modifications

Reapply OCR/CSV redaction edits via /review_apply with coverage verification.

55|11|Updated Apr 25, 2024
One-click install
npx skills add https://github.com/seanpedrick-case/doc_redaction --skill doc-redaction-modifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-redaction-modifications
Source: https://github.com/seanpedrick-case/doc_redaction/tree/main/skills/doc-redaction-modifications
Command: npx skills add https://github.com/seanpedrick-case/doc_redaction --skill doc-redaction-modifications

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a repeatable workflow for correcting and reapplying document redactions when initial OCR or box proposals were incomplete or inaccurate, while minimizing the risk of text-layer leaks.

Core Features & Use Cases

  • Two-pass review workflow (text first, optional visual QA): run Pass 1 OCR/CSV/text checks first, then only run Pass 2 VLM on targeted flagged pages when needed.
  • CSV-driven edits with safety guardrails: edit the existing *_review_file.csv to add/remove/modify normalized bounding boxes and ensure coordinates are valid (0–1) before apply.
  • Coverage-first verification before committing changes: enforce use of verify_redaction_coverage so you can iterate until policy satisfaction (pass_strict) and confirm no text-layer leaks on *_redacted.pdf.
  • One consistent apply path: apply redactions only via /review_apply using the original PDF plus the matching review CSV, avoiding unsafe custom PDF rewriting.

Quick Start

Use the doc-redaction-modifications Skill to merge your OCR-derived review edits into *_review_file.csv, run the coverage report until pass_strict is true, then call /review_apply once to generate the corrected *_redacted.pdf for verification.

Frequently Asked Questions about doc-redaction-modifications

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix inaccurate OCR redactions on a PDF without causing text-layer leaks?

To fix incomplete document redactions without text-layer leaks, edit your master review CSV with corrected normalized 0–1 bounding boxes and apply them exclusively through a dedicated review endpoint using the original PDF.

What is a two-pass document redaction workflow and when do I need visual VLM checks?

A two-pass redaction workflow runs OCR and CSV text checks first, then uses visual VLM checks only on targeted flagged pages to verify coverage when initial bounding box proposals are incomplete or inaccurate.

How do I verify redaction coverage before applying changes to a PDF?

Verify redaction coverage by running a coverage verification tool against your edited CSV until it achieves strict policy satisfaction, ensuring no text-layer leaks remain on the final redacted PDF.

Can I manually edit normalized bounding box coordinates in a CSV for PII removal?

Yes, you can manually add, remove, or modify normalized 0–1 bounding box coordinates in your review CSV to correct initial OCR proposals before final redaction application.

Why should I avoid custom PDF rewriting scripts when reapplying redactions?

Custom PDF rewriting scripts risk introducing text-layer leaks, whereas applying redactions through a standardized review_apply path using the original PDF and edited review CSV ensures safe, consistent coverage.