Content
20%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a persona-and-taxonomy dump that re-states Scala knowledge Claude already has, with no concrete code, commands, or real workflow. It reads as a knowledge outline rather than actionable skill guidance.
Suggestions
Replace the concept taxonomy with concrete, executable guidance: code snippets, build commands (sbt/Mill), or copy-paste templates for the most common tasks (e.g., a Pekko Streams pipeline, a Cats Effect error-handling pattern, a ZIO service definition).
Cut the enumeration of well-known concepts (monads, Catalyst optimizer, GC tuning) and keep only non-obvious project-specific conventions, decisions, or pitfalls Claude would not already know.
Turn the generic three-step Instructions into a real sequenced workflow with explicit validation checkpoints (e.g., compile → run tests → benchmark with JMH) for system-design and performance tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a long enumeration of domain concepts Claude already knows ("functors, monads, applicatives", "Catalyst optimizer", "generational GC, heap tuning (G1/ZGC)", "union/intersection types"), padded with taxonomy that does not earn its tokens. | 1 / 3 |
Actionability | No executable code, commands, or concrete examples appear; guidance is abstract ("Design for horizontal scalability", "Implement eventual consistency with well-defined conflict resolution strategies"), describing rather than instructing. | 1 / 3 |
Workflow Clarity | The Instructions section lists a loose sequence ("Clarify goals", "Apply relevant best practices and validate outcomes", "Provide actionable steps and verification") and mentions validation, but there are no concrete checkpoints or feedback loops for risky operations like system design or perf optimization. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but is a monolithic single file; the detailed framework/tooling taxonomy (Cats Effect, Pekko Streams, Doobie, Tapir, etc.) that could live in separate reference files is all inline with no external references. | 2 / 3 |
Total | 6 / 12 Passed |