[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AXHW6ENKKHP24X54B9KT4":3,"skill-same:01M69AXHW6ENKKHP24X54B9KT4":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M69AXHW6ENKKHP24X54B9KT4","flint-board-author",null,"Use when: several Flint charts should be read together in one view: a dashboard, KPI tiles over a trend, a side-by-side comparison, an overview with its detail; or a board on screen should change (add, retitle, resize, reconnect a chart). Produce one board spec whose headline, chart choice, layout and connected fields are decided, check and refine it with validate_board, then put it on screen once with show.","microsoft\u002Fflint-chart","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AXB6SP1R3N8FK0Y1CNSDW",4577,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fflint-chart\u002Fblob\u002Fmain\u002Fagent-skills\u002Fflint-board-author\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,30,31,32,33],"flint board author","spec","dashboard","change","validate","2026-11-10 10:12:30",false,"---\nname: flint-board-author\ndescription: \"Use when: several Flint charts should be read together in one view: a dashboard, KPI tiles over a trend, a side-by-side comparison, an overview with its detail; or a board on screen should change (add, retitle, resize, reconnect a chart). Produce one board spec whose headline, chart choice, layout and connected fields are decided, check and refine it with validate_board, then put it on screen once with show.\"\n---\n\n# flint-board: several charts, one view\n\nA board holds several Flint charts under one headline. The agent writes it as\none board spec, checks it with `validate_board`, which draws nothing, and puts\nit on screen with `show({ \"board\": … })`, which opens a new card below the\nconversation's latest message. The server keeps nothing between calls: the spec\nin the conversation is the board. So call `show` once a turn, after the board\nis right; to change it later, change the spec and call `show` again.\n\nEach chart on a board is a full chart spec (`flint-chart-author`), plus an\n`id` and a `layout`. This skill covers what a board adds: the headline, which\ncharts, where they sit, how they connect, and how they look as one piece.\n\nWork through the steps in order. A board is ready to show when its latest\nreport shows no `✗` and its `Review:` section is empty or says only that a\ncolour field is shared.\n\n## Step 1 — write the headline\n\nThe board's `title` is what the reader takes away, or what the board is for,\nin one line. Its `subtitle` is the deck: the data, its scope, period and\nunits. `source` is the footer: where the data comes from and when.\n\n```\ntitle:    \"Europe carried the third-quarter recovery\"\nsubtitle: \"Monthly revenue by region and product line, Jan–Sep 2025, $m\"\nsource:   \"Source: finance ledger, closed books to 30 Sep 2025\"\n```\n\nA monitoring board with no single finding names its purpose instead:\n`\"Operations at a glance\"`. The card draws the title largest, so it is the\nfirst thing read; every board gets one.\n\n## Step 2 — choose the charts\n\nStart from the questions the reader brings, one chart per question, and keep\nthe board to the charts that answer them: three to five KPI tiles and up to\nsix charts. More than that is two boards.\n\n| The reader asks | Chart |\n|---|---|\n| How are we doing on the numbers we steer by? | `KPI Card` per number, with `goal` when there is a target |\n| How did it move over time? | `Line Chart` (few series), `Area Chart` (parts of a total) |\n| Which is largest, how do they rank? | `Bar Chart` sorted by value, `Bar Table` for many rows with labels |\n| Which records are behind it? | `Table`: the rows as given, one column per field, `encodings: {}` |\n| What is it made of? | `Stacked Bar Chart`, or `Pie Chart` with `innerRadius` for up to five parts |\n| How do two measures relate? | `Scatter Plot` |\n| Where? | `Choropleth`, `Map` |\n| How is it spread? | `Histogram`, `Boxplot` |\n| Each series' trend at a glance | `Sparkline` |\n\nPick the lead chart, the one the headline is about, and put it first after the\nKPI tiles. The charts after it explain it: a breakdown, a ranking, a relation.\n\nGive each chart its own data, aggregated to what it draws: a bar, a slice or\na cell is one row. Rows that repeat a category (monthly rows under a by-product\nbar) draw as a stack of thin slices; sum them first, or set the measure's\n`aggregate: \"sum\"`. A KPI tile takes\none row: `{ metric, value, goal }`. It draws progress only when `value` and\n`goal` are both numbers. Pass raw numbers and declare the value field's unit\nin `semantic_types`: the tile prints `{ \"semanticType\": \"Amount\", \"unit\": \"USD\" }`\nas `$1.18M`, a `Percentage` of 0.378 as `37.8%`, and compacts amounts and\ncounts from 10,000 up. A value already scaled says so in `metric`\n(`\"Revenue, $m\"`) and is not compacted again. A string `value` prints as given.\n\n## Step 3 — give each chart a heading\n\nEach chart draws its own `title` and `subtitle` in its theme, as on its own\ncard. Write the title as the chart's finding, one line at half width (a\nwrapped title pushes its plot down), and the subtitle as its units:\n\n```\ntitle:    \"Europe climbed every month after the April dip\"\nsubtitle: \"Revenue by region, $m\"\n```\n\nA `KPI Card` names itself with its `metric` field and needs no title.\n\n## Step 4 — place them\n\nThe board is a grid of `columns` (default 2 once it has two charts that are\nnot KPI tiles). Charts fill rows in the order given:\n\n- **KPI Cards in a row** share one row, up to four; a short row spreads its tiles.\n- **`layout.span`** is how many columns a chart takes. Time series, maps and\n  Gantt charts take the full row by default; everything else takes one column.\n  A row left short stretches to the full width.\n- **`layout.height`** is `compact` (~130 px), `standard` (~280 px, the default)\n  or `tall` (~420 px). A row takes its tallest chart's height, so the plots of\n  a row line up. A time series alone in its row defaults to `tall`: Flint\n  banks a line toward readable slopes, and the height is what lets it spread\n  across the width.\n\n| Shape | Layout |\n|---|---|\n| KPI row, lead trend, two explaining charts | tiles; trend (full row); two charts (one column each) |\n| Side-by-side comparison | `columns: 2`, both charts `span: 1`, same height |\n| Overview with its detail | detail `span: 2, height: tall`; overview strip below it `height: compact` |\n| Many small series | one `Sparkline` chart, `height: compact` or `standard` |\n\nOn a narrow card each chart takes its own row; the layout needs no second version.\n\n**`view: \"table\"`** on a chart opens its cell on the table of the rows the chart\ndraws; the reader can switch it back. Use it when the numbers matter more than\nthe shape.\nA `Table` is a table either way.\n\n## Step 5 — connect them\n\nConnect the charts by the fields they share, not chart by chart:\n\n```json\n\"link_spec\": { \"fields\": [\"product\", \"region\"] }\n```\n\nThe board holds one selection that every chart shares, a part per field: a\nclick on Asia sets `region` to Asia, a brush over March to June then adds\n`month` from March to June, and every chart shows the marks that meet both\nparts on the fields it carries; a chart that carries neither stays as drawn.\nA new selection on a field the board already holds replaces that part. A click\non nothing in any chart, Escape, or the selection chip under the headline\nclears the whole selection everywhere.\n\nWhat a selection sets comes from the interaction that made it: a click on a\nmark sets every connected field the mark carries, a series or group focus its\ngroup field, a brush its axis field as a range, an axis highlight that axis's\nfield. A hover interaction (`hover-group-focus`, or `axis-highlight` with\n`event: \"hover\"`) previews its part over the selection for as long as the\npointer stays.\n\nConnect on the fields the reader thinks in: categories with about a dozen\nvalues or fewer, and the dimension the board is about. A chart takes part as\nfar as it can:\n\n- **It receives a field** when its marks carry it. Marks carry the fields the\n  chart encodes; when a chart shows the field nowhere else, encode it on\n  `detail` (`encodings.detail: \"product\"`).\n- **It sends** when it also has an interaction that selects, in its\n  `interaction_spec`; pick the one whose subject is what the reader will ask\n  about:\n\n  | Chart | Interaction |\n  |---|---|\n  | Bar, Stacked Bar, Pie, Heatmap | `click-highlight` |\n  | Line | `click-group-focus` (a series), `brush-x` (a period), `hover-group-focus` (a series, on hover) |\n  | Scatter Plot | `select` (drag a region) |\n\n- **`charts`** sets a chart apart: `{ \"trend\": { \"receive\": false } }` keeps an\n  overview as drawn while it still sends; `send: false` keeps a chart's own\n  selections to itself.\n\nThe report's `Links:` section says what each chart sends and receives, and\nwhy a field is left out.\n\nColour does the quiet linking: charts that colour by the same field (on\n`color`, or `group` on a grouped bar chart) get one value order, so a value\nkeeps one colour across the board. Colour each chart\nby the same field as the others when it shows the same categories, and give\nit the same set of values, since a chart missing a value shifts the colours\nafter it.\n\n## Step 6 — theme the board once\n\nSet `theme_spec` on the board, not on the charts. Every chart takes it and\ndraws its own furniture (the Economist's red tab); the board's headline and\nfooter take its paper, ink and fonts, with the furniture above the headline.\nPick it with `list_themes` as for one chart.\n\n## Step 7 — read the report and refine\n\n`validate_board` returns the board as the model must judge it, and `show`\nreturns the same report:\n\n- `Layout:` the rows as the card draws them. Check that the lead chart sits\n  where the headline points and no row holds an orphan.\n- `## \u003Cid>` per chart: its encodings and each update op, `✓` or `✗`.\n- `Links:` what each chart sends and receives, `✓`, or `✗` when it joins no field, with the fix.\n- `Review:` what the board should still fix: a missing headline, deck or chart\n  title, too many tiles or charts, themes set per chart.\n\nFix each `✗` and each review note in the spec, check it again if the fix was\nlarge, then call `show` once with the same spec. A chart with errors is left\noff the report's board, and `show` draws nothing until every chart is valid.\n\nWhat the reader then does on the card reaches the model with their next\nmessage: selections and link emphasis, one section per chart. The reader's\nchanges live on that card only, and the context says how to keep each one in\nthe next `show`:\n\n- **A theme** picked in the bar applies to every chart. To keep it, pass that\n  `theme_spec` on the board and leave it out of the charts.\n- **An arrangement** made with **Edit layout** (moving, swapping, resizing\n  charts on a 12-column grid). To keep it, pass the `grid` the context gives.\n  `Layout:` then reads \"Arranged on a 12-column grid\". A chart added to the\n  spec takes a place below the rest and a chart left out drops its place;\n  leave `grid` out to lay the board out in rows again, only when the user asks\n  for a new layout.\n\nLeave out what the user asked to change, and keep the rest: a `show` without\nthem gives the reader back the agent's theme and rows.\n\n## Worked example\n\nThe board spec, passed as it is to `validate_board`, then as `board` to `show`:\n\n```json\n{\n  \"title\": \"Europe carried the third-quarter recovery\",\n  \"subtitle\": \"Monthly revenue by region and product line, Jan–Sep 2025, $m\",\n  \"source\": \"Source: finance ledger, closed books to 30 Sep 2025\",\n  \"theme_spec\": \"economist\",\n  \"charts\": [\n    { \"id\": \"k-revenue\", \"data\": { \"values\": [{ \"metric\": \"Revenue, Q3 ($m)\", \"value\": 38.6, \"goal\": 36 }] },\n      \"chart_spec\": { \"chartType\": \"KPI Card\", \"encodings\": { \"metric\": \"metric\", \"value\": \"value\", \"goal\": \"goal\" } } },\n    { \"id\": \"k-margin\", \"data\": { \"values\": [{ \"metric\": \"Gross margin, %\", \"value\": 37, \"goal\": 40 }] },\n      \"chart_spec\": { \"chartType\": \"KPI Card\", \"encodings\": { \"metric\": \"metric\", \"value\": \"value\", \"goal\": \"goal\" } } },\n    { \"id\": \"trend\", \"data\": { \"url\": \".\u002Fflint-data\u002Frevenue-by-month.csv\" },\n      \"semantic_types\": { \"month\": \"YearMonth\", \"region\": \"Category\", \"revenue\": \"Amount\" },\n      \"chart_spec\": { \"chartType\": \"Line Chart\", \"title\": \"Europe climbed every month after the April dip\",\n        \"subtitle\": \"Revenue by region, $m\", \"encodings\": { \"x\": \"month\", \"y\": \"revenue\", \"color\": \"region\" } },\n      \"interaction_spec\": { \"interactions\": [{ \"type\": \"click-group-focus\" }] } },\n    { \"id\": \"by-product\", \"data\": { \"url\": \".\u002Fflint-data\u002Frevenue-by-product.csv\" },\n      \"semantic_types\": { \"product\": \"Category\", \"region\": \"Category\", \"revenue\": \"Amount\" },\n      \"chart_spec\": { \"chartType\": \"Bar Chart\", \"title\": \"Analytics leads in every region\",\n        \"subtitle\": \"Revenue by product, Jan–Sep, $m\", \"encodings\": { \"y\": \"product\", \"x\": \"revenue\", \"color\": \"region\" } },\n      \"interaction_spec\": { \"interactions\": [{ \"type\": \"click-highlight\" }] } },\n    { \"id\": \"margin\", \"data\": { \"url\": \".\u002Fflint-data\u002Frevenue-by-product.csv\" },\n      \"semantic_types\": { \"product\": \"Category\", \"region\": \"Category\", \"revenue\": \"Amount\", \"margin\": \"Percentage\" },\n      \"chart_spec\": { \"chartType\": \"Scatter Plot\", \"title\": \"Security earns the widest margin\",\n        \"subtitle\": \"Revenue vs gross margin, by product and region\",\n        \"encodings\": { \"x\": \"revenue\", \"y\": \"margin\", \"color\": \"region\", \"detail\": \"product\" } } }\n  ],\n  \"link_spec\": { \"fields\": [\"product\", \"region\"] }\n}\n```\n\nRows: two KPI tiles; the trend across the row, tall; the bar chart and the\nscatter side by side. A click on one segment of a product's bar lights that\nproduct's points on the scatter and the segment's region on the trend; a click\non a region's line lights that region on the bars and the scatter.\n\n## Checklist\n\n- [ ] `title` says the finding or the purpose; `subtitle` says data, scope, period, units; `source` is set.\n- [ ] Three to five KPI tiles at most, up to six charts, the lead chart first after the tiles.\n- [ ] Every chart but a KPI tile has a one-line `title` and a units `subtitle`.\n- [ ] `layout` set where the default is wrong: the lead chart wide, a comparison at equal spans and heights.\n- [ ] `link_spec.fields` names the shared dimensions; each chart that should take part encodes them and, to send, has the interaction whose subject the reader asks about.\n- [ ] `theme_spec` on the board only.\n- [ ] `validate_board` reports no `✗` and no review note left but the shared colour field.\n- [ ] In a later turn: the reader's theme and `grid` from the context are kept unless the user asked to change them.\n","# flint-board: several charts, one view\n\nA board holds several Flint charts under one headline. The agent writes it as\none board spec, checks it with `validate_board`, which draws nothing, and puts\nit on screen with `show({ \"board\": … })`, which opens a new card below the\nconversation's latest message. The server keeps nothing between calls: the spec\nin the conversation is the board. So call `show` once a turn, after the board\nis right; to change it later, change the spec and call `show` again.\n\nEach chart on a board is a full chart spec (`flint-chart-author`), plus an\n`id` and a `layout`. This skill covers what a board adds: the headline, which\ncharts, where they sit, how they connect, and how they look as one piece.\n\nWork through the steps in order. A board is ready to show when its latest\nreport shows no `✗` and its `Review:` section is empty or says only that a\ncolour field is shared.\n\n## Step 1 — write the headline\n\nThe board's `title` is what the reader takes away, or what the board is for,\nin one line. Its `subtitle` is the deck: the data, its scope, period and\nunits. `source` is the footer: where the data comes from and when.\n\n```\ntitle:    \"Europe carried the third-quarter recovery\"\nsubtitle: \"Monthly revenue by region and product line, Jan–Sep 2025, $m\"\nsource:   \"Source: finance ledger, closed books to 30 Sep 2025\"\n```\n\nA monitoring board with no single finding names its purpose instead:\n`\"Operations at a glance\"`. The card draws the title largest, so it is the\nfirst thing read; every board gets one.\n\n## Step 2 — choose the charts\n\nStart from the questions the reader brings, one chart per question, and keep\nthe board to the charts that answer them: three to five KPI tiles and up to\nsix charts. More than that is two boards.\n\n| The reader asks | Chart |\n|---|---|\n| How are we doing on the numbers we steer by? | `KPI Card` per number, with `goal` when there is a target |\n| How did it move over time? | `Line Chart` (few series), `Area Chart` (parts of a total) |\n| Which is largest, how do they rank? | `Bar Chart` sorted by value, `Bar Table` for many rows with labels |\n| Which records are behind it? | `Table`: the rows as given, one column per field, `encodings: {}` |\n| What is it made of? | `Stacked Bar Chart`, or `Pie Chart` with `innerRadius` for up to five parts |\n| How do two measures relate? | `Scatter Plot` |\n| Where? | `Choropleth`, `Map` |\n| How is it spread? | `Histogram`, `Boxplot` |\n| Each series' trend at a glance | `Sparkline` |\n\nPick the lead chart, the one the headline is about, and put it first after the\nKPI tiles. The charts after it explain it: a breakdown, a ranking, a relation.\n\nGive each chart its own data, aggregated to what it draws: a bar, a slice or\na cell is one row. Rows that repeat a category (monthly rows under a by-product\nbar) draw as a stack of thin slices; sum them first, or set the measure's\n`aggregate: \"sum\"`. A KPI tile takes\none row: `{ metric, value, goal }`. It draws progress only when `value` and\n`goal` are both numbers. Pass raw numbers and declare the value field's unit\nin `semantic_types`: the tile prints `{ \"semanticType\": \"Amount\", \"unit\": \"USD\" }`\nas `$1.18M`, a `Percentage` of 0.378 as `37.8%`, and compacts amounts and\ncounts from 10,000 up. A value already scaled says so in `metric`\n(`\"Revenue, $m\"`) and is not compacted again. A string `value` prints as given.\n\n## Step 3 — give each chart a heading\n\nEach chart draws its own `title` and `subtitle` in its theme, as on its own\ncard. Write the title as the chart's finding, one line at half width (a\nwrapped title pushes its plot down), and the subtitle as its units:\n\n```\ntitle:    \"Europe climbed every month after the April dip\"\nsubtitle: \"Revenue by region, $m\"\n```\n\nA `KPI Card` names itself with its `metric` field and needs no title.\n\n## Step 4 — place them\n\nThe board is a grid of `columns` (default 2 once it has two charts that are\nnot KPI tiles). Charts fill rows in the order given:\n\n- **KPI Cards in a row** share one row, up to four; a short row spreads its tiles.\n- **`layout.span`** is how many columns a chart takes. Time series, maps and\n  Gantt charts take the full row by default; everything else takes one column.\n  A row left short stretches to the full width.\n- **`layout.height`** is `compact` (~130 px), `standard` (~280 px, the default)\n  or `tall` (~420 px). A row takes its tallest chart's height, so the plots of\n  a row line up. A time series alone in its row defaults to `tall`: Flint\n  banks a line toward readable slopes, and the height is what lets it spread\n  across the width.\n\n| Shape | Layout |\n|---|---|\n| KPI row, lead trend, two explaining charts | tiles; trend (full row); two charts (one column each) |\n| Side-by-side comparison | `columns: 2`, both charts `span: 1`, same height |\n| Overview with its detail | detail `span: 2, height: tall`; overview strip below it `height: compact` |\n| Many small series | one `Sparkline` chart, `height: compact` or `standard` |\n\nOn a narrow card each chart takes its own row; the layout needs no second version.\n\n**`view: \"table\"`** on a chart opens its cell on the table of the rows the chart\ndraws; the reader can switch it back. Use it when the numbers matter more than\nthe shape.\nA `Table` is a table either way.\n\n## Step 5 — connect them\n\nConnect the charts by the fields they share, not chart by chart:\n\n```json\n\"link_spec\": { \"fields\": [\"product\", \"region\"] }\n```\n\nThe board holds one selection that every chart shares, a part per field: a\nclick on Asia sets `region` to Asia, a brush over March to June then adds\n`month` from March to June, and every chart shows the marks that meet both\nparts on the fields it carries; a chart that carries neither stays as drawn.\nA new selection on a field the board already holds replaces that part. A click\non nothing in any chart, Escape, or the selection chip under the headline\nclears the whole selection everywhere.\n\nWhat a selection sets comes from the interaction that made it: a click on a\nmark sets every connected field the mark carries, a series or group focus its\ngroup field, a brush its axis field as a range, an axis highlight that axis's\nfield. A hover interaction (`hover-group-focus`, or `axis-highlight` with\n`event: \"hover\"`) previews its part over the selection for as long as the\npointer stays.\n\nConnect on the fields the reader thinks in: categories with about a dozen\nvalues or fewer, and the dimension the board is about. A chart takes part as\nfar as it can:\n\n- **It receives a field** when its marks carry it. Marks carry the fields the\n  chart encodes; when a chart shows the field nowhere else, encode it on\n  `detail` (`encodings.detail: \"product\"`).\n- **It sends** when it also has an interaction that selects, in its\n  `interaction_spec`; pick the one whose subject is what the reader will ask\n  about:\n\n  | Chart | Interaction |\n  |---|---|\n  | Bar, Stacked Bar, Pie, Heatmap | `click-highlight` |\n  | Line | `click-group-focus` (a series), `brush-x` (a period), `hover-group-focus` (a series, on hover) |\n  | Scatter Plot | `select` (drag a region) |\n\n- **`charts`** sets a chart apart: `{ \"trend\": { \"receive\": false } }` keeps an\n  overview as drawn while it still sends; `send: false` keeps a chart's own\n  selections to itself.\n\nThe report's `Links:` section says what each chart sends and receives, and\nwhy a field is left out.\n\nColour does the quiet linking: charts that colour by the same field (on\n`color`, or `group` on a grouped bar chart) get one value order, so a value\nkeeps one colour across the board. Colour each chart\nby the same field as the others when it shows the same categories, and give\nit the same set of values, since a chart missing a value shifts the colours\nafter it.\n\n## Step 6 — theme the board once\n\nSet `theme_spec` on the board, not on the charts. Every chart takes it and\ndraws its own furniture (the Economist's red tab); the board's headline and\nfooter take its paper, ink and fonts, with the furniture above the headline.\nPick it with `list_themes` as for one chart.\n\n## Step 7 — read the report and refine\n\n`validate_board` returns the board as the model must judge it, and `show`\nreturns the same report:\n\n- `Layout:` the rows as the card draws them. Check that the lead chart sits\n  where the headline points and no row holds an orphan.\n- `## \u003Cid>` per chart: its encodings and each update op, `✓` or `✗`.\n- `Links:` what each chart sends and receives, `✓`, or `✗` when it joins no field, with the fix.\n- `Review:` what the board should still fix: a missing headline, deck or chart\n  title, too many tiles or charts, themes set per chart.\n\nFix each `✗` and each review note in the spec, check it again if the fix was\nlarge, then call `show` once with the same spec. A chart with errors is left\noff the report's board, and `show` draws nothing until every chart is valid.\n\nWhat the reader then does on the card reaches the model with their next\nmessage: selections and link emphasis, one section per chart. The reader's\nchanges live on that card only, and the context says how to keep each one in\nthe next `show`:\n\n- **A theme** picked in the bar applies to every chart. To keep it, pass that\n  `theme_spec` on the board and leave it out of the charts.\n- **An arrangement** made with **Edit layout** (moving, swapping, resizing\n  charts on a 12-column grid). To keep it, pass the `grid` the context gives.\n  `Layout:` then reads \"Arranged on a 12-column grid\". A chart added to the\n  spec takes a place below the rest and a chart left out drops its place;\n  leave `grid` out to lay the board out in rows again, only when the user asks\n  for a new layout.\n\nLeave out what the user asked to change, and keep the rest: a `show` without\nthem gives the reader back the agent's theme and rows.\n\n## Worked example\n\nThe board spec, passed as it is to `validate_board`, then as `board` to `show`:\n\n```json\n{\n  \"title\": \"Europe carried the third-quarter recovery\",\n  \"subtitle\": \"Monthly revenue by region and product line, Jan–Sep 2025, $m\",\n  \"source\": \"Source: finance ledger, closed books to 30 Sep 2025\",\n  \"theme_spec\": \"economist\",\n  \"charts\": [\n    { \"id\": \"k-revenue\", \"data\": { \"values\": [{ \"metric\": \"Revenue, Q3 ($m)\", \"value\": 38.6, \"goal\": 36 }] },\n      \"chart_spec\": { \"chartType\": \"KPI Card\", \"encodings\": { \"metric\": \"metric\", \"value\": \"value\", \"goal\": \"goal\" } } },\n    { \"id\": \"k-margin\", \"data\": { \"values\": [{ \"metric\": \"Gross margin, %\", \"value\": 37, \"goal\": 40 }] },\n      \"chart_spec\": { \"chartType\": \"KPI Card\", \"encodings\": { \"metric\": \"metric\", \"value\": \"value\", \"goal\": \"goal\" } } },\n    { \"id\": \"trend\", \"data\": { \"url\": \".\u002Fflint-data\u002Frevenue-by-month.csv\" },\n      \"semantic_types\": { \"month\": \"YearMonth\", \"region\": \"Category\", \"revenue\": \"Amount\" },\n      \"chart_spec\": { \"chartType\": \"Line Chart\", \"title\": \"Europe climbed every month after the April dip\",\n        \"subtitle\": \"Revenue by region, $m\", \"encodings\": { \"x\": \"month\", \"y\": \"revenue\", \"color\": \"region\" } },\n      \"interaction_spec\": { \"interactions\": [{ \"type\": \"click-group-focus\" }] } },\n    { \"id\": \"by-product\", \"data\": { \"url\": \".\u002Fflint-data\u002Frevenue-by-product.csv\" },\n      \"semantic_types\": { \"product\": \"Category\", \"region\": \"Category\", \"revenue\": \"Amount\" },\n      \"chart_spec\": { \"chartType\": \"Bar Chart\", \"title\": \"Analytics leads in every region\",\n        \"subtitle\": \"Revenue by product, Jan–Sep, $m\", \"encodings\": { \"y\": \"product\", \"x\": \"revenue\", \"color\": \"region\" } },\n      \"interaction_spec\": { \"interactions\": [{ \"type\": \"click-highlight\" }] } },\n    { \"id\": \"margin\", \"data\": { \"url\": \".\u002Fflint-data\u002Frevenue-by-product.csv\" },\n      \"semantic_types\": { \"product\": \"Category\", \"region\": \"Category\", \"revenue\": \"Amount\", \"margin\": \"Percentage\" },\n      \"chart_spec\": { \"chartType\": \"Scatter Plot\", \"title\": \"Security earns the widest margin\",\n        \"subtitle\": \"Revenue vs gross margin, by product and region\",\n        \"encodings\": { \"x\": \"revenue\", \"y\": \"margin\", \"color\": \"region\", \"detail\": \"product\" } } }\n  ],\n  \"link_spec\": { \"fields\": [\"product\", \"region\"] }\n}\n```\n\nRows: two KPI tiles; the trend across the row, tall; the bar chart and the\nscatter side by side. A click on one segment of a product's bar lights that\nproduct's points on the scatter and the segment's region on the trend; a click\non a region's line lights that region on the bars and the scatter.\n\n## Checklist\n\n- [ ] `title` says the finding or the purpose; `subtitle` says data, scope, period, units; `source` is set.\n- [ ] Three to five KPI tiles at most, up to six charts, the lead chart first after the tiles.\n- [ ] Every chart but a KPI tile has a one-line `title` and a units `subtitle`.\n- [ ] `layout` set where the default is wrong: the lead chart wide, a comparison at equal spans and heights.\n- [ ] `link_spec.fields` names the shared dimensions; each chart that should take part encodes them and, to send, has the interaction whose subject the reader asks about.\n- [ ] `theme_spec` on the board only.\n- [ ] `validate_board` reports no `✗` and no review note left but the shared colour field.\n- [ ] In a later turn: the reader's theme and `grid` from the context are kept unless the user asked to change them.\n",{"name":5,"description":7},"main","a794557384adcc3293a77043f6b9aff1c33d152c","agent-skills\u002Fflint-board-author",267,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fflint-chart","https:\u002F\u002Fmicrosoft.github.io\u002Fflint-chart\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 15:45:10",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add microsoft\u002Fflint-chart --skill flint-board-author",{"tool":55,"command":56},"bunx","bunx skills add microsoft\u002Fflint-chart --skill flint-board-author",{"tool":58,"command":59},"pnpm","pnpm dlx skills add microsoft\u002Fflint-chart --skill flint-board-author","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fflint-chart\u002Fblob\u002Fmain\u002Fagent-skills\u002Fflint-board-author\u002FSKILL.md",true,[63,69],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002FGemfile","SCRIPT","脚本",362,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-documentdb\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpreviewing-docs-site\u002Fscripts\u002FGemfile",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fpreview.ps1",2290,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fvscode-documentdb\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpreviewing-docs-site\u002Fscripts\u002Fpreview.ps1",[74,91,105,121],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":86,"publishedAt":34},"01M69AXSRQVDB9W7S83SRE0ZSP","flint-theme-author","Use when: creating, translating, refining, reviewing, or validating a custom Flint ThemeSpec from brand guidelines, websites, slide decks, publication references, design tokens, or an existing visual identity. Produce a reusable ThemeSpec JSON object for Flint Theme Lab without inventing fields or changing chart semantics.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fflint-chart\u002Fblob\u002Fmain\u002Fagent-skills\u002Fflint-theme-author\u002FSKILL.md",[80,83],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":84,"categoryName":85,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[87,88,89,90],"flint theme author","design","brand guidelines","identity",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":101,"publishedAt":34},"01M69AXPYV1F85RNSJM8FC9SXN","flint-interaction-author","Use when: a Flint chart should respond to the reader (highlight, zoom, brush, legend toggle, reorder, annotate, explore, link charts); an application or an agent changes a mounted chart from outside or reads what it shows; or a gesture no preset gives must be built. Produce one valid interaction_spec, one ChartUpdate, or code against flint-chart\u002Finteractive, with no invented names.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fflint-chart\u002Fblob\u002Fmain\u002Fagent-skills\u002Fflint-interaction-author\u002FSKILL.md",[97,98],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[102,30,103,104],"flint interaction author","valid","preset",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":117,"publishedAt":34},"01M69AXMC64Z7NCCRZKFENZ1AE","flint-chart-author","Use when: the user asks to make or render charts with flint-chart, visualize tabular data, generate a ChartAssemblyInput, validate\u002Frender through MCP, or add Flint to a JS\u002FTS project. Author the semantic spec, transform data before Flint when needed, install\u002Fimport Flint only when executable code is needed, and reserve backend-specific style tweaks for after compiling from Flint.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fflint-chart\u002Fblob\u002Fmain\u002Fagent-skills\u002Fflint-chart-author\u002FSKILL.md",[111,114,115,116],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[118,119,30,120,33],"flint chart author","MCP","visualize",{"skillNo":122,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":129,"publishedAt":34},"01M69AXEZX3YWNKXJ5Y5P76B0W","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fflint-chart\u002Fblob\u002Fmain\u002F.github\u002Fextensions\u002Fflint-chart\u002Fskills\u002Fflint-chart-author\u002FSKILL.md",[125,126,127,128],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[118,33,119,120,30]]