Content
75%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.
A thorough, highly actionable seaborn reference with copy-paste code across all major plot types and well-organized sections plus properly signaled reference files. The main weakness is conciseness: the body inlines a good deal of API detail Claude already knows that could live in the reference files.
Suggestions
Trim or relocate the full color-palette enumerations and per-parameter explanations of hue/size/style into references/function_reference.md to reduce body length and token cost.
Consolidate the repeated 'When to use' bullet lists across sections into a single decision table to avoid restating the same guidance.
Move the per-category 'Key parameters' blocks into the function reference, keeping only a representative example inline in the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is well-structured and mostly useful, but at ~660 lines it restates seaborn API knowledge Claude already has (full palette enumerations, per-parameter explanations of hue/size/style, multiple 'When to use' lists) that could be tightened or pushed to references. It is not a 2 because the material is organized and actionable rather than padded tutorial prose, and not a 4 because the unnecessary explanatory restatement is more than minor. | 3 / 5 |
Actionability | Provides abundant copy-paste-ready, executable code across every major plot category, with concrete function names and key parameter listings covering the common cases. It is not below 5 because the examples are complete and runnable, matching the anchor-5 example. | 5 / 5 |
Workflow Clarity | The 'Best Practices' section sequences guidance from data prep through plot choice, faceting, semantic mapping, estimation, matplotlib integration, and saving, giving a clear sequence. It is not a 5 because there are no explicit validation/feedback checkpoints, and not a 3 because the sequence is clear and the skill is non-destructive so the validation cap does not apply. | 4 / 5 |
Progressive Disclosure | A Resources section clearly signals three one-level-deep reference files (function_reference.md, objects_interface.md, examples.md), all confirmed present, with a concise overview pointing to them. It is not a 5 because substantial reference-grade content (full palette and per-category parameter lists) is inlined in the body rather than fully delegated to the reference files. | 4 / 5 |
Total | 16 / 20 Passed |