@pixerate/editor 0.223.0 → 0.223.1

package/dist/tools/skill-evals.d.cts

@@ -20,7 +20,7 @@ export interface SkillEvalCheck extends SkillEvalToolCall {
 }
 export interface SkillEval {
     prompt: string;
-    fixture: SpreadsheetEvalFixture | ImageEvalFixture | VectorEvalFixture | PaintEvalFixture | VideoEvalFixture;
+    fixture: SpreadsheetEvalFixture | ImageEvalFixture | VectorEvalFixture | PaintEvalFixture | VideoEvalFixture | ChartEvalFixture;
     checks: SkillEvalCheck[];
     solution: SkillEvalToolCall[];
 }
@@ -67,6 +67,11 @@ export interface VideoEvalFixture {
     /** Tool calls that build the starting project (settings, assets, clips, markers), run in order. */
     setup?: SkillEvalToolCall[];
 }
+export interface ChartEvalFixture {
+    editor: 'chart';
+    /** Tool calls that build the starting chart (`set_chart_data`, `update_chart`), run in order. */
+    setup?: SkillEvalToolCall[];
+}
 /** One eval file of a skill. */
 export interface SkillEvalFile {
     skill: string;

package/dist/tools/skill-evals.d.ts

@@ -20,7 +20,7 @@ export interface SkillEvalCheck extends SkillEvalToolCall {
 }
 export interface SkillEval {
     prompt: string;
-    fixture: SpreadsheetEvalFixture | ImageEvalFixture | VectorEvalFixture | PaintEvalFixture | VideoEvalFixture;
+    fixture: SpreadsheetEvalFixture | ImageEvalFixture | VectorEvalFixture | PaintEvalFixture | VideoEvalFixture | ChartEvalFixture;
     checks: SkillEvalCheck[];
     solution: SkillEvalToolCall[];
 }
@@ -67,6 +67,11 @@ export interface VideoEvalFixture {
     /** Tool calls that build the starting project (settings, assets, clips, markers), run in order. */
     setup?: SkillEvalToolCall[];
 }
+export interface ChartEvalFixture {
+    editor: 'chart';
+    /** Tool calls that build the starting chart (`set_chart_data`, `update_chart`), run in order. */
+    setup?: SkillEvalToolCall[];
+}
 /** One eval file of a skill. */
 export interface SkillEvalFile {
     skill: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pixerate/editor",
-  "version": "0.223.0",
+  "version": "0.223.1",
   "description": "UI-agnostic rich text and media editing core library",
   "author": "Pixerate",
   "license": "MIT",

package/skills/README.md

@@ -53,6 +53,8 @@ request like "clean up this export" finds it.
 | [`pixerate-video-social-cut`](pixerate-video-social-cut/SKILL.md) | Video (`pixerate-video-editor`) | Vertical or square reframes that fill the frame, the hook first, platform lengths, titles in the safe area. |
 | [`pixerate-video-colour-grade`](pixerate-video-colour-grade/SKILL.md) | Video (`pixerate-video-editor`) | Correct and match shots, then one look on an adjustment clip; LUTs at moderate strength with skin protected. |
 | [`pixerate-video-montage`](pixerate-video-montage/SKILL.md) | Video (`pixerate-video-editor`) | Selects on the beat, varied pacing, short transitions with handles, music under everything and a clean ending. |
+| [`pixerate-chart-choose-and-build`](pixerate-chart-choose-and-build/SKILL.md) | Chart (`pixerate-chart`) | From the question to the type, clean ordered data, honest axes, units and colour-blind-safe colours. |
+| [`pixerate-chart-annotate`](pixerate-chart-annotate/SKILL.md) | Chart (`pixerate-chart`) | A takeaway title, highlights, labelled targets and ranges, callouts and a source note, kept few. |
 | [`pixerate-talking-head-edit`](pixerate-talking-head-edit/SKILL.md) | Video (`pixerate-video-editor`) | Talking-head cleanup by transcript: fillers, long pauses and stutters found in one pass and cut as one plan reviewed before it applies. Owns the dialogue tools. |
 | [`pixerate-bgm-alignment`](pixerate-bgm-alignment/SKILL.md) | Video (`pixerate-video-editor`) | Background music: beats and cuts on the beat, ducking under speech, loudness in LUFS. Owns the music tools. |
 
@@ -117,7 +119,8 @@ same change.
   user's words), a `fixture` (the starting document: `{ "editor": "spreadsheet", "rows" }`,
   `{ "editor": "image", "width", "height", "background", "shapes" }` or `{ "editor":
   "vector", "width", "height", "setup" }` with commands that draw the starting art, 
-  `{ "editor": "paint", "width", "height", "setup" }` or `{ "editor": "video", "setup" }` with tool calls), `checks` (a read-only
+  `{ "editor": "paint", "width", "height", "setup" }` `{ "editor": "video", "setup" }` or `{ "editor":
+  "chart", "setup" }` with tool calls), `checks` (a read-only
   tool, or `run_command` with a read-only command such as `vector.list`, its `args`, what its result must match in `expect`, and `why`) and a `solution` (the
   tool calls an expert would make). The test proves each eval: some check fails on the fixture,
   and all pass after the solution. A model harness runs the same file with the model in place

package/skills/pixerate-chart/SKILL.md

@@ -44,6 +44,14 @@ Charts inside a rich-text document are not edited with these tools: use `insert_
 `list_document_charts` and `update_chart_in_document` from the `pixerate-rich-text` skill
 (a chart block goes in the prose, never inside a table row).
 
+## Workflow skills
+
+For these jobs, load the workflow skill too: it has the method, the checks between steps and
+the pitfalls, and uses the tools below.
+
+- `pixerate-chart-choose-and-build`: the type from the question, clean data, honest axes, units, colours.
+- `pixerate-chart-annotate`: a takeaway title, highlights, targets, ranges, callouts and the source.
+
 ## Working method
 
 0. **House style.** When the host has one (`list_toolsets` shows a `style` field on the chart

package/skills/pixerate-chart-annotate/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: pixerate-chart-annotate
+description: The annotation workflow in the Pixerate chart editor - turning a correct chart into one that makes its point - a title that states the takeaway, highlighting the categories or series that matter, reference lines for targets and averages, bands for ranges, callouts on the points that need explaining, units, a source note and a check that the annotations stay few and honest. Use when asked to make a chart tell a story, highlight or call out a point, show a target, goal, threshold, average or range, add a source or footnote, or make a chart ready for a report, slide or board pack, or when highlight_chart, add_chart_reference_line, add_chart_reference_band or set_chart_callout are available. Load with pixerate-chart, which lists every tool.
+metadata:
+  kind: workflow
+  reference: pixerate-chart
+---
+
+# Annotating a chart
+
+A chart for a report or a slide should say what it means, not leave the reader to find it. Once
+the type and data are right (`pixerate-chart-choose-and-build`), add the few marks that point at
+the message: a title that states it, a highlight on what matters, a reference line or band for
+the benchmark, a callout where something needs explaining, and a source note. Fewer is better:
+every annotation competes with the data.
+
+This skill is the method. `pixerate-chart` has the full tool reference.
+
+## Goal and quality bar
+
+- The title states the takeaway ("Q3 was our record quarter"), the subtitle the measure and
+  units if the axis does not.
+- What matters stands out (`highlight`), and everything else recedes.
+- Benchmarks are drawn, labelled, on the right axis: a target line, an average, a normal range.
+- At most one or two reference lines, one band and a couple of callouts.
+- The source is cited in `note`; units are stated.
+- The data is unchanged by annotating.
+
+## Inputs to confirm
+
+- **The message:** the one thing the reader should take away.
+- **Benchmarks:** targets, averages, thresholds or ranges, with their values and units.
+- **Source** of the data, and the audience (report, slide, dashboard).
+
+## Working method
+
+1. **Read.** `get_chart`: the type, categories, series, existing annotations and warnings.
+   **Check:** the chart is already the right type with clean data; if not, fix that first.
+2. **Title the takeaway.** `update_chart` `title` with the message, `subtitle` with the measure
+   and units.
+3. **Highlight.** `highlight_chart` with the category labels or series names that carry the
+   message; the rest dims.
+   **Check:** `get_chart` `spec.highlight`.
+4. **Benchmarks.** `add_chart_reference_line` for a target or average (`value`, `label`, `axis`);
+   `add_chart_reference_band` for a range (`from`, `to`, `label`).
+   **Check:** `spec.referenceLines` / `referenceBands` have the values and labels.
+5. **Callouts** for points that need a word (`set_chart_callout` on a series and category), such
+   as "Launch" or "Strike".
+6. **Source and units.** `update_chart` `note` ("Source: …"); the axis `format` or title for
+   units.
+7. **Review.** `render_chart`; remove any annotation that does not help the message.
+
+## Decision table
+
+| Want to say | Annotation |
+| --- | --- |
+| This one is the point | `highlight_chart` on it; title states it |
+| Above or below a goal | `add_chart_reference_line` at the target, labelled |
+| Inside or outside a normal range | `add_chart_reference_band`, labelled |
+| Compared with the average | Reference line at the average, labelled "Average" |
+| Something happened here | `set_chart_callout` on that point |
+| Where the numbers came from | `note` |
+| The trend, not the noise | `add_chart_trendline` (say what it models) |
+
+## Recipes
+
+**Record quarter.** `highlight_chart` `{ names: ["Q3"] }` → `update_chart` `{ title: "Q3 was our
+record quarter" }`.
+
+**Target.** `add_chart_reference_line` `{ value: 100000, label: "Target" }`.
+
+**Board-ready.** `update_chart` `{ note: "Source: internal CRM, 2026", yAxis: { format: { style:
+"currency", currency: "USD" } } }`.
+
+## Pitfalls
+
+- **Neutral titles** ("Quarterly revenue") make the reader do the work; state the finding when
+  the chart has one.
+- **Annotation clutter**: many lines, bands and callouts hide the data.
+- **Recolouring instead of highlighting**: changing one series' colour by hand breaks palettes
+  and colour checks; `highlight_chart` keeps them.
+- **Unlabelled lines**: a line without a label is a puzzle.
+- **Targets on the wrong axis**: put a reference line on the axis of the series it belongs to
+  (`axis: "y2"` for a secondary-axis series).
+- **Claims the data does not support**: the title must be true of the chart as drawn.
+
+## Tools used
+
+- `get_chart`, `render_chart`: read and look
+- `update_chart`: title, subtitle, note and axis formats
+- `highlight_chart`: what stands out
+- `add_chart_reference_line`, `update_chart_reference_line`, `remove_chart_reference_line`: targets and averages
+- `add_chart_reference_band`, `update_chart_reference_band`, `remove_chart_reference_band`: ranges
+- `set_chart_callout`: notes on points
+- `add_chart_trendline`: a fitted trend
+- `undo_chart`: take back a step

package/skills/pixerate-chart-annotate/evals/highlight-the-point.json

@@ -0,0 +1,78 @@
+{
+	"prompt": "Make this chart tell the reader that Q3 was our record quarter.",
+	"fixture": {
+		"editor": "chart",
+		"setup": [
+			{
+				"tool": "set_chart_data",
+				"args": {
+					"categories": [
+						"Q1",
+						"Q2",
+						"Q3",
+						"Q4"
+					],
+					"series": [
+						{
+							"name": "Revenue",
+							"values": [
+								82000,
+								91000,
+								118000,
+								96000
+							]
+						}
+					]
+				}
+			},
+			{
+				"tool": "update_chart",
+				"args": {
+					"type": "bar",
+					"title": "Quarterly revenue"
+				}
+			}
+		]
+	},
+	"checks": [
+		{
+			"why": "Q3 stands out",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"$expr": "v.highlight.includes('Q3') || v.series.some((s) => (s.callouts || [])[2]) || v.series.some((s) => s.pointColors && s.pointColors[2] && s.pointColors.filter(Boolean).length === 1)"
+				}
+			}
+		},
+		{
+			"why": "the title states the takeaway",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"title": {
+						"$match": [
+							"q3|third quarter",
+							"i"
+						]
+					}
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "highlight_chart",
+			"args": {
+				"names": [
+					"Q3"
+				]
+			}
+		},
+		{
+			"tool": "update_chart",
+			"args": {
+				"title": "Q3 was our record quarter"
+			}
+		}
+	]
+}

