Skip to main content

Elastic and Kibana

These skills are gated to Elastic/Kibana contexts and layer domain policy over generic workflows.

The boundary is intentional: generic skills (k-review, k-agent-review, k-github, k-compose-*) keep portable mechanics and gates; this page's skills own Elastic/Kibana labels, ownership, Buildkite routing, bot allowlists, PR templates, release-note rules, commit attribution, and Kibana live-UI target/data setup.

k-elastic-domain

FieldValue
Use whenElastic/Kibana overlay for PRs, labels, ownership, bots, Buildkite, live UI
Sourceexact_k-elastic-domain
Boundarypropose-only unless the active primary skill permits side effects

The overlay also carries a Kibana planning fork checklist (references/kibana-planning-forks.md) that the generic k-spec skill consults when the target repo is elastic/kibana: API versioning, Saved Objects/migrations, privileges, dependencies, feature flags, backports, test placement, alerting, and instrumentation forks. Adapted from the specialist elicitation_questions in elastic/plan (prompts/teams/elastic-kibana/); refresh it by re-reading that directory upstream and folding in changes — curated, not mirrored.

k-buildkite

FieldValue
Use whenBuildkite status, logs, pipelines, debug, or any buildkite.com URL
Sourceexact_k-buildkite
Gateelastic org repos

k-kibana-labels-propose

FieldValue
Use whenproposing labels, backports, or version targets for Kibana PRs/issues
Sourceexact_k-kibana-labels-propose
Boundarypropose-only

k-kibana-management-ownership

FieldValue
Use whendetermining Kibana ownership/reviewer targeting via CODEOWNERS
Sourceexact_k-kibana-management-ownership
Boundarypropose-only

k-kibana-console-monaco

FieldValue
Use whenautomating/testing Kibana Dev Tools Console Monaco editor
Sourceexact_k-kibana-console-monaco
Gateelastic/kibana repos

k-kbn-stack

FieldValue
Use whenstarting, reusing, inspecting, or tearing down local Kibana ES+Kibana dev stacks
Sourceexact_k-kbn-stack
Tool,kbn-stack
Gateelastic/kibana repos

Detached ,kbn-stack --detach starts record the Kibana process log as kbn_log in the registry. Kibana live-UI checks use that log for optimizer-bundle readiness; the ES log field is not optimizer evidence. Before reusing a ready registry entry, correlate it with recorded pids, slot-derived port listeners, and log paths. That check validates a registry entry; it does not license guessing arbitrary localhost targets.

k-kbn-backport

FieldValue
Use whenrunning an end-to-end Kibana backport workflow
Sourceexact_k-kbn-backport
Routingmanual

k-kbn-standup

FieldValue
Use whenpreparing a draft for the Admin UX daily update
Scopeaccessible public, internal, and private Elastic repositories plus Slack/DMs
Formatbare URLs; per-artifact icons; :merged: per merge; direct :sdh: summary tag
Sourceexact_k-kbn-standup
Routingmanual