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 well-engineered, self-contained workflow: concrete MCP tool contracts, a clearly sequenced 10-step interview with validation and error-recovery branches, and honest guardrails against fabricating state. The only structural note is that everything lives inline in one file with no progressive-disclosure layer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and instructional — exact tool calls, patch-op shapes, and file-naming conventions with almost no padding or explanation of concepts Claude already knows. Minor asides (the Tone section, "GSC is the richest first-party signal: ...") could be trimmed, keeping it just below the 'every token earns its place' anchor. | 4 / 5 |
Actionability | Guidance is copy-paste ready for an instruction-only skill: exact MCP tool signatures (`update_project_context(projectId, updates)`), concrete patch-op shapes (`{ section: "business_overview" | ... }`, `{ addCompetitors: [{ domain, name?, notes? }] }`), specific tool names for every branch, and literal CSV filenames like `gsc/queries-last-3-months.csv`. Specific examples cover the common cases throughout. | 5 / 5 |
Workflow Clarity | Ten numbered steps in a logical dependency order (resolve projectId before any writes, read existing context before asking), with explicit validation checkpoints and feedback loops: "If the project list is ambiguous, ask the user", "If no project matches, offer to create one", "If the MCP is unavailable, tell the user to connect", and "do not claim Search Console is connected unless `get_search_console_performance` confirms it". | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the single-file body is cleanly sectioned with a scannable checklist, output template, and guardrails — nothing that clearly belongs in a separate reference file is inlined. It does not reach 5 because there are no well-signaled references at all and the ~190-line body keeps everything at one level, leaving minor organization headroom (e.g. the GSC export details or next-workflow table could live in a reference file). | 4 / 5 |
Total | 18 / 20 Passed |