Content
67%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 well-structured dispatch skill with genuinely executable commands and strong fail-closed error handling for the inline path. Its main weaknesses are redundant routing descriptions across three sections and heavy reliance on external workflow files for the primary configuration paths.
Suggestions
State the flag routing once (the <routing> table) and have <objective> and <context> reference it instead of restating it.
Move the generic Pi dispatch boilerplate to a shared reference file and keep only the GSD-specific dispatch notes inline.
Spell out what "Preserve all workflow gates from the target workflow" concretely requires, or point to where those gates are defined.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, but the flag-routing logic is stated three times (in <objective>, the <routing> table, and <context>), and lines like "The text inside <arguments> is exactly what the user typed" spend tokens on conventions that could be tightened. | 3 / 5 |
Actionability | Guidance is largely executable — "command -v gsd-tools", the install hint string, "gsd-tools query config-set-model-profile <profile-name> --raw", and concrete gsd_dispatch role/task parameters — but the default/--advanced/--integrations paths only delegate to external workflows without showing any of their steps. | 4 / 5 |
Workflow Clarity | The sequence (parse flag → load workflow or run inline command → preserve gates) is clear with explicit checkpoints: a PATH pre-check that stops with an install hint, and fail-closed dispatch handling that stops on unresolved roles or child failure with optional-vs-required escalation. It falls short of 5 because the primary config paths inherit their validation from the external workflows rather than defining feedback loops here. | 4 / 5 |
Progressive Disclosure | The three workflow references are one level deep and clearly signaled in a dedicated <execution_context> block with an instruction to read them first, and sections are well organized. Minor gaps come from the duplicated routing content inlined in three sections and the Pi dispatch boilerplate that a shared reference could carry. | 4 / 5 |
Total | 15 / 20 Passed |