Version 1 of 1 · published Sep 8, 2026Version 1 · only version
Score 0
Creates a private draft copy of “Critique an existing chart for misleading interpretation” that credits the original. You'll add your own example result before publishing.
Example output
No public result for version 1 yet
Nobody has shared what a model actually produced from this exact version, and PromptByte never generates examples itself. Run the prompt and add yours to fill this in.
Fill in the values below — the customized prompt updates as you type.* marks a required value.
Who reads the chart and the decision it supports. Default: Operations managers comparing monthly support performance.
Attach a chart or describe its actual scales, labels and values. Default: Illustrative specification: vertical bars for January 82% and February 86%; y-axis spans 80%-90%; title says Performance doubled; no sample sizes shown.
Definitions, denominators, source data and intended claim. Default: Metric is tickets resolved within one business day. January had 100 tickets and February 50. The intended question is whether resolution improved.
Customized prompt
live preview
Resolved user prompt10 lines
Critique this existing chart for Operations managers comparing monthly support performance..
Chart image or precise specification: Illustrative specification: vertical bars for January 82% and February 86%; y-axis spans 80%-90%; title says Performance doubled; no sample sizes shown.
Underlying metric definitions and intended claim: Metric is tickets resolved within one business day. January had 100 tickets and February 50. The intended question is whether resolution improved.
Check whether the encoding supports the intended comparison. Examine axis ranges, baselines, scales, ordering, units, denominators, aggregation, uncertainty and missing groups where visible. Identify labels or color choices that could obscure meaning.
For each material issue, cite the visible feature, explain the likely misreading, and propose a minimal correction. Separate what can be seen from what requires the data or calculation logic; do not infer a truncated axis or missing observations without evidence.
Give a revised title and annotation plan that match the supported claim. End with the two highest-value checks before publication. Do not declare a chart statistically valid or accessible from an incomplete description.
Converts a natural-language data requirement plus a table schema into a syntactically correct SQL query for a named database, with its assumptions stated up front.