Content
73%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 orchestrator-style skill body: an unambiguous 10-step deployment workflow with real validation checkpoints, error recovery, and safety gates, backed by a well-organized reference bundle. Its main weakness is token efficiency — the prerequisite warnings are repeated to the point of padding — and its execution detail is almost entirely delegated to recipe files rather than inlined.
Suggestions
Consolidate the prerequisite messaging into a single check: the azure-prepare/azure-validate requirement is stated four times (top blockquote, ⛔ STOP block, Validation Proof Check note, Rules 1–2/Step 1) — keep one authoritative statement plus the Step 1 check and delete the rest.
Trim emphasis padding ('AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE', 'DO NOT ASSUME', 'DO NOT SKIP') — the bolded ⛔ markers already carry the emphasis; the extra adverbs add tokens without adding information.
Give Step 5 (Execute Deploy) one or two inline example commands per recipe type (or a pointer to the exact recipe section anchor) so the body is actionable even before the recipe file is opened.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, but the azure-prepare/azure-validate prerequisite is restated four times (top blockquote, the ⛔ STOP block, the 'Validation Proof Check' note, and again in Rules 1–2 and Step 1), with added emphasis padding ('DO NOT ASSUME', 'DO NOT SKIP', 'AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE'). This goes beyond minor trimmable instances. Not 2 because there is no conceptual over-explanation and the rest of the body earns its tokens. | 3 / 5 |
Actionability | Provides concrete anchors: a specific command ('azd provision --no-prompt'), named MCP tools, exact file paths, and a 10-step table pointing to real reference files. Not 5 because 'Execute Deploy — Follow recipe steps' and several steps defer entirely to reference files without any inline detail, leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clearly sequenced 10-step table with explicit validation checkpoints (plan status + Validation Proof check in Step 1, mandatory pre-deploy checklist, error-handling Step 7, verification Steps 8–10), destructive actions gated behind ask_user, and a feedback loop through recipe errors.md. This matches the top anchor exactly. | 5 / 5 |
Progressive Disclosure | The body is a genuine overview with well-signaled references, all of which exist in the bundle (checklist, global-rules, recipes README, azd post-deployment/verify, live-role-verification, sdk references). Not 5 because references run two levels deep (recipes/README.md → recipes/azd/*.md), though SKILL.md deep-links the key second-level files directly, which keeps navigation reasonable. | 4 / 5 |
Total | 16 / 20 Passed |