# Roofline Walk > A phone-first field checklist for walking around your own home from the ground - after a hail or wind storm, before wildfire season, or on a spring or autumn roof and drainage check - that ends in a report laid out to send to a roofer, an insurer or a contractor. URL: https://roofline-walk.skillsafe.ai/ API tutorial: https://roofline-walk.skillsafe.ai/api.html ## What it does - Three complete checklists, each item with what to look for, what a pass and a fail look like, why it matters, who fixes it and a question to ask them: - After a hail or wind storm (37 items, 8 sections: safety, roof from the ground, soft metals as hail evidence, gutters, siding/windows/doors, yard, attic and ceilings, documentation for the claim). - Before wildfire season (39 items, 9 sections: Zone 0 / 1 / 2 defensible space, roof and gutters, vents and eaves, walls/windows/doors, decks and fences, propane and utilities, access for firefighters). - Spring or autumn roof and drainage check (30 items, 7 sections). - Per item: pass, fail or n/a with big touch targets, a note, and up to eight photos taken with the phone camera or dropped on desktop. Photos are downscaled in the browser (longest side 1280 px, JPEG). - Section progress, a defects-only filter, and a live report: cover block (what, where, when, who), a pass/fail summary bar per section, findings grouped by severity with the photo beside each. - Exports: printable HTML report with photos inline, CSV of items, JSON of the walk, Markdown. - Free in the browser: everything above. Walks save to the person's SkillSafe account (a declared collection) when signed in; photos go to the account's private file store. ## Paid lanes (model: gpt-terra) - `report` - the completed walk becomes a prioritised findings report: severity (urgent/high/medium/low) and urgency per failed item, what it most likely means, what to do, who does it, a question to ask them, 3-8 questions for the insurer/roofer/contractor and a one-paragraph verdict (act now / repair soon / monitor / sound). - `reinspect` - a follow-up walk over only the items that failed last time: resolved, improved, unchanged, worse or not re-checked per item, what is left and what to ask. The model receives item statuses, notes (middle-clipped) and photo COUNTS - never image bytes. Its reply is checked against the walk in the browser: every finding must map to a failed or noted item; failed items it skips are listed as "not addressed"; a safety failure rated below urgent and a re-check outcome that contradicts today's status are flagged. ## Input contract One JSON object: `task` (report | reinspect), `template` (storm | wildfire | seasonal), `template_name`, `cover_json`, `sections_json`, `items_json`, `prescan_json`, `previous_json` (reinspect), optional `retry_note`. Reply: JSON Lines - `meta`, then `finding` (report) or `recheck` (reinspect) lines, `question` lines, a `verdict` line, `{"k":"end"}`. ## Limits A homeowner's walkaround from the ground, not a professional inspection, an insurance adjustment or a fire-safety certification. The app never asks anyone to climb onto a roof. ## Sources Checklist guidance after the skill @erichowens/drone-inspection-specialist (roof inspection, hail damage analysis, wildfire precondition assessment), applied to a ground-level walk with the general approach of NFPA Firewise USA, IBHS and CAL FIRE defensible-space zones.