← ClaudeAtlas

ieee-vtools-reportinglisted

Automate IEEE vTools event reporting for any IEEE organizational unit (Section, Affinity Group, Chapter, Student Branch). Syncs Google Calendar events into a tracking Google Sheet with vTools-form-ready fields, auto-detects which events are already reported on events.vtools.ieee.org, and produces gap lists and form-fill sheets. Use this skill whenever the user mentions vTools, IEEE event reporting, ExCom meeting reports, L31/activity reporting, IEEE OU officer duties, unreported IEEE events, or wants to reconcile an IEEE calendar against vTools — even if they only say "which IEEE events haven't I reported yet".
Ramneek-kalra/ieee-vtools-reporting-skill · ★ 0 · Data & Documents · score 62
Install: claude install-skill Ramneek-kalra/ieee-vtools-reporting-skill
# IEEE vTools Event Reporting Help IEEE volunteers (Section/AG/Chapter/SB officers) keep vTools event reporting complete with minimal manual work. The workflow has three parts: a Google Apps Script tracker (bundled), a gap-analysis method, and an assisted form-filling routine. ## Key facts about vTools (verified July 2026) - **There is no public write API.** Event reports must be submitted at https://events.vtools.ieee.org/ while logged in with an IEEE account. Never promise fully unattended submission; the human always clicks Save & Publish. - The JSON API (`/RST/events/api/public/v8/events/list?span=A~B`) works but **ignores OU filter parameters** — it returns events from all of IEEE, so it is impractical for per-OU reconciliation. - The OU-filtered source that works, without login, is the public advanced search page: `https://events.vtools.ieee.org/events/search/advanced?meeting[ou_spoid]=<SPOID>&meeting_after=<YYYY-MM-DD>&meeting_before=now&sub=true&page=<N>` Parse event titles from the `/m/<id>` anchor tags in the HTML. There is no ICS/RSS variant (`.ics` returns HTTP 500). - Officers can email eventsfeedback@ieee.org to ask about authenticated API/feed access. ## Information to gather from the user first Ask for (or find in prior context) these values — the script cannot work without them: 1. **Calendar ID** — the Google Calendar holding their IEEE events (often their `name@ieee.org` alias calendar). 2. **OU SPOID** — e.g. `YP00123`, `CH02165`, `S