Docs Lens Chart Settings logo

Docs Lens Chart Settings

Organization
elastic
docs-lens-chart-settings

Verify Kibana Lens chart UI settings against the source code. Use when documenting chart types, reviewing chart settings accuracy, or checking UI labels and rendering order for Lens visualizations (bar, line, area, pie, treemap, mosaic, waffle, tag cloud, heat map, gauge, metric, region map, table).

Overview

Publisherelastic
Repositoryelastic-docs-skills
Skill namedocs-lens-chart-settings
Stars
71
Forks
10
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by elastic on GitHub. Read the source before you install it.

Installation

Install the Docs Lens Chart Settings AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/elastic/elastic-docs-skills.git /tmp/elastic-docs-skills
mkdir -p .claude/skills
cp -r /tmp/elastic-docs-skills/skills/project/lens-chart-settings .claude/skills/docs-lens-chart-settings
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Docs Lens Chart Settings in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Docs Lens Chart Settings on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Docs Lens Chart Settings is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Verifying Kibana Lens Chart Settings from Source Code

When documenting Lens chart settings, always verify labels, options, and rendering order against the Kibana source code. Do NOT guess UI labels.

Key Principles

  1. UI labels come from i18n defaultMessage strings — always extract the exact label.
  2. Rendering order in JSX = rendering order in the UI — document settings in the same order they appear in the component tree.
  3. Conditional rendering is everywhere — many settings only appear under specific conditions (chart type, selected options, number of dimensions). Trace the conditions.
  4. Shared components are parameterized per chart — the same LegendSettings component behaves differently for treemaps vs waffle vs pie based on props.

Source Code Layout

Partition charts (pie, donut, treemap, mosaic, waffle)

All partition-type charts share code under:

x-pack/platform/plugins/shared/lens/public/visualizations/partition/
├── partition_charts_meta.ts          # Per-chart config (toolbar options, legend config)
├── toolbar/
│   ├── style_settings.tsx            # Orchestrates Style panel sections
│   ├── titles_and_text_settings.tsx  # Slice labels + Slice values options
│   ├── appearance_settings.tsx       # Donut hole (pie/donut only)
│   └── legend_settings.tsx           # Partition-specific legend wrapper

Shared legend component:

x-pack/platform/plugins/shared/lens/public/shared_components/legend/
├── legend_settings.tsx               # Main legend settings (Visibility, Size, Truncation, Nested, Stats)
├── location/legend_location_settings.tsx  # Position (only when `location` prop is defined)
└── size/legend_size_settings.tsx     # Width/Size dropdown

Other chart types

Each chart type has its own directory under visualizations/:

  • visualizations/xy/ for bar, line, area
  • visualizations/heatmap/
  • visualizations/gauge/
  • visualizations/metric/
  • visualizations/tagcloud/

Verification Workflow

Step 1: Find the chart metadata

For partition charts, start with partition_charts_meta.ts. This file defines per-chart:

  • toolbar.categoryOptions — Slice labels options (or empty array if none)
  • toolbar.numberOptions — Slice values options (or empty array if none)
  • toolbar.emptySizeRatioOptions — Donut hole options (pie/donut only)
  • toolbar.isDisabled — Whether the Style panel is disabled entirely (waffle)
  • legend.defaultLegendStats — Enables Statistics/Show value in legend (waffle only)
  • legend.hideNestedLegendSwitch — Hides the Nested toggle (waffle)
  • legend.getShowLegendDefault — Default legend visibility behavior for Auto mode
  • maxBuckets — Maximum Group by dimensions

Step 2: Trace the Style settings

Read toolbar/style_settings.tsx to understand the Style panel structure:

  • If emptySizeRatioOptions exists → renders Appearance accordion + Titles and text accordion
  • If not → renders only PartitionTitlesAndTextSettings directly (no sub-headers)

Then read toolbar/titles_and_text_settings.tsx:

  • categoryOptions renders as the first button group (label: check i18n key xpack.lens.pieChart.labelSliceLabels)
  • numberOptions renders as the second button group (label: check i18n key xpack.lens.pieChart.sliceValues)
  • If numberDisplay === 'percent', a Decimal places input appears

If categoryOptions is empty, the first button group is hidden. If numberOptions is empty, the second button group is hidden. If isDisabled is true, the entire section is disabled/hidden.

Step 3: Trace the Legend settings

