Content
53%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 lean, well-intentioned router that gives a few concrete commands and good conditional loading guidance, but it delegates the entire deployment workflow and all substantive detail to files outside the bundle via a two-level chain of pass-through references. The body alone leaves an agent without the executable steps or ordered workflow it needs.
Suggestions
Inline or relocate the actual content: replace the pass-through reference stubs (each pointing to ../../../../cli/templates/deployment/references/*.md) with real content one level deep, or point SKILL.md directly at the final files so references are a single hop.
Include the deployment step sequence in the body (collect model key + sign-in method, choose broker, deploy via the selected provider, run acceptance checks, release gate) so the workflow does not depend solely on an external deployment.md.
State the key acceptance checks and the handoff deliverables concretely (e.g., the exact qm check --live command invocation and what the handoff must contain) instead of referencing them by name only.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean (~150 words), assumes competence, and every sentence gives instruction (e.g., "Do not require or clone the QM source repository"). Not 5: email guidance is split across two paragraphs and "references/email.md" is named twice, a redundancy that could be trimmed into one statement. | 4 / 5 |
Actionability | Concrete commands appear ("npm exec qm -- <command>", "qm admin-login", "qm check --live", "modelProvider"), but the actual deployment procedure is delegated to "../../../deployment.md", which lives outside the bundle — the key executable steps are missing from the body. Not 4: the gap is central, not minor; not 2: several specific, runnable commands are given. | 3 / 5 |
Workflow Clarity | Sequence signals exist but are implicit in prose ("Collect both in the same pass", "Read references/email.md once the operator has chosen the broker") and the authoritative sequence is in the external deployment.md. A validation gate is named ("Treat qm check -- live... as the automated release gate") but the steps connecting the checkpoints are not laid out in-body. Not 4: the ordering is not clearly presented within the skill. | 3 / 5 |
Progressive Disclosure | Top-level signaling is good ("Read only the selected provider reference", "Read references/slack.md only when Slack is requested"), but against the actual bundle every file in references/ is itself a pass-through pointer to "../../../../cli/templates/deployment/references/*.md" — a second indirection level that does not resolve in the bundle — and SKILL.md points to "../../../deployment.md" outside the bundle. Not 1: the top-level navigation is clear; not 3: the real content is buried two reference levels deep, matching the nested-pointer anti-pattern. | 2 / 5 |
Total | 12 / 20 Passed |