Process and publish WebPerfWG meeting minutes from Google Docs zip exports. Read this before handling any WebPerfWG meeting minute zip files.
96
95%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
This skill covers processing WebPerfWG meeting minutes exported as zip files from Google Docs and publishing them to the web-performance repo.
All work happens in the meetings directory of the web-performance repo:
/Users/yoavweiss/OS/web-performance/meetings/
Zip files are named like:
WebPerfWG call - December 18th, 2025.zipWebPerfWG call - October 9th 2025.zipEach zip contains:
WebPerfWGcallDecember18th2025.html)images/ directory (optional, contains referenced PNGs)Use the pattern {year}/{year}-{MM}-{DD}/ with zero-padded month and day:
2025/2025-12-18/
2025/2025-10-09/
2026/2026-01-15/cp "WebPerfWG call - December 18th, 2025.zip" 2025/2025-12-18/
cd 2025/2025-12-18 && unzip *.zip && rm *.zip && cd ../..mv 2025/2025-12-18/WebPerfWGcallDecember18th2025.html 2025/2025-12-18/index.htmlThe cleaner.sh script in the meetings directory applies formatting fixes (bold speaker names, remove Google Docs boilerplate, fix diacritics like Nicolás Peña, adjust layout):
bash cleaner.sh 2025/2025-12-18/index.htmlrm "WebPerfWG call - December 18th, 2025.zip"Add links under the appropriate year heading in README.md, in reverse chronological order. The link format is:
* [December 18th](https://w3c.github.io/web-performance/meetings/2025/2025-12-18/index.html)If a new year section is needed, add it above the previous year's heading:
# 2026
* [January 15th](https://w3c.github.io/web-performance/meetings/2026/2026-01-15/index.html)
# 2025Extract the month, day, and year from the zip filename. Map month names to numbers:
Strip ordinal suffixes (st, nd, rd, th) from the day and zero-pad to 2 digits.
{year}/{year}-{MM}-{DD}/ patternindex.htmlcleaner.sh run on the HTMLREADME.md updated with link in correct chronological position415abe6
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.