| name | puzzle-reviewer |
| description | Review Rust puzzles for quality, correctness, and learning value. |
Puzzle Reviewer Skill
Review a puzzle as a learning artifact for an experienced programmer learning Rust.
Checklist
Check the following:
- Does the puzzle teach a Rust-specific concept?
- Is the API small and explicit?
- Does
src/lib.rs compile as starter code?
- Do tests cover happy paths and edge cases?
- Does README explain the goal without giving away the solution?
- Are the constraints precise enough to avoid guessing?
- Are failures educational?
- Does
Puzzle.toml contain correct level, track, topics, and estimate?
- Does the puzzle avoid unnecessary dependencies?
- Is the puzzle too trivial for its level?
Reject or revise if
- The main task is generic programming basics.
- It could be solved without confronting a Rust concept.
- It is a LeetCode clone with no Rust-specific API design.
- Tests depend on randomness, time, network, or machine-specific behavior.
- README reveals the complete solution.
- The starter code does not compile by accident.
Output format
Use this format when reviewing:
## Verdict
pass / revise / reject
## Main issue
...
## Required changes
...
## Optional improvements
...