Content
42%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 has a clean section structure and the Best Practices list contains real domain knowledge (permissive-to-strict mTLS, sidecar sizing, destination rules), but the Instructions and non-use sections are generic template filler, the workflow carries no validation checkpoints, and there is not a single executable command or YAML example. The lone reference to resources/implementation-playbook.md points to a file that does not exist in the bundle.
Suggestions
Add executable examples for the common cases: istioctl install flags, a VirtualService traffic-splitting YAML for canary deploys, and a sample STRICT-mTLS AuthorizationPolicy — currently no step can be acted on directly.
Fix or remove the dangling reference to `resources/implementation-playbook.md`; if detailed examples belong there, ship the file (e.g., under references/) and link it by its real path.
Replace the template filler ("Clarify goals, constraints, and required inputs", "The task is unrelated to service mesh expert") with mesh-specific guidance, and add validation checkpoints to the workflow (e.g., run `istioctl verify-install` / `istioctl analyze` after applying policies, verify mTLS with `istioctl x authz check`).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows, but it is padded with generic template filler — "Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes", and a circular non-use section ("The task is unrelated to service mesh expert") — plus an intro paragraph that duplicates the description. Mostly efficient with unnecessary boilerplate to trim: anchor 3, not 4 because the filler sections add no mesh-specific value. | 3 / 5 |
Actionability | There is no code, no command, and no configuration example anywhere — "Istio and Linkerd installation, configuration" and "Implement security policies (mTLS, AuthorizationPolicy)" are high-level hints that name real Istio concepts but omit the specific steps to execute (no istioctl commands, no VirtualService/DestinationRule/AuthorizationPolicy YAML). Anchor 2 (minimal concrete guidance), not 1 because specific technologies and policy kinds are named; not 3 because nothing in the body is executable or copy-paste ready. | 2 / 5 |
Workflow Clarity | The 7-step Workflow has a coherent sequence ("Assess current infrastructure" → "Design mesh topology" → "Implement security policies" → "Test failover"), but no step includes a validation checkpoint or concrete command — "Test failover and resilience patterns" gives no method. Anchor 3 (steps listed, checkpoints missing), not 4 because verification is only implicit. | 3 / 5 |
Progressive Disclosure | Sections are consistently organized (Instructions, Capabilities, Use when, Workflow, Best Practices), but the single reference — "open `resources/implementation-playbook.md`" — is a dangling pointer: no such file exists in the bundle (no references/, scripts/, assets/, or resources/ directories). Anchor 3 (structure present but references not usable), not 4 because navigation to the referenced detail is broken and the mesh-specific detail the reference should hold is simply missing. | 3 / 5 |
Total | 11 / 20 Passed |