kc-streetcar-reportlisted

# KC Streetcar Issue Report Draft a concise, actionable issue report email to the KC Streetcar operations team. **Setup**: Before first use, replace `[Your Name]`, `[Your Phone]`, and `[Your Email]` placeholders below (in Step 3 and the Email Template) with your own contact info. Keep that contact info out of the public repo if you are sharing this skill. ## Workflow ### Step 1: Identify the station **If the user uploaded a photo**, try two approaches in order: 1. **Visual identification** -- read the station name from the photo itself (the blue vertical platform signs are labeled, e.g., "River Market West", "Armour"). 2. **EXIF fallback** -- run the extraction script for timestamp and device info: ```bash pip install Pillow --break-system-packages -q python3 /path/to/this/skill/scripts/extract_metadata.py /mnt/user-data/uploads/<filename> ``` The script returns JSON with `timestamp`, `device`, and nearest-station match. Visual identification from the photo is more reliable than GPS matching -- prefer the station name you can read on the sign. **Directional disambiguation**: Some stops have separate northbound and southbound platforms. If the photo or context makes clear which direction (e.g., the sign says "River Market West" vs "River Market East", or the user mentions NB/SB), include that in the report. If unclear, just use the base station name. **If no photo**, gather the station name from conversation context or ask the user. ### Step 2: Gather remaining deta