manual-image-review

Audits screenshots inside docx manuals via extraction, OCR, and triage-based visual review.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dadafinger/dadafinger-skills --skill manual-image-review-dadafinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manual-image-review
Source: https://github.com/dadafinger/dadafinger-skills/tree/main/manual-image-review
Command: npx skills add https://github.com/dadafinger/dadafinger-skills --skill manual-image-review-dadafinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Text-level washing of translated manuals misses sensitive data and errors embedded in screenshots: leftover Korean text, real employee emails, customer names, public IPs, UI copy mistakes, and low-resolution or misplaced images. This Skill automates detection of those issues across hundreds of images in a docx manual. ## Core Features & Use Cases - Automated extraction and mapping: Pulls every image from a docx, maps each to its section and surrounding paragraph context, and computes pixel size, effective DPI, duplicates, and reuse statistics. - OCR-based triage: Runs macOS Vision OCR (Korean/Japanese/English) over all images, then flags only suspicious ones (Korean residue, public IPs, emails, keywords, jpg format, low resolution) so reviewers inspect roughly 10-20% of images instead of all of them. - Capture type classification: Classifies each image into nine types (FULL, CONTENT, MODAL, PANEL, INLINE, DIAGRAM, COVER, CLI, TOAST) to support consistent recapture workflows. - Use Case: Before submitting an English product manual, run the pipeline on the docx, review the flagged images in the triage queue, and produce a severity-classified findings report covering washing omissions, Korean residue, UI copy errors, placement issues, and quality defects. ## Quick Start Run an image audit on the attached manual.docx and give me the triage queue of suspicious screenshots with a findings report.

Frequently Asked Questions about manual-image-review

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

FAQPage Schema
How do I audit screenshots in a docx manual for sensitive data?▼

Extract all images from the docx with the extraction script, run OCR over them, then analyze the OCR output to flag images containing emails, public IPs, keywords, or leftover Korean text. Only the flagged images need manual visual review, typically 10-20% of the total.

How to find leftover Korean text in an English manual's screenshots?▼

Run OCR with Korean and English language recognition over the extracted images, then filter for Korean tokens of two or more consecutive characters. Single-character matches are usually OCR noise from misread English UI text and can be ignored.

Does this image review workflow work without macOS Vision OCR?▼

Without swift and macOS Vision, the OCR step is skipped and the pipeline falls back to format-based flags such as jpg files, tiny crops, and low-resolution images, combined with full manual visual review of every image.

Can I review images in a PDF manual instead of docx?▼

Yes, for PDF manuals use pdfimages to extract the embedded images, then reuse the OCR and triage analysis steps. Only the docx-specific extraction and section-mapping step is replaced.

Why does OCR flag images that have no real problems?▼

OCR frequently misreads English UI text as single Korean characters, and jpg flags often turn out to be legitimate diagrams. The flags are only clues; reviewers confirm each flagged image visually and mark intentional cases like language-change screens as non-issues.

How do I review only changed images between manual versions?▼

Extract images from both the old and new docx versions, then compare MD5 hashes to identify added, changed, and deleted images. Review only the delta visually and summarize the rest with automated flags, saving significant review time.