Site Inspection Report Assistant

Problem

Field inspection records are often scattered across photos, notes, and informal messages, making it hard to produce a consistent report with clear issues, evidence, and remediation steps. This skill targets internal inspection workflows and turns materials from safety checks, equipment patrols, or quality reviews into a reviewable HTML report.

How It Works

The skill follows a staged flow. It first confirms the inspection type, then collects images and text descriptions with short acknowledgments instead of premature conclusions. When the user signals inspection ended or generate report, it proposes an outline for section structure, key points, and length before generating the final file.

Key steps include:
- saving images to ./inspection_images/ and converting them to base64 via scripts/process_images.py;
- reading assets/report-template.html and replacing variables such as report_title, problems_section, and rectification_section;
- organizing content as major issue category -> subcategory -> related photos, with the same photo reusable across categories;
- outputting Inspection_Report_YYYYMMDD.html for easy opening and archiving.

Boundaries

The skill is suitable for standardized inspection documentation, not for formal legal interpretation, professional certification, or emergency safety decisions. Inputs should include key fields such as scope, location, and personnel, and the environment should support Python 3.9+. If dependencies or fields are missing, it should prompt for clarification or report the failure clearly.