package/skills/pixerate-chart-annotate/evals/source-and-units.json

@@ -0,0 +1,76 @@
+{
+	"prompt": "Before this chart goes in the board report, add the source (internal CRM, 2026) and make the units clear.",
+	"fixture": {
+		"editor": "chart",
+		"setup": [
+			{
+				"tool": "set_chart_data",
+				"args": {
+					"categories": [
+						"Q1",
+						"Q2",
+						"Q3",
+						"Q4"
+					],
+					"series": [
+						{
+							"name": "Revenue",
+							"values": [
+								82000,
+								91000,
+								118000,
+								96000
+							]
+						}
+					]
+				}
+			},
+			{
+				"tool": "update_chart",
+				"args": {
+					"type": "bar",
+					"title": "Quarterly revenue"
+				}
+			}
+		]
+	},
+	"checks": [
+		{
+			"why": "a source note",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"note": {
+						"$match": [
+							"crm",
+							"i"
+						]
+					}
+				}
+			}
+		},
+		{
+			"why": "the units are stated (axis title, format or subtitle)",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"$expr": "/usd|\\$|dollar/i.test(v.yAxis.title + ' ' + v.subtitle) || v.yAxis.format.style === 'currency'"
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "update_chart",
+			"args": {
+				"note": "Source: internal CRM, 2026",
+				"yAxis": {
+					"format": {
+						"style": "currency",
+						"currency": "USD"
+					}
+				}
+			}
+		}
+	]
+}

