flint-theme-author

flint-theme-author is a skill for Claude Code, Codex from microsoft/flint-chart. It costs 64 tokens per session (2,215 once invoked), scanned A, original, MIT.

A set of rules for turning brand references such as websites, slide decks, and design tokens into a Flint ThemeSpec, a reusable JSON description of chart styling. Flint is a charting library from Microsoft.

In plain words
What is it for?
It helps create a valid ThemeSpec for Flint Theme Lab and omit design decisions that Flint's theme format cannot represent.
Why use it?
It helps keep chart colors, typography, and other supported visual settings consistent with an existing brand or reference design.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit It helps create a valid ThemeSpec for Flint Theme Lab and omit design decisions that Flint's theme format cannot represent.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/flint-chart/flint-theme-author
About the project

Flint is a visualization language that turns compact, human-editable chart descriptions into charts without requiring an agent to specify every layout detail. Its library produces output for formats including Vega-Lite, ECharts, Chart.js, Plotly, and editable Excel charts, while its MCP server lets agents create, validate, and render visualizations. The catalogue skills, agent, and MCP integration help coding agents use Flint.

microsoft/flint-chart · 4,380 stars · on GitHub · microsoft.github.io

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add microsoft/flint-chart --skill flint-theme-author
Clone the repo
git clone --depth 1 https://github.com/microsoft/flint-chart

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for flint-theme-author

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/flint-chart/flint-theme-author/github.svg)](https://agentmods.dev/skills/microsoft/flint-chart/flint-theme-author)
Your own site
<a href="https://agentmods.dev/skills/microsoft/flint-chart/flint-theme-author"><img src="https://agentmods.dev/badge/skills/microsoft/flint-chart/flint-theme-author/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for flint-theme-author

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/flint-chart/flint-theme-author"><img src="https://agentmods.dev/badge/skills/microsoft/flint-chart/flint-theme-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,215 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.02215
Opus 5.5 $0.00026 $0.00886
Sonnet 5.5 $0.00013 $0.00443
Haiku 4.5 $0.00006 $0.00221

Measured 29d ago against content hash 066bc3d4fbf6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flint-theme-author scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 29d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agent-skills/flint-theme-author/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flint ThemeSpec authoring

Create a reusable visual system for Flint charts. Translate the user's reference materials into one valid ThemeSpec that can be pasted directly into Theme Lab.

Authoritative references

Read these before authoring. When prose and source disagree, the TypeScript contract is authoritative.

Do not invent keys. If a requested decision cannot be represented by ThemeSpec, omit it and briefly identify the unsupported decision outside the JSON only when the user asked for an explanation.

Output contract

Unless the user asks for commentary, return exactly one valid JSON object:

  • Return the bare ThemeSpec, not { "theme_spec": ... } and not a complete ChartAssemblyInput.
  • Do not wrap JSON in a Markdown fence.
  • Do not include comments, placeholders, ellipses, or trailing commas.
  • Include a stable kebab-case id and a human-readable label.
  • Include only supported fields and only decisions justified by the references.
  • Omit unspecified optional fields rather than guessing.

The top-level output schema is:

{
  "extends": "optional-preset-id",
  "id": "theme-id",
  "label": "Theme label",
  "ink": {},
  "type": {},
  "structure": {},
  "marks": {},
  "labels": {},
  "legend": {},
  "dataLabels": {},
  "annotation": {},
  "furniture": [],
  "facets": {},
  "layout": {},
  "chartDefaults": {},
  "compileDefaults": {},
  "interaction": {},
  "variants": []
}

Every block except id and label may be omitted. The skeleton shows the shape, not a requirement to emit empty blocks.

Theme boundary

A theme controls presentation and compiler behavior across many charts. It may decide color, typography, surfaces, grids, axes, mark geometry, labels, legends, annotations, density, spacing, facets, and reusable chart defaults.

Read the full file on GitHub · 205 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 29d ago Changed · +2 lines 066bc3d4fbf6
  2. 1mo ago First seen · 203 lines · 64 tokens per session scan A e1d84f72850f

Subscribe to this mod's changes

flint-theme-author is a skill published in the GitHub repository microsoft/flint-chart (4,380 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 2,215 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

wireframe-power-bi-page

Use when planning the layout of a Power BI report page. Triggers on phrases like "wireframe a page", "layout for a dashboard", "where should I put the visuals", "design the page layout", "how should I arrange these visuals". Covers canvas geometry (1280x720), 5 validated layouts, the pbirlayoutgrid tool, spacing math.

jonathan-pap/powerbi-report-mcp · 81 tokens

design-power-bi-report

Use when polishing or theming a Power BI report — typography, colors, KPI cards, slicer placement, formatting taste decisions. Triggers on phrases like "make my report look better", "improve the design", "what colors should I use", "format this dashboard", "report doesn't look professional".

jonathan-pap/powerbi-report-mcp · 67 tokens

diagram-design

Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel…

cathrynlavery/diagram-design · 211 tokens

dashboard-design

Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after…

mckinsey/vizro · 71 tokens

bklit-ui-design

Turns plain-language chart design requests into exact Bklit UI (@bklit shadcn registry) components and props, styled to fit the host app. Use when someone describes how a chart should look rather than naming props, e.g. "diagonal pattern background that fades out", "squircle bars", "3D glass bars", "hatched area"…

bklit/bklit-ui · 185 tokens

reimagine-it-extract

Emit the content signals reimagine-it reads from an HTML file — title, anchors, proper nouns, dates, numbers, emails, links, source hex colors, and the derived palette — as JSON without generating a redesign. Use when the user says /reimagine-it extract, "what does the engine see in this page", "extract the palette"…

Kayforkind/reimagine-it · 133 tokens