Read toolbar/legend_settings.tsx (partition wrapper) to see what props are passed to the shared LegendSettings component. Key props to check:

PropWhat it controlsHow to verify
legendOptionsVisibility options (Auto/Show/Hide)Always present for all partition charts
positionOnly renders if location is also passedPartition charts do NOT pass location → Position hidden
renderNestedLegendSwitchNested toggle!hideNestedLegendSwitch && groups > 1
allowedLegendStatsStatistics/Show valueOnly if defaultLegendStats defined in chart meta
legendSize / onLegendSizeChangeWidth dropdownRenders if isVerticalLegend is true
shouldTruncate / onTruncateLegendChangeLabel truncation toggleAlways present when legend not hidden
showAutoLegendSizeOptionAuto in size dropdownOnly for pre-8.3 visualizations

Step 4: Determine rendering order

Read the shared legend_settings.tsx JSX top to bottom. For partition charts (no location prop), the actual rendering order is:

  1. Visibility (always)
  2. Width (when legend not hidden, via LegendSizeSettings)
  3. Label truncation + Line limit (when legend not hidden)
  4. Nested (when legend not hidden AND multiple groups AND not hideNestedLegendSwitch)

Settings that do NOT render for partition charts:

  • Position — requires location prop (only XY charts pass this)
  • Statistics — requires allowedLegendStats.length > 1
  • Show value — requires exactly 1 allowed legend stat of type Value/CurrentAndLastValue

Step 5: Verify option labels

For each button group or dropdown, check the label or inputDisplay in the options array. Common pitfalls:

What you might assumeActual UI labelSource
"Labels""Slice labels"xpack.lens.pieChart.labelSliceLabels
"Values""Slice values"xpack.lens.pieChart.sliceValues
"Legend size""Width"xpack.lens.shared.legendSizeSetting.label
"Truncate""Label truncation"xpack.lens.shared.labelTruncation
"Max lines""Line limit"xpack.lens.shared.maxLinesLabel
"Show" (legend)"Show"xpack.lens.pieChart.legendVisibility.show

Quick Reference: Per-Chart Differences

FeaturePie/DonutTreemapMosaicWaffle
Slice labelsHide/Inside/AutoHide/Show(none)(none)
Slice valuesHide/Integer/PercentageHide/Integer/PercentageHide/Integer/Percentage(none)
Donut holeYesNoNoNo
Style panel disabledNoNoNoYes
Legend PositionNoNoNoNo
Legend WidthYesYesYesYes
Nested legendYes (>1 group)Yes (>1 group)Yes (>1 group)No
Show valueNoNoNoYes
StatisticsNoNoNoNo
Default legend visibilityAuto shows when >1 bucketAuto hidesAuto hidesAuto shows always
Max Group by dimensions3221
Color mappingFirst Group by onlyFirst Group by onlyVertical axisGroup by

Common Mistakes to Avoid

  1. Assuming Position exists for partition charts — it doesn't. Only XY-type charts have Position.
  2. Using "Legend size" instead of "Width" — the actual label is "Width".
  3. Including Auto in Width options — Auto only shows for pre-8.3 visualizations.
  4. Documenting Statistics for non-waffle charts — only waffle has defaultLegendStats.
  5. Assuming "Titles and text" sub-header exists for all charts — it only appears when emptySizeRatioOptions is defined (pie/donut).
  6. Getting the Nested legend condition wrong — it requires both hideNestedLegendSwitch !== true AND multiple Group by dimensions.
  7. Assuming color mapping works on all Group by levels — only available on the first dimension.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Docs Lens Chart Settings AI skill do?

Verify Kibana Lens chart UI settings against the source code. Use when documenting chart types, reviewing chart settings accuracy, or checking UI labels and rendering order for Lens visualizations (bar, line, area, pie, treemap, mosaic, waffle, tag cloud, heat map, gauge, metric, region map, table).

Why use Docs Lens Chart Settings on TypingMind?

Because you install it once and use it with any model. Docs Lens Chart Settings is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Docs Lens Chart Settings in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/elastic/elastic-docs-skills/tree/main/skills/project/lens-chart-settings. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Docs Lens Chart Settings?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Docs Lens Chart Settings?

As many as you like. As long as a model supports skills, you can use Docs Lens Chart Settings with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Docs Lens Chart Settings AI skill free?

Yes. It is published on GitHub by elastic under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