package/skills/pixerate-chart-annotate/evals/target-line.json

@@ -0,0 +1,85 @@
+{
+	"prompt": "Show our quarterly target of 100,000 on the revenue chart so it's clear which quarters hit it.",
+	"fixture": {
+		"editor": "chart",
+		"setup": [
+			{
+				"tool": "set_chart_data",
+				"args": {
+					"categories": [
+						"Q1",
+						"Q2",
+						"Q3",
+						"Q4"
+					],
+					"series": [
+						{
+							"name": "Revenue",
+							"values": [
+								82000,
+								91000,
+								118000,
+								96000
+							]
+						}
+					]
+				}
+			},
+			{
+				"tool": "update_chart",
+				"args": {
+					"type": "bar",
+					"title": "Quarterly revenue"
+				}
+			}
+		]
+	},
+	"checks": [
+		{
+			"why": "a labelled reference line at 100,000 on the value axis",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"referenceLines": {
+						"$some": {
+							"value": 100000,
+							"label": {
+								"$match": [
+									"target",
+									"i"
+								]
+							}
+						}
+					}
+				}
+			}
+		},
+		{
+			"why": "the data is unchanged",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"series": [
+						{
+							"values": [
+								82000,
+								91000,
+								118000,
+								96000
+							]
+						}
+					]
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "add_chart_reference_line",
+			"args": {
+				"value": 100000,
+				"label": "Target"
+			}
+		}
+	]
+}

