Content
75%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, actionable instruction skill that conveys xberg-specific conventions without over-explaining basics. It sequences the sync workflow clearly and includes a drift-check validation step, though an explicit feedback loop and a worked example would push it higher.
Suggestions
Add an explicit fix→re-check feedback loop, e.g. 'If task version:check fails on drift, re-run task version:sync then re-check before committing.'
Include one end-to-end worked example (e.g. bumping 1.0.0-rc.32 to 1.0.0-rc.33) showing the exact command sequence and the resulting manifest changes.
Consider moving the per-target integration package list into a short reference table so the core sync/release flow stays scannable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and project-specific with little padding of concepts Claude already knows; explanations (e.g. PEP 440 floor excluding rc) justify non-obvious rationale, though a few lists could be trimmed. | 4 / 5 |
Actionability | Provides concrete, copy-paste-ready commands (task version:sync, version:bump:major|minor|patch, version:set -- <version>, version:check) and specific file paths; minor gap is the absence of a single end-to-end worked example. | 4 / 5 |
Workflow Clarity | The three sync steps are numbered in order with file references, and a validation checkpoint exists (task version:check / --check failing on drift), satisfying the batch-operation validation cap; a fully explicit fix→re-check feedback loop is only implied. | 4 / 5 |
Progressive Disclosure | Well-organized into clear sections (Single source of truth, three steps, lockstep integrations, Do, Don't) with no nested references and all content appropriately placed in one self-contained file; no separate files are needed but none are offered either. | 4 / 5 |
Total | 16 / 20 Passed |