Content
85%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-organized router skill body that routes effectively with concrete commands, explicit disambiguation, and a validation checkpoint, while appropriately deferring deep authoring detail to sibling domain skills. The main weakness is mild verbosity in the versioning/update section.
Suggestions
Tighten the "Keeping skills current" section: lead with the user-facing check/update commands and move the --skip-skills/HYPERFRAMES_SKIP_SKILLS and offline-fallback implementation details into a one-line aside or a referenced doc.
The "Workflow details" block repeats input/output/trigger triples that largely mirror the cheat-sheet table; consider collapsing to a table or keeping only the disambiguating detail per workflow to reduce token cost.
Add a one-line explicit "validate after routing" note (e.g. re-confirm the chosen workflow's specifics at its first step) so the validation checkpoint reads as a numbered workflow step rather than prose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and decision-relevant throughout with little concept re-explanation, but the "Keeping skills current" section over-explains mechanism details (e.g. the "neutered" --skip-skills flag, GitHub round-trip fallback behavior) that could be trimmed. Not a 5 because a few passages pad rather than instruct. | 4 / 5 |
Actionability | Concrete, copy-pasteable commands ("npx skills add heygen-com/hyperframes --skill <workflow-name>", "npx hyperframes skills check --json") and explicit per-workflow triggers and defaults (16:9 / 9:16, language). Not a 5 because as a router it intentionally delegates executable authoring steps to domain skills rather than including them inline. | 4 / 5 |
Workflow Clarity | Clear sequenced flow — confirm input before routing, pick a workflow via the cheat-sheet/disambiguation, verify it is installed, then continue — with an explicit validation checkpoint ("check it's actually available to you"; skills check exits non-zero when outdated or missing). No destructive/batch cap applies. | 5 / 5 |
Progressive Disclosure | Well-structured overview → capability map (domain skills loaded on demand) → intent router → per-workflow details, with one-level-deep, clearly signaled references to sibling skills (/hyperframes-core, /hyperframes-animation, etc.) and no nested reference chains. No bundle files exist in this skill, and the body's cross-skill pointers are the appropriate disclosure pattern. | 5 / 5 |
Total | 18 / 20 Passed |