package/skills/pixerate-chart-choose-and-build/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: pixerate-chart-choose-and-build
+description: The chart building workflow in the Pixerate chart editor - starting from the question the chart answers, choosing the chart type for it (change over time, comparison, part of a whole, distribution, relationship, flow, geography), loading clean data in order, honest axes (bars from zero, log only for orders of magnitude), units and number formats, colours that colour-blind readers can tell apart, and checking before handing it over. Use when asked to make, build, create, choose, recommend or fix a chart or graph, visualise or plot data, pick the right chart, or make a chart clearer, more honest or accessible, or when recommend_chart, set_chart_data, update_chart or check_chart_colors are available. Load with pixerate-chart, which lists every tool.
+metadata:
+  kind: workflow
+  reference: pixerate-chart
+---
+
+# Choosing and building a chart
+
+A chart answers one question. Name the question first ("how did revenue change over the
+year?", "which region sells most?"), and the type, the order of the data, the axes and the
+title follow from it. Build in few calls: data in one, style in one, then check the warnings,
+the colours and the numbers before anyone sees it.
+
+This skill is the method. `pixerate-chart` has the full tool reference; for titles, highlights,
+reference lines and notes that make the point, see `pixerate-chart-annotate`.
+
+## Goal and quality bar
+
+- The type fits the question (see the decision table).
+- The data is in a meaningful order: time in calendar order, categories sorted by value unless
+  they have a natural order.
+- Axes are honest: bars and areas start at zero; a log scale only when values span orders of
+  magnitude, and labelled as such; a second axis only for a second unit.
+- Units are stated (axis title or number `format`); the title says what the chart shows.
+- Colours pass `check_chart_colors` (`ok: true`) and there are at most about seven series
+  colours.
+- `get_chart` `summary.warnings` and `issues` are empty.
+
+## Inputs to confirm
+
+- **The question** the chart must answer, and for whom (a report, a slide, a dashboard).
+- **The data**: where it is (pasted, CSV, a spreadsheet, an Office file) and its units.
+- **House style** if the host has one (`check_chart_style`).
+
+## Working method
+
+1. **Read.** `get_chart` (the spec, the data table, warnings); `list_file_charts` when the
+   data is in an open Office file.
+2. **Name the question and choose the type.** `recommend_chart` suggests types for the data;
+   check its suggestion against the question (see the table).
+   **Check:** you can say the question in one sentence and why this type answers it.
+3. **Load clean data in one call.** `set_chart_data` with categories in the right order and one
+   series per measure (or `import_chart_csv`); numbers as numbers, gaps as `null`.
+   **Check:** `get_chart` `spec.categories` and each series' `values` line up as intended.
+4. **Style in one call.** `update_chart` with `type`, `title`, axis `title` and `format`,
+   `legend`, `stacking`, `orientation`, `dataLabels`. Bars from zero (`yAxis.min` null or 0).
+   **Check:** `get_chart` spec; `summary.description` reads as the chart you meant.
+5. **Colours.** `check_chart_colors`; fix failing pairs with `update_chart_series` `color` (a
+   palette such as `#4269d0` / `#efb118` separates for most colour vision), or
+   `apply_chart_preset` for a tested palette.
+   **Check:** `check_chart_colors` `ok: true`.
+6. **Look.** `render_chart` once after the batch; fix anything that does not read.
+
+## Decision table
+
+| Question | Type |
+| --- | --- |
+| How did it change over time? | `line` (one or a few series), `area` for totals, columns for few periods |
+| Which is biggest? Compare categories | `bar`, horizontal for long labels, sorted by value |
+| Part of a whole (few parts) | `pie` or `donut` (at most five slices), or a stacked bar |
+| Part of a whole, nested | `treemap`, `sunburst` (`set_chart_tree`) |
+| How are values distributed? | `histogram`, `box` |
+| Do two measures relate? | `scatter`, `bubble` for a third measure |
+| Before and after per category | `slope` |
+| Contributions to a total | `waterfall` |
+| Flows between stages | `sankey` (`set_chart_links`), `funnel` for one path |
+| Survey answers | `likert` |
+| By region on a map | `choropleth` |
+
+## Recipes
+
+**Trend over time.** `set_chart_data` with categories in calendar order → `update_chart`
+`{ type: "line", title, yAxis: { title: "Revenue (USD thousands)" } }` → `get_chart`.
+
+**Colour-blind fix.** `check_chart_colors` → `update_chart_series` `color` on the clashing series
+→ `check_chart_colors` again.
+
+**Honest bars.** `update_chart` `{ yAxis: { min: 0 } }`; when small differences matter, show the
+differences themselves (a bar of the change) or a dot plot rather than a cut axis.
+
+## Pitfalls
+
+- **Truncated bar axes** exaggerate differences; bars start at zero.
+- **Pie charts with many or similar slices** cannot be read; use a sorted bar.
+- **Red and green** as the only distinction fail for the most common colour-vision deficiency.
+- **Unsorted categories** without a natural order hide the ranking.
+- **Mixed units on one axis**, or a second axis for the same unit, mislead.
+- **Missing units** leave the reader guessing; put them in the axis title or format.
+
+## Tools used
+
+- `get_chart`, `render_chart`: the spec, data table, warnings, and a picture
+- `recommend_chart`: types that suit the data
+- `set_chart_data`, `import_chart_csv`, `transpose_chart`: load the data in order
+- `update_chart`, `update_chart_series`, `apply_chart_preset`: type, titles, axes, formats and colours
+- `check_chart_colors`, `check_chart_style`: colour-blind and house-style checks
+- `list_file_charts`, `load_file_chart`: data from open Office files
+- `undo_chart`: take back a step

package/skills/pixerate-chart-choose-and-build/evals/colour-blind-safe.json

@@ -0,0 +1,113 @@
+{
+	"prompt": "Some of our readers are colour-blind and can't tell the two years apart in this chart. Fix the colours without changing the data.",
+	"fixture": {
+		"editor": "chart",
+		"setup": [
+			{
+				"tool": "set_chart_data",
+				"args": {
+					"categories": [
+						"North",
+						"South",
+						"East",
+						"West"
+					],
+					"series": [
+						{
+							"name": "2025",
+							"values": [
+								12,
+								15,
+								9,
+								11
+							],
+							"color": "#d62728"
+						},
+						{
+							"name": "2026",
+							"values": [
+								14,
+								13,
+								12,
+								15
+							],
+							"color": "#2ca02c"
+						}
+					]
+				}
+			},
+			{
+				"tool": "update_chart",
+				"args": {
+					"type": "bar",
+					"title": "Sales by region"
+				}
+			}
+		]
+	},
+	"checks": [
+		{
+			"why": "the colours pass the colour-blind check",
+			"tool": "check_chart_colors",
+			"expect": {
+				"ok": true
+			}
+		},
+		{
+			"why": "the data is unchanged",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"categories": [
+						"North",
+						"South",
+						"East",
+						"West"
+					],
+					"series": [
+						{
+							"name": "2025",
+							"values": [
+								12,
+								15,
+								9,
+								11
+							]
+						},
+						{
+							"name": "2026",
+							"values": [
+								14,
+								13,
+								12,
+								15
+							]
+						}
+					]
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "check_chart_colors"
+		},
+		{
+			"tool": "update_chart_series",
+			"args": {
+				"series": "2025",
+				"color": "#4269d0"
+			}
+		},
+		{
+			"tool": "update_chart_series",
+			"args": {
+				"series": "2026",
+				"color": "#efb118"
+			}
+		},
+		{
+			"tool": "check_chart_colors"
+		}
+	]
+}

package/skills/pixerate-chart-choose-and-build/evals/honest-baseline.json

@@ -0,0 +1,81 @@
+{
+	"prompt": "This bar chart makes the differences between teams look huge, but they're small. Make it honest.",
+	"fixture": {
+		"editor": "chart",
+		"setup": [
+			{
+				"tool": "set_chart_data",
+				"args": {
+					"categories": [
+						"Team A",
+						"Team B",
+						"Team C",
+						"Team D"
+					],
+					"series": [
+						{
+							"name": "Satisfaction (%)",
+							"values": [
+								92,
+								95,
+								94,
+								97
+							]
+						}
+					]
+				}
+			},
+			{
+				"tool": "update_chart",
+				"args": {
+					"type": "bar",
+					"title": "Satisfaction by team",
+					"yAxis": {
+						"min": 90,
+						"max": 98
+					}
+				}
+			}
+		]
+	},
+	"checks": [
+		{
+			"why": "bars start at zero (or the chart is no longer bars)",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"$expr": "v.type !== 'bar' || v.yAxis.min === null || v.yAxis.min === 0"
+				}
+			}
+		},
+		{
+			"why": "the data is unchanged",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"series": [
+						{
+							"values": [
+								92,
+								95,
+								94,
+								97
+							]
+						}
+					]
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "update_chart",
+			"args": {
+				"yAxis": {
+					"min": 0,
+					"max": 100
+				}
+			}
+		}
+	]
+}

