Content
67%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 well-structured overview with genuinely useful progressive disclosure: every section points to a real, one-level-deep reference file, and code examples are concrete and mostly executable. The main cost is token efficiency — the chart-type catalog and Common Workflows sections restate what Claude already knows and duplicate reference-file content.
Suggestions
Trim the Common Workflows section to one-line pointers into the relevant reference files, or make its snippets self-contained (defined variables) so they earn their inline tokens.
Replace the enumerated chart-type catalog with a brief summary plus the existing pointer to references/chart-types.md, since Claude already knows plotly's chart families.
Make later code examples copy-paste ready by defining the data they use (df, z_data, correlation_matrix), which would raise actionability to fully executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is code-forward rather than padded prose, but the chart-type catalog ('Basic Charts: scatter, line, bar, pie...'), built-in template names, and the ~70-line Common Workflows section restate knowledge plotly-literate Claude already has and duplicate content in chart-types.md and export-interactivity.md. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trimming level of anchor 4. | 3 / 5 |
Actionability | Concrete, near-executable guidance throughout: install commands ('uv pip install plotly'), a runnable quick start, hovertemplate usage, write_html/write_image exports with the kaleido dependency, and a Dash app skeleton. Not anchor 5 because later snippets reference undefined variables (df, z_data, correlation_matrix, data), making them illustrative rather than copy-paste ready. | 4 / 5 |
Workflow Clarity | A clear decision workflow is present: explicit px-vs-go selection criteria, a note on combining them, and when to reach for Dash, sequenced from install through quick start to export. The domain is non-destructive so validation checkpoints are not required, but there are minor gaps (e.g., no render/verification step after export), keeping it below the explicit-validation anchor 5. | 4 / 5 |
Progressive Disclosure | All five referenced files exist, are signaled inline at each point of use ('See references/plotly-express.md for complete guide'), are indexed in a Reference Files section, and are verified one level deep with no nested pointers. It falls short of anchor 5 because the inlined Common Workflows and Dash code largely duplicates the reference files' material — a minor organization gap. | 4 / 5 |
Total | 15 / 20 Passed |