Content
88%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 strong, densely operational skill: it provides copy-paste-ready commands, exact thresholds and error-code recovery loops, and mandatory validation gates for every fragile operation. Its two weak spots are mild — a few overloaded paragraphs that could be tightened, and long subsections (storyboard grammar, non-Enterprise token binding) that would read better as split-out reference files.
Suggestions
Break the one-paragraph non-Enterprise variables path (line 73) into a short numbered procedure (retrieve → cache → join boundVariables → write bindings) so each step is scannable instead of a single run-on sentence chain.
Move the storyboard grammar (scene units, ordering, diffing, note-verb table) into a references/storyboards.md and keep the section as the cardinal rule plus a clearly-signaled one-level-deep pointer, slimming the main file's token load.
Trim re-derivations of already-stated rules — e.g. the escalation step (line 130) restates the 'frames read as states, not slides' cardinal rule from the section top; a back-reference would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every sentence carries non-obvious, project-specific fact (scope requirements, the ~12-id render-timeout chunk limit, the 15dB PSNR threshold, 60s Retry-After cap) — no explaining of concepts Claude already knows. It falls between 'efficient; minor instances of over-explanation' and the lean top anchor: the non-Enterprise variables path (line 73) is one enormous run-on paragraph, and the Storyboards escalation step (line 130) re-derives the cardinal rule already stated at the section top, so a tightening pass would earn the top score. | 4 / 5 |
Actionability | Fully executable guidance throughout: complete CLI invocations with flags ('hyperframes figma asset ... [--format svg|png|jpg|pdf] [--scale 2]'), a runnable verification script with exact arguments ('node skills/figma/scripts/verify-motion.mjs --reference <export.mp4> --render <render.mp4> --crop WxH+X+Y'), concrete jsonl row shapes for bindings, and named helper functions with their option objects. Specific failure modes and remedies (401 → re-mint, 403 → named scope, 429 → auto-retried) cover the common cases. | 5 / 5 |
Workflow Clarity | The five phases are sequenced in an upfront table with routing by user intent, and validation checkpoints are explicit and mandatory: preflight token-existence check before the first CLI call, the static fidelity self-check against figma's own pixels, the verify-motion PSNR gate with calibration meaning ('FAIL means re-check the translation, not the threshold'), and `npx hyperframes check` before calling it done. Error-recovery feedback loops (retry/backoff behavior, degraded-modes like styles fallback) are spelled out per error code. | 5 / 5 |
Progressive Disclosure | Structure is good: clear section headers mirror the phase table, and the one bundle script (scripts/verify-motion.mjs) is real and referenced with an exact, clearly-signaled path. It sits just below the top anchor because some dense subsections — the storyboard grammar with its note-verb table and the non-Enterprise variables procedure — are candidates for one-level-deep reference files, and a few cited paths (motionEase.ts, ../hyperframes/references/plugin-installation.md) live outside this skill's bundle, so navigation depends on the surrounding project layout. | 4 / 5 |
Total | 18 / 20 Passed |