package/skills/pixerate-chart-choose-and-build/evals/trend-over-time.json

@@ -0,0 +1,175 @@
+{
+	"prompt": "This is our 2026 monthly revenue in thousands of US dollars, pasted in a muddle. Make a chart that shows how revenue changed over the year.",
+	"fixture": {
+		"editor": "chart",
+		"setup": [
+			{
+				"tool": "set_chart_data",
+				"args": {
+					"categories": [
+						"Mar",
+						"Jan",
+						"Feb",
+						"Jun",
+						"Apr",
+						"May",
+						"Sep",
+						"Jul",
+						"Aug",
+						"Dec",
+						"Oct",
+						"Nov"
+					],
+					"series": [
+						{
+							"name": "Revenue",
+							"values": [
+								51,
+								42,
+								45,
+								61,
+								48,
+								55,
+								70,
+								58,
+								64,
+								82,
+								68,
+								75
+							]
+						}
+					]
+				}
+			},
+			{
+				"tool": "update_chart",
+				"args": {
+					"type": "pie"
+				}
+			}
+		]
+	},
+	"checks": [
+		{
+			"why": "a line or area chart for change over time",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"type": {
+						"$in": [
+							"line",
+							"area"
+						]
+					}
+				}
+			}
+		},
+		{
+			"why": "months in calendar order, with their own values",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"categories": [
+						"Jan",
+						"Feb",
+						"Mar",
+						"Apr",
+						"May",
+						"Jun",
+						"Jul",
+						"Aug",
+						"Sep",
+						"Oct",
+						"Nov",
+						"Dec"
+					],
+					"series": [
+						{
+							"values": [
+								42,
+								45,
+								51,
+								48,
+								55,
+								61,
+								58,
+								64,
+								70,
+								68,
+								75,
+								82
+							]
+						}
+					]
+				}
+			}
+		},
+		{
+			"why": "a title and a value axis that says the unit",
+			"tool": "get_chart",
+			"expect": {
+				"spec": {
+					"title": {
+						"$match": "\\S"
+					},
+					"yAxis": {
+						"$expr": "/usd|\\$|dollar/i.test(v.title) || v.format.style === 'currency' || /\\$/.test(v.format.prefix || '')"
+					}
+				}
+			}
+		}
+	],
+	"solution": [
+		{
+			"tool": "get_chart"
+		},
+		{
+			"tool": "set_chart_data",
+			"args": {
+				"categories": [
+					"Jan",
+					"Feb",
+					"Mar",
+					"Apr",
+					"May",
+					"Jun",
+					"Jul",
+					"Aug",
+					"Sep",
+					"Oct",
+					"Nov",
+					"Dec"
+				],
+				"series": [
+					{
+						"name": "Revenue",
+						"values": [
+							42,
+							45,
+							51,
+							48,
+							55,
+							61,
+							58,
+							64,
+							70,
+							68,
+							75,
+							82
+						]
+					}
+				]
+			}
+		},
+		{
+			"tool": "update_chart",
+			"args": {
+				"type": "line",
+				"title": "Revenue grew through 2026",
+				"yAxis": {
+					"title": "Revenue (USD thousands)"
+				}
+			}
+		}
+	]
+}