publish-wg-minutes

Process and publish WebPerfWG meeting minutes from Google Docs zip exports. Read this before handling any WebPerfWG meeting minute zip files.

1.00x

Quality

78%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/publish-wg-minutes/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with copy-paste commands, a clear sequenced workflow, and a verification checklist. It is concise and well-structured, with only minor room to add a mid-process validation checkpoint.

Suggestions

Add an explicit validation step after unzip (e.g., confirm index.html exists and unzip exited 0) before running rm, to raise workflow_clarity toward 5 and guard the destructive delete.

Tighten the Date Parsing section by replacing the full month-name list with a compact note ("map month name to zero-padded MM; strip st/nd/rd/th and zero-pad the day").

Consider moving the README link-format examples into a short reference snippet to slim the Process section.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, using copy-paste commands and brief, useful specifics (e.g., diacritics examples); the month-mapping list and restated date-parsing rules are slightly verbose, keeping it just below a 5.	4 / 5
Actionability	Fully executable, copy-paste-ready bash and markdown snippets cover every common case (cp/unzip/rm, mv to index.html, cleaner.sh invocation, README link format), with concrete examples for new-year sections.	5 / 5
Workflow Clarity	Six clearly sequenced steps plus a final checklist provide a strong sequence with verification; not a 5 because there is no explicit mid-process validation checkpoint (e.g., confirm unzip succeeded before deleting the zip) for the destructive rm operations.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Working Directory, Input Format, Process, Date Parsing, Checklist) with no nested references; at ~90 lines it exceeds the simple-skill threshold, so the longer Process section is appropriately inline but not maximally split, keeping it at 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, distinctive, and answers both what and when, though the trigger guidance is implicit rather than a crisp "Use when..." clause. It is concise and free of fluff.

Suggestions

Add an explicit "Use when..." clause with concrete trigger phrases (e.g., "Use when processing WebPerfWG meeting minute .zip exports from Google Docs") to lift completeness toward 5.

Include a file extension synonym (".zip") and a destination cue ("publish to the web-performance repo") to broaden trigger-term coverage.

Optionally enumerate more concrete actions (rename, run cleaner.sh, update README) to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("WebPerfWG meeting minutes from Google Docs zip exports") and two concrete actions ("Process and publish"), but offers no further enumerated actions, matching the '1-2 concrete actions' anchor; not a 4 because coverage is not broad.	3 / 5
Completeness	Clearly states what ("Process and publish WebPerfWG meeting minutes") and provides a when ("Read this before handling any WebPerfWG meeting minute zip files"), but the trigger is phrased as a read-instruction rather than an explicit "Use when..." with concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Includes natural terms users would say ("WebPerfWG meeting minutes", "Google Docs zip exports", "zip files") with good coverage; a 5 would require synonyms/file extensions like ".zip" or "publish to the repo", which are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (WebPerfWG minutes from Google Docs zip exports) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: w3c/web-performance
Path: skills/publish-wg-minutes/SKILL.md
Commit: 6551627

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.