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.
A highly actionable, well-sequenced diagnostic skill with concrete tooling, error-to-cause mapping, and proper destructive-action validation. Its main weakness is mild redundancy between the workflow and the Important notes recap, and a single-file structure that could offload the tools table and webhook deep-dive to references.
Suggestions
Remove or cross-reference the duplicated guidance in 'Important notes' (Running vs last_synced_at, resync is destructive, delete-data preserves config) that already appears in Step 4, keeping only net-new cautions like the destination-prefixed error note.
Move the 20-row Available tools table and the detailed webhook recovery sub-workflow (Step 4-I) into reference files, leaving a concise overview plus a pointer, to reduce the SKILL.md footprint and improve progressive disclosure.
Tighten the intro paragraph's 'Do not jump straight to resync' guidance so it is stated once and reinforced only in Step 5 rather than repeated across the intro, Step 4-D, and Important notes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense with operational specifics Claude would not know (serializer enum rewriting, webhook failures hidden behind green status) and free of basic-concept padding, but the 'Important notes' section recapitulates points already made in Step 4 (Running isn't always healthy, resync is destructive, delete-data preserves config), a minor redundancy that could be trimmed. | 4 / 5 |
Actionability | Names exact tools, API fields (job_inputs, sync_type_config, incremental_field, last_synced_at), error substrings to match, and a per-root-cause fix; the webhook sub-workflow spells out numbered tool calls with parameters, giving fully executable guidance. | 5 / 5 |
Workflow Clarity | A clearly sequenced five-step workflow with an explicit validation checkpoint (Step 5 requires explicit approval before destructive resync/delete-data/destroy actions) and a decision-tree feedback loop for webhook recovery, satisfying the destructive-operation validation requirement. | 5 / 5 |
Progressive Disclosure | Well-organized with clear section headers (When to use, Available tools, Workflow, Example, Important notes) and no nested references, but the long tools table and the specialized webhook sub-workflow are inlined in a 230-line single file where a one-level-deep reference could keep the overview leaner. | 4 / 5 |
Total | 18 / 20 Passed |