Content
78%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.
The content is a highly actionable, well-sequenced workflow: exact commands, paths, naming conventions, and a justified code template cover the common cases, with validation checkpoints and a pitfalls checklist. Its weaknesses are token efficiency and progressive disclosure — the large inline WebGL2 boilerplate template both pads the file and belongs in a separate reference file. Adding an explicit error-recovery step would round out the workflow.
Suggestions
Move the full WebGL2 boilerplate template (vertex/fragment shaders, state type, setup/apply/cleanup) into a references/ file such as references/webgl2-effect-template.ts, keeping a short skeleton plus a one-level-deep pointer in SKILL.md.
Trim the generic parts of the inline example (standard vertex shader, MyEffectState type) by pointing to halftone.ts or blur/blur-runtime.ts as the canonical pattern instead of reproducing them.
Add an explicit error-recovery step after builds and tests, e.g. "If bun test or bun run build fails, fix the errors and re-run before proceeding to docs and demos."
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence (no explanations of WebGL or Remotion basics) and stays instructional throughout, but the ~130-line template inlines generic boilerplate (standard vertex shader, state types, shader plumbing) that duplicates existing files like "halftone.ts" and could be trimmed to a pointer; not 5 because that boilerplate does not earn its place, not 3 because there is no padding or teaching of known concepts. | 4 / 5 |
Actionability | Guidance is fully executable: exact commands ("bun test src/test", "bunx remotion still src/remotion/entry.ts effects-my-effect-preview static/img/effects-my-effect-preview.png --overwrite --image-format=png", "bun render-cards.ts"), exact file paths and docs frontmatter fields, and a near copy-paste template; the single placeholder createMyEffectState() is explicitly justified by pointing to concrete existing runtime files, which the rubric guidelines permit. | 5 / 5 |
Workflow Clarity | Ten numbered steps in correct dependency order with explicit validation checkpoints ("bun test src/test", "bun run build", "bun run formatting", "git diff --check") and a "Common pitfalls" checklist; not 5 because explicit error-recovery feedback loops (e.g. "if tests fail, fix and re-run") are missing, not 3 because checkpoints are explicit and appear at multiple stages. | 4 / 5 |
Progressive Disclosure | Sections are well organized and every cross-reference (writing-docs, docs-demo, offload-r2 skills; existing effect files) is clearly signaled, but the ~130-line WebGL2 template is exactly the detailed material that belongs in a references/ file, and no bundle files exist so everything is inline in a ~350-line SKILL.md; not 4 because inlining that bulk is more than a minor organization gap, not 2 because nothing is buried and structure is good. | 3 / 5 |
Total | 16 / 20 Passed |