Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A compact, well-sectioned body that names the right Elixir tooling, but it leans on generic boilerplate in the Instructions and trigger sections and offers no executable code or validation checkpoints. It reads more as an advisory checklist than a concrete procedural guide.
Suggestions
Replace the generic Instructions boilerplate ('Clarify goals...', 'Apply relevant best practices...') with Elixir-specific procedural guidance or remove it.
Add at least one executable example (e.g., a minimal GenServer or supervision tree snippet) and concrete commands (e.g., `mix test`, `:observer.start()`) to lift actionability.
Turn the Approach list into a real workflow with validation checkpoints (e.g., run `mix credo`/Dialyzer, then re-check after changes) instead of principle-only steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient lists, but padded with templated boilerplate ('Working on elixir pro tasks or workflows', 'Clarify goals, constraints, and required inputs', 'Provide actionable steps and verification') that adds no domain value; not score 3 because of this filler, not score 1 because it never bloats into explaining concepts Claude already knows. | 2 / 3 |
Actionability | Names concrete tools ('Test with ExUnit', 'Profile with :observer and :recon', 'Dialyzer specs', 'Benchee') but provides no executable code, commands, or copy-paste examples; not score 3 because nothing is executable, not score 1 because specific tooling and patterns are given rather than vague abstraction. | 2 / 3 |
Workflow Clarity | The Approach section lists a numbered sequence (1-6) but contains no validation checkpoints or error-recovery feedback loops, and 'validate outcomes' is only implicit; not score 3 because checkpoints are missing, not score 1 because steps are present and sequenced. | 2 / 3 |
Progressive Disclosure | The body is under 50 lines, single-domain, needs no external references, and is organized into clear labeled sections (Use when / Do not use / Instructions / Focus Areas / Approach / Output), meeting the simple-skill allowance for a 3; not score 2 because organization is clean rather than monolithic or poorly signaled. | 3 / 3 |
Total | 9 / 12 Passed |