Content
81%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.
The body is exceptionally actionable with a clearly gated, validated workflow and concrete error recovery for every failure mode. Its main weakness is token efficiency — repeated shell guards and restated binding rules — and moderately good, though not fully split-out, content structure.
Suggestions
Factor the repeated four-line bash guard into one canonical block and reference it ('use the canonical Bash guard below') instead of duplicating it in every code block.
Consolidate the root-binding/context rules stated in the 'Invocation context' section, Step 5, and the forwarding template into a single authoritative statement to cut restated tokens.
Move the version-gated roadmap notes (v0.2 selectedrelationshipsschema, v0.5 CloneMobileOfflineProfile work) into a clearly labeled 'Not yet supported' subsection or reference to avoid time-sensitive content in the main flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly operational with no concept over-explanation, but the identical `cd -- '<working_dir>' || { echo "BLOCKED..."; exit 1; }` guard is repeated in six code blocks and the root-binding contract is restated in at least three sections ("Apply the canonical contract to every shell call", "All linked recovery commands... must bind the same root", "The recipient must enforce the same canonical root contract"), which could be factored out. | 3 / 5 |
Actionability | Fully executable throughout: exact node CLI calls with complete $select field lists, concrete PATCH bodies, a flag-pattern table with ranges (sync 5–1440), specific error-code handling (400 / 0x80071141 circular relationship), and a copy-paste-ready context-forwarding template. | 5 / 5 |
Workflow Clarity | The 7-step sequence has explicit validation checkpoints (Step 3 current/proposed diff with a single confirm gate, Step 6 re-read of changed items to update artifacts) and feedback loops for error recovery (parse the cycle path, prompt to drop an association, retry; 403/PrivilegeCheckFailed is BLOCKED, not retried), plus a defined status-code contract. | 5 / 5 |
Progressive Disclosure | References are one level deep and well-signaled with purpose (e.g. "dataverse-offline-api.md §4 / §7 — POST item + PATCH selectedcolumns"), but no bundle files exist in this skill directory to verify the ${PLUGIN_ROOT}/shared paths against, and the ~270-line body inlines substantial contract and error-handling detail that could partly live in a shared reference. | 4 / 5 |
Total | 17 / 20 Passed |