// Use when reviewing dashboard JSON changes in a PR or branch. Extracts structured descriptions with kbdash, compares before/after, and checks guideline compliance.
Use for all CEL and mito work on integrations that collect from APIs — writing CEL programs, cel.yml.hbs templates, manifest configuration, mock-first development with the mito CLI, system test mock setup, and answering CEL/mito questions. Load this skill whenever any data stream uses the cel input type.
Research a vendor, product, or feature to collect all information needed before building an Elastic integration. Investigates data collection methods, API or log documentation, sample data formats, field schemas, ECS mapping candidates, and configuration requirements. Outputs a structured research brief to research_results/<product>/. Invoke manually with /research-integration.
Anonymize and sanitize customer-provided log files before they are committed as pipeline test fixtures or sample events. Performs a line-by-line review and replaces all sensitive values inline, preserving log structure and format exactly — never reformats, re-indents, or restructures content. Invoke manually with /anonymize-logs.
Use when creating a new Elastic integration package, scaffolding data streams, answering package layout or structure questions, or running the end-to-end integration build workflow. Covers package topology, scaffold commands, post-scaffold edits, and full orchestration of CEL/pipeline/test subagents.
Use when creating or reviewing Kibana assets in packages, including dashboard export structure, naming, and data stream alignment.
Use when defining field mappings for data streams, populating ecs.yml with ECS field references, selecting ECS categorization values, choosing custom field types, or troubleshooting mapping validation failures.
| name | dashboard-review |
| description | Use when reviewing dashboard JSON changes in a PR or branch. Extracts structured descriptions with kbdash, compares before/after, and checks guideline compliance. |
| license | Apache-2.0 |
| metadata | {"author":"elastic","version":"1.0"} |
Use this skill when tasks include:
Do not use this skill as the primary guide for:
dashboard-guidelines)dashboard-guidelines → references/kibana-assets-layout.md)elastic-package-cli)integration-testing)kbdash must be installed:
go install github.com/efd6/kbdash@latest
Lines prefixed with [!] in the output are warnings about potential
issues in the dashboard JSON (consistency mismatches, incomplete
extraction, parse errors). Run kbdash -h for a description of each
warning type.
Read references/review-procedure.md for the full step-by-step
workflow. The high-level flow is:
kbdash.After summarizing changes, check the final state of every added or modified dashboard against the official dashboard guidelines. Report violations in a "Guideline notes" subsection after the change summary for each dashboard.
Check for these issues:
visualization panel using TSVB. The
guidelines require Lens for all new visualizations. Migrating
existing TSVB to Lens is encouraged.data_stream.dataset or an equivalently specific scope. Flag
panels that query broad index patterns (metrics-*, logs-*)
without scoping.references entries with a panelRefName indicate
by-reference panels. Flag these.input-control-vis type is
deprecated. Dashboard-native controls should be used instead.[<Package Name> ...] create unnecessary repetition. Flag these.-* patterns
without further qualification are a performance concern.Only report issues that actually exist — skip passing checks. For pre-existing violations in unchanged panels, mention them once briefly ("N existing panels also use TSVB") rather than listing each one. Focus review attention on newly added or modified panels.
After the review is complete:
dashboard-guidelines for creation or export guidance if the review surfaces structural issuespackage-spec when dashboard changes require a release note entryelastic-package-cli for validation commandsreferences/review-procedure.md — full extraction, comparison, and output formatting workflow