Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tightly written, well-organized MCP-orchestration skill with a clear workflow and good voice guidance, held back primarily by its missing reference.md bundle file — the body leans on it for templates and GROQ that are not inlined — and by implicit rather than explicit validation checkpoints in the workflow.
Suggestions
Ship the missing reference.md (containing the GROQ fetch queries, Portable Text cheat sheet, and changeBlock template) or inline those templates directly into SKILL.md — currently all section-anchored references resolve to a file absent from the bundle.
Add an explicit validation checkpoint after create_documents, e.g. fetch the draft back via GROQ and confirm the block _keys and structure before reporting success, rather than only warning about JSON brace/bracket errors.
Make destructive-op verification explicit: confirm the target draft count/IDs before discard_drafts, and re-fetch the document after publish_documents to verify the published state.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and dense — assumes Claude knows what Sanity, Linear, and Portable Text are, and every line earns its place (e.g. "brace/bracket errors are the most common failure" is a high-value earned detail rather than padding). | 3 / 3 |
Actionability | Gives concrete tool names (create_documents, patch_documents, discard_drafts, publish_documents) and an executable GROQ patch example (content[_key=="fd1ce739c172"]), but the key copy-paste artifact — the Portable Text document JSON template — is deferred to reference.md, which is not present in the bundle, leaving a gap in the most important executable detail. | 2 / 3 |
Workflow Clarity | A clear 7-step sequenced checklist with sensible guards on destructive ops (confirm intent for discard_drafts, publish only when asked), but validation checkpoints are implicit rather than explicit — there is no verify-after-create step (e.g. fetch the draft back to confirm blocks/_keys) despite create_documents JSON being flagged as the most common failure. | 2 / 3 |
Progressive Disclosure | The overview is well structured and references are clearly signaled one level deep with section anchors, but every reference points to reference.md (fetch-reference-ids, linear-release-review, portable-text-cheat-sheet, changeblock-template) and that file does not exist in the bundle, so the navigation is broken. | 2 / 3 |
Total | 9 / 12 Passed |