Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, actionable skill body that delegates build logic to a bundled script and provides concrete commands and validation cues. Main weaknesses are inline time-sensitive version pins, a placeholder plus hardcoded user path, and the absence of an explicit body-level failure feedback loop.
Suggestions
Move the repeated Chrome for Testing version/revision pins into a single named constant or a 'Pinned versions' subsection so they are not duplicated across sections.
Add an explicit 'If the file-presence check fails, rerun the rebuild script and inspect $dist_dir' feedback loop in the Rebuild section so error recovery is documented in the body, not only inside the script.
Replace the hardcoded /Users/jonathanburger path with a parameter or named variable (and document how to override it) so the skill is portable beyond one machine.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and operational with no padding of concepts Claude already knows, but repeats the Chrome version/revision pins and embeds time-sensitive version numbers inline rather than isolating them in a deprecated/old-patterns section. | 4 / 5 |
Actionability | Provides copy-paste-ready commands (the rebuild script invocation, `bun run dev`, `chrome://flags/#canvas-draw-element`) and exact paths, but uses a `<remotion-checkout>` placeholder, hardcodes one user's home path, and several steps are manual Chrome UI interactions rather than executable code. | 4 / 5 |
Workflow Clarity | Three numbered, clearly sequenced workflows with a validation checkpoint (confirm installed directory contains the listed files) and conditional branching in the reload section, but the body lacks an explicit feedback loop for what to do if the file-presence check fails (the script handles errors internally). | 4 / 5 |
Progressive Disclosure | Well-organized into three labeled sections with a clearly signaled one-level-deep reference to scripts/rebuild-extension.sh (a real bundle file) for the heavy lifting; minor gap is that some inline operational detail could remain in the overview, keeping it just shy of the top anchor. | 4 / 5 |
Total | 16 / 20 Passed |