Content
72%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-structured index-style skill body: dense with non-obvious CLI facts, excellent progressive disclosure with a verified topic-to-file map, and a destructive-op warning. The main gaps are the absence of any in-body setup sequence or validation/verification guidance (notably around the irreversible delete-group) and a redundant restatement of the grep instruction.
Suggestions
Add a brief numbered quick-start sequence in the body (create group → add microfrontends.json → install @vercel/microfrontends → integrate framework → deploy), or explicitly point to the Getting Started steps in references/configuration.md from the overview.
Add a verification checkpoint before the irreversible delete-group operation (e.g., run inspect-group first to confirm the target group and projects).
State the grep-on-demand instruction once instead of twice to trim the duplicated guidance around reference usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~30-line body is dense with non-obvious operational facts (interactive-terminal requirements, free-tier blocking of --non-interactive, --project-default-route format) and teaches no known concepts. However, the grep instruction is stated twice — 'Do not read all references upfront. Instead, search or grep the relevant file' and again after the table 'use grep or search over the relevant reference file... without loading all references into context' — a minor instance of over-explanation that could be trimmed, matching anchor 4 rather than 5. | 4 / 5 |
Actionability | Concrete, executable commands with exact flags ('vercel microfrontends create-group', 'inspect-group --format=json', 'pull --dpl') and precise behavioral caveats. It falls short of anchor 5 because no complete example invocation is shown (e.g., a full non-interactive create-group command) and the end-to-end setup steps are delegated to references/configuration.md rather than given inline. | 4 / 5 |
Workflow Clarity | The body is an overview plus command reference and reference-routing table; the actual setup sequence lives in references/configuration.md, so the body itself presents no ordered multi-step workflow and no validation checkpoints. Notably 'delete-group — delete a group and all its settings, irreversible' is a destructive operation with no verification guidance, which caps this at 3 per the destructive-operation rule. It is not a 2 because the concepts-to-CLI-to-deep-dives organization is coherent and each reference file contains its own well-sequenced steps. | 3 / 5 |
Progressive Disclosure | A clear overview body with a well-signaled, one-level-deep reference table mapping six topics to six real files (all present in references/ and topical), plus explicit instruction to grep the relevant file instead of loading everything. This matches the anchor-5 pattern of an easy-to-navigate overview pointing to appropriately split detail. | 5 / 5 |
Total | 16 / 20 Passed |