Content
75%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 well-structured, concise instruction skill with a solid approval-and-read-back workflow for destructive CRM writes. The main gaps are the absence of concrete tool-call examples and a dead external reference.
Suggestions
Verify the ../docs/mcp-connection.md link resolves (it does not exist on disk) or inline the minimal connection steps so the skill is self-contained.
Add one or two concrete example tool invocations or the exact read used to confirm connected locations, so guidance is copy-paste ready rather than delegated to live discovery.
Convert the write workflow into an explicit numbered checklist with an error-recovery branch (validation fails → fix → re-read), to lift workflow clarity to a full feedback-loop standard.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's knowledge (no explanation of what a CRM or MCP is), with only minor contextual padding such as the legacy "/api/mcp/gohighlevel" route note, matching the efficient-with-minor-trim anchor. | 4 / 5 |
Actionability | Concrete, specific guidance ("Show the exact location, object, current value, proposed value, risk, and rollback before acting. Obtain approval, apply once, then read back", "pass an explicit locationId", "Use ISO 8601 datetimes") is actionable, but it delegates tool selection to live capability discovery rather than naming calls/examples, so it is not fully copy-paste ready. | 4 / 5 |
Workflow Clarity | A clear three-phase sequence (Establish the live location → Read before changing → Execute approved changes safely) with validation checkpoints (resolve ids first, approval gate, read-back confirmation, partial-failure reporting) covers the destructive-write case well, but the phases are mostly prose rather than a numbered checklist with explicit error-recovery loops. | 4 / 5 |
Progressive Disclosure | The under-50-line body is well-organized into clear sections and keeps bulk detail out, but its only navigation aid is a single one-level reference to ../docs/mcp-connection.md, which does not exist on disk (dead link), and no bundle files are present, leaving minor organization gaps. | 4 / 5 |
Total | 16 / 20 Passed |