kibana-dashboard

Generate Kibana dashboards with metric, XY, gauge, datatable, and markdown panels.

6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill kibana-dashboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kibana-dashboard
Source: https://github.com/patrykkopycinski/elastic-cursor-plugin/tree/main/.cursor/skills/kibana-dashboard
Command: npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill kibana-dashboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes manual dashboard construction by translating high-level descriptions and data queries into runnable Kibana-as-code dashboards, saving time and ensuring consistent layouts and validation.

Core Features & Use Cases

  • Data discovery: Use index listing, mappings, and sampling queries to understand available fields and time ranges before building panels.
  • Dashboard as code: Generate metric, XY, gauge, datatable, and markdown panels and translate them into the raw Kibana as-code API format or call the kibana_create_dashboard tool.
  • Schema and safety rules: Enforces ES|QL vs dataView placement, layer-level dataset rules, axis/alias constraints, grid sizing, time-range validation, and required feature-flag handling with fallbacks for older Kibana versions.
  • Use case: Quickly create observability dashboards that show KPIs, trend charts, and summary tables for an Elasticsearch index across a consistent grid and validated time window.

Quick Start

Create a Kibana dashboard showing average response time, request rate, and error rate for my-index over the last 24 hours using the kibana_create_dashboard tool.

Frequently Asked Questions about kibana-dashboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I programmatically create Kibana dashboards from Elasticsearch queries?

You can programmatically create Kibana dashboards by translating high-level descriptions and data queries into runnable Kibana-as-code dashboards. This process automatically generates metric, XY, gauge, datatable, and markdown panels while enforcing grid layouts and time-range validation.

Can I use ES|QL queries in Kibana dashboard panels?

Yes, you can use ES|QL queries in Kibana dashboard panels. The generation process enforces specific ES|QL versus dataView placement rules, ensuring layer-level dataset rules, axis constraints, and required feature-flag handling are correctly satisfied for your visualization layers.

What is the best way to automate observability dashboard generation in Kibana?

Automating observability dashboard generation in Kibana is best achieved by using a dashboard-as-code approach. This translates high-level descriptions into raw Kibana API formats or calls the kibana_create_dashboard tool, ensuring consistent layouts and validated time windows for monitoring KPIs and trend charts.

Does Kibana dashboard automation support metric, XY, and gauge visualizations?

Kibana dashboard automation supports metric, XY, gauge, datatable, and markdown visualizations. It translates your high-level descriptions and data queries into these panel types while enforcing grid sizing, time-range validation, and schema rules across your Elasticsearch indices.

How do I discover available fields and time ranges before building Kibana panels?

To discover available fields and time ranges before building Kibana panels, use index listing, mappings, and sampling queries. This data discovery step helps you understand your Elasticsearch dataset structure and time windows prior to generating the final dashboard layout.

What are the limitations of generating Kibana dashboards as code for older Kibana versions?

Generating Kibana dashboards as code for older Kibana versions may encounter feature-flag limitations. The generation process includes fallbacks for older versions, but certain schema rules, ES|QL dataset placements, or panel-level constraints might not be fully supported without the necessary feature flags enabled.