// Use when creating or reviewing Kibana assets in packages, including dashboard export structure, naming, and data stream alignment.
| name | dashboard-guidelines |
| description | Use when creating or reviewing Kibana assets in packages, including dashboard export structure, naming, and data stream alignment. |
| license | Apache-2.0 |
| metadata | {"author":"elastic","version":"1.0"} |
Use this skill when tasks include:
kibana/ foldersdata_stream.dataset filteringDo not use this skill as the primary guide for:
create-integration, package-structure)ingest-pipelines)elastic-package-cli)integration-testing → references/system-testing.md)Before creating or updating dashboard assets, verify:
packages/<package_name>/)manifest.yml compatibility constraints (conditions.kibana.version) are understood# from package root
elastic-package export
elastic-package edit dashboards
elastic-package export dashboards
Review exported files under kibana/:
Run package validation commands before opening a PR:
elastic-package check
Use naming conventions from dashboard creation guidance:
<Name> (avoid repeating package name in each panel title)[<Metrics | Logs> <PACKAGE NAME>] <Name>[Metrics System] Host overview, [Logs Nginx] Access overview{PACKAGE_NAME}-{identifier}.jsonnginx-046212a0-a2a1-11e7-928f-5dbe6f6f5519.jsonlogs-* / metrics-* queries where possible.
data_stream.datasetkibana/dashboard/ and follow expected naming patterndata_stream.dataset when applicable)elastic-package check passes for the packagelogs-*/metrics-* queries that cause noisy or slow panelsAfter dashboard updates are in place, continue with:
dashboard-review for reviewing dashboard JSON changes in a PR or branchintegration-testing → references/system-testing.md for system test validationelastic-package-cli for broader check/lint/test command selectionpackage-spec when dashboard changes require a release note entryreferences/kibana-assets-layout.mdUse 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 reviewing dashboard JSON changes in a PR or branch. Extracts structured descriptions with kbdash, compares before/after, and checks guideline compliance.
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.