Content
35%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 well-sectioned but padded with ecosystem knowledge Claude already possesses and provides almost no executable code or commands. Its one progressive-disclosure reference is broken (the file does not exist), and workflows lack explicit validation checkpoints.
Suggestions
Cut the "Capabilities", "Knowledge Base", and "Behavioral Traits" package lists down to a few non-obvious specifics, or move them into a real reference file, to reduce token cost for things Claude already knows.
Add copy-paste-ready examples (e.g., a Pkg.jl workflow snippet, a @code_warntype type-stability check, a BenchmarkTools.jl benchmark) to make the guidance executable.
Create the referenced `resources/implementation-playbook.md` (or fix the path) and insert explicit validation steps (e.g., 'run @code_warntype; fix type instabilities; re-check') into the Response Approach so the workflow has feedback loops.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body devotes 80+ lines of "Capabilities", "Knowledge Base", and "Behavioral Traits" to enumerating Julia packages and ecosystem facts Claude already knows, with padded restatement across sections — fitting 'noticeably verbose; several unnecessary explanations or padded sections' below the mostly-efficient 3 anchor. | 2 / 5 |
Actionability | There is no executable code or concrete command anywhere; guidance like "Apply relevant best practices and validate outcomes" and "Profile and optimize using BenchmarkTools.jl and Profile.jl" are high-level hints missing the specific steps to execute, matching the 2 anchor rather than the pseudocode-bearing 3 anchor. | 2 / 5 |
Workflow Clarity | The "Response Approach" gives a clear 8-step numbered sequence (Analyze → Design → Implement → Test → Profile → Document → Format), but checkpoints are only implicit and no validation/feedback steps are defined, fitting 'steps listed but validation gaps; checkpoints missing or implicit'. | 3 / 5 |
Progressive Disclosure | Section headers organize the body well, but the single external reference (`resources/implementation-playbook.md`) is a dangling path to a nonexistent file and the bulk package-listing that should live in a reference file is inlined, fitting 'some structure, references present but not clearly signaled, content that should be separate is inline'. | 3 / 5 |
Total | 10 / 20 Passed |