Content
46%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 body is a cleanly organized, token-efficient index that correctly practices one-level-deep progressive disclosure on paper. However, the entire bundle of rule files it points to is missing, so the skill delivers no actual domain knowledge and no actionable guidance. Shipping the rules/ directory (or inlining a minimal quick-start) is the critical fix.
Suggestions
Ship the rules/ directory with all referenced files, or remove/repair the links — 34 dangling references currently make the skill unusable.
Add a minimal inline quick-start (one small code sample of a Composition with an animated component) so the skill provides some standalone value before file loading.
Fold the four topical sections (Captions, FFmpeg, Audio visualization, Sound effects) into the single rule list or give them trigger conditions, since they currently duplicate the list's format with less context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean routing index (one line per topic, e.g. 'load the [./rules/subtitles.md](./rules/subtitles.md) file for more information') with no explanation of concepts Claude already knows. Minor trimmable filler remains ('to obtain the domain-specific knowledge', the repeated 'for more information'), matching anchor 4 rather than the every-token-earns-its-place bar of 5. | 4 / 5 |
Actionability | The body contains no code, commands, or inline examples — its only guidance is 'load file X', and all 34 referenced rules/*.md files are absent from the bundle, so the pointers lead nowhere. This is anchor 2 (high-level hints missing the specific steps to execute); not 1 because the pointers do give concrete file-to-topic routing instructions. | 2 / 5 |
Workflow Clarity | As a simple routing skill the single action (match task to rule file, then read it) is unambiguous, but the workflow dead-ends because none of the referenced rule files exist. It sits between anchor 2 and 4: clear sequencing of intent, but the executable step cannot be carried out. | 3 / 5 |
Progressive Disclosure | The structure is well-signaled (descriptive one-line entries, references one level deep), but scored against the actual bundle every referenced path (./rules/subtitles.md, ./rules/ffmpeg.md, and all 30 files under 'How to use') is missing, leaving navigation broken. The good organization cannot lift it above 2 when no reference resolves. | 2 / 5 |
Total | 11 / 20 Passed |