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 a tight, actionable operating contract with strong workflow sequencing and explicit validation/feedback loops for destructive ad-spend changes; progressive disclosure is good but references are inline rather than navigational.
Suggestions
Tighten or remove soft filler like 'Choose available read capabilities and batch related data when useful' to push conciseness toward the 5 anchor.
Move the shared/docs references into a short 'References' or 'Prerequisites' section with labeled links (e.g., 'Operating contract: ../shared/operating-contract.md') to strengthen navigation and progressive disclosure.
Add one concrete example of a safe write flow (e.g., a pause/enable or budget-change call with its dry-run preview and before/after confirmation) to lift actionability toward copy-paste-ready specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and respectful of Claude's competence with no concept-padding; a few sentences such as 'Choose available read capabilities and batch related data when useful' could be tightened further, keeping it just below the 5 anchor. | 4 / 5 |
Actionability | As an instruction-only skill driving a live MCP connector, executable code is not expected, and the guidance is concrete and specific (divide *_local_micro by 1,000,000, resolve targeting names to IDs before applying, create paused then verify); minor gaps in fully copy-paste-ready specificity keep it at 4. | 4 / 5 |
Workflow Clarity | A clearly sequenced Establish scope -> Diagnose -> Execute flow with explicit validation checkpoints and feedback loops (harmless read first, dry-run previews, verify before activation, confirm resulting state after mutation, report partial failures), satisfying the destructive-operation validation requirement. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the three external references (shared operating-contract, measurement-framework, docs/mcp-connection) are one level deep and clearly signaled with markdown links in a well-sectioned body; references sit inline at the top rather than in a dedicated navigation section, a minor organization gap from the 5 anchor. | 4 / 5 |
Total | 17 / 20 Passed |