About this skill

Problem

Screenshots, construction details, and site photos in technical bids often sit inside multiple Word docs as opaque files like image001.png. Reusing them means opening each file, reading surrounding context, and renaming images manually.

How It Works

The skill treats Word documents as an image source:
- Batch extraction: pulls embedded images from bid documents, technical specs, drawing notes, and related Word files
- Context-aware naming: prefers captions, then uses titles, keywords, or semantic context to create readable Chinese file names
- Mode choices: mechanical naming is fast; semantic naming is more precise; LLM-assisted mode can produce clearer topic phrases
- Format handling: converts images to PNG when Pillow is available, otherwise keeps the original format

Boundaries

It addresses “recover, name, and organize” rather than drafting the technical proposal itself. .docx is parsed natively; .doc requires LibreOffice. Naming quality depends on how clearly captions, headings, and context are written, so ambiguous documents still need manual review after renaming.

Screenshots

Use Cases

When organizing technical bid Word docs, extract embedded images and name them by captions, headings, and context.
When bid specs and drawing notes are split across Word files, collect images and convert them to PNG for reuse.
When processing legacy .doc bid files, convert then extract images to avoid meaningless names like image001.png.
When reviewing bid materials, verify that extracted images trace back to the correct source docs and section context.

Best For

Technical bid writers who need to gather images from multiple Word bid files into a searchable asset library.
Engineering document archivists who need to extract, rename, and standardize images scattered across docx and doc files.
Bid reviewers who need to check image names, source sections, and formats before reuse.
Bid project leads who need to build a reusable project image library and cut repeated manual image hunting.