Content
88%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.
An exceptionally actionable, well-sequenced operational skill with explicit validation, gating, idempotency, and recovery handling. Remaining improvements are token-level: deduplicate the repeated working-directory guard boilerplate and move verbose command/query detail into a reference file.
Suggestions
State the working-directory guard once (e.g., 'Run every command from <working_dir>') and remove the repeated cd/BLOCKED boilerplate from each code block to cut significant token waste.
Move the long OData discovery queries and the AskUserQuestion dialog templates into a reference file (e.g., shared/references/dataverse-offline-api.md §12 or a membership-discovery reference), keeping only the command shape inline.
Trim the opening two paragraphs, which largely restate the frontmatter description and shared-instructions content already loaded at invocation time.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and operational with no concept padding — every section is task-specific. However, the 'cd -- <working_dir> || { echo BLOCKED... }' guard is repeated verbatim in roughly nine code blocks and the opening paragraph restates the frontmatter description, so minor trimming opportunities remain. | 4 / 5 |
Actionability | Fully executable guidance throughout: concrete node CLI invocations with exact OData $filter/$select/$expand query strings, POST bodies with @odata.bind navigation properties, a flags table, exact AskUserQuestion dialog copy with options, status codes, and a duplicate-409 rescue note — copy-paste ready modulo clearly marked placeholders. | 5 / 5 |
Workflow Clarity | The 7-step sequence is explicitly mapped up front, includes a single confirmation gate (Step 4), an explicit verification step with readback assertion (Step 6), idempotent re-run guidance, and a failure-recovery section — satisfying the validation requirement for batch operations with clear feedback loops. | 5 / 5 |
Progressive Disclosure | The top references block is well-signaled with per-file descriptions pointing one level deep to shared files (entity field maps and API recipes are properly delegated out of the body). Minor gaps: full OData query strings and dialog templates remain inline where a reference could hold them, and the referenced ${PLUGIN_ROOT}/shared paths cannot be verified against this skill's bundle since no local references/ or scripts/ directories exist. | 4 / 5 |
Total | 18 / 20 Passed |