Content
86%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 tight, example-driven guidelines skill that respects token budget and gives concrete, API-level direction for every design decision. The main improvements are a small copy-adaptable code snippet for menu contributions and an explicit verification step when changing group IDs across extensions/*/package.json.
Suggestions
Add one minimal example of the two contribution forms in practice — an Action2 registration with `group`/`order` and a `package.json` `menu` entry using `group@n` — so the syntax is copy-adaptable rather than assumed.
For the rule 'When you change one [group ID], update every contribution', add a verification checkpoint such as searching the repo (including `extensions/*/package.json`) for the old group ID before considering the change done.
Order the Rules section to mirror the application sequence (choose group → set order → gate with `when`/`precondition` → label) so a reader applying them to a new menu has an implicit order of operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean: the group table and terse rules ('Destructive actions last', 'Keep it short') convey non-obvious, project-specific conventions with no padding and no explanation of concepts Claude already knows. Every token earns its place. | 5 / 5 |
Actionability | Concrete guidance throughout — exact group IDs (`navigation`, `1_state`…`4_manage`), ordering mechanisms ('`order` (or `group@n` in `package.json`)'), and named APIs (`when`, `precondition`, `Separator.join`, `MenuId`). It falls short of fully executable because no snippet shows the Action2 `menu` registration or `group@n` contribution syntax in practice, leaving a minor gap for the reader. | 4 / 5 |
Workflow Clarity | For a simple single-purpose skill the rules are individually unambiguous (group table, per-rule bolded imperatives), but they are presented as a flat list with no order of application. The group-ID-change rule ('update every contribution, including `extensions/*/package.json`') is a batch update with no verification checkpoint such as searching for the old ID, a minor validation gap. | 4 / 5 |
Progressive Disclosure | Under 50 lines with no need for external references, and the content is well organized into a purpose statement, a 'Group order' section with a table, and a 'Rules' section. Per the simple-skill guideline, this earns full marks with just well-organized sections; the only links are attribution URLs, appropriately inline. | 5 / 5 |
Total | 18 / 20 Passed |