Kibana Workflows
ElasticOfficialCreated by elastic
- Skill
- Tool integration
- Automation and integrations
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The kibana-workflows skill enables users to create, validate, and execute declarative automation workflows within Kibana. It supports the full lifecycle of workflow development, from initial drafting based on natural language requirements to testing, saving, and running workflows against an Elastic stack. The skill provides guidance on using the correct authoring path—either via Discovery-tools or raw schema—and ensures safe testing practices by recommending console-stubbed drafts for side-effecting operations.
What it does
- Translates natural language requests into valid Elastic Workflow YAML definitions.
- Validates workflow YAML against the target Kibana environment.
- Executes workflow tests and individual steps to verify logic.
- Manages the lifecycle of workflows including saving, enabling, and running.
- Inspects workflow execution status and logs for debugging.
- Resolves connector IDs and step definitions for accurate workflow configuration.
When to use it
- When you need to automate tasks within Kibana using triggers like manual, scheduled, or alert events.
- When you are building or debugging Elastic Workflow YAML files.
- When you need to integrate external systems like Slack or Jira into your Kibana automation.
- When you want to test a workflow logic safely before enabling it in production.
Advantages
- Provides a structured, safe testing loop to prevent unintended side effects.
- Automates the discovery of step definitions and connector configurations.
- Supports both modern Discovery-tools and legacy schema-based authoring paths.
- Ensures consistent YAML structure through validated templates and best practices.
Usage examples
- “Create a manual workflow named 'Manual Hello Workflow' that accepts a name input and logs 'Hello {{ inputs.name }}'.”
- The agent generates the YAML, tests it using the test API, and provides the steps to save and run the workflow.
- “How do I trigger a workflow when a security alert fires?”
- The agent explains the alert trigger configuration and provides a template for iterating over alert events.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/elastic/kibana-workflows/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip kibana-workflows.zip -d .agents/skills
Documentation by elastic
Author Elastic Workflows
Create and iterate on Elastic Workflow YAML definitions. Workflows are declarative automations that run inside Kibana: they query Elasticsearch, set data, branch, loop, call connectors, create cases, notify external systems, and invoke AI steps.
<!-- begin-partial: preamble -->
Environment Configuration
This skill executes Elasticsearch operations through the elastic CLI. If the
elastic CLI is not installed, tell the user what it is needed for. Do
not guess credentials, call the HTTP API directly, or attempt other workarounds.
This skill references operations in HTTP-shorthand form (e.g., GET /, GET /_cat/indices, GET /{index}/_mapping,
GET /{index}/_settings/index.mode, POST /_query). The Operations table at the end of this document
maps each shorthand to the equivalent elastic CLI command — always use the CLI rather than calling the HTTP API
directly.
<!-- end-partial: preamble -->
If the user asks only for a draft or explanation and explicitly forbids live access, skip connection verification and do not call the CLI or APIs. State that the draft was not validated against a target deployment.
If workflow APIs are unavailable, report the returned status and message. Common causes are an unsupported Kibana
version, insufficient license or feature privileges, or Workflows not being offered on the target project. The
workflows:ui:enabled setting controls the Kibana UI; it does not remove the public Workflows APIs.
Pick the authoring path
Default to the Discovery-tools path below — the platform.workflows.* tools are registered by default on Kibana
9.5+ and Serverless. Confirm with one probe: GET kbn:/api/agent_builder/tools returns
{ "results": [ { "id": ... } ] }; save it to a file and grep for "id": "platform.workflows.". Two fallbacks, both
loaded only when needed:
No
agent_builderendpoint (404) or noplatform.workflows.*ids (e.g. Kibana 9.4) → read references/schema-path.md and hand-author from the raw JSON Schema.An LLM connector is wired into Agent Builder and the user prefers Kibana's own generator → read references/generator-path.md.
State which path you picked and why in one sentence before proceeding. Measured path benchmarks live in references/path-performance.md.
Guidelines (all paths)
Treat tests as executions.
POST kbn:/api/workflows/testruns the workflow graph, andPOST kbn:/api/workflows/step/testruns the selected step. Test only when every executed action is read-only or the user authorized its effects. Otherwise test a copy whose writes, notifications, and external calls are replaced withconsole, then restore the real steps and save the workflow disabled.Cite endpoints in HTTP shorthand, never raw transport. This skill's body refers to operations like
POST kbn:/api/workflows/test. The Operations table is the single place where shorthand binds to a concrete CLI command.Prefer purpose-built actions over generic
http. For Slack/Jira/PagerDuty/etc., prefer the connector step type (e.g.slack2.sendMessage) over a rawhttpcall. Discover the exact action type viaget_step_definitions(or the strict schema on the fallback path).Reference step outputs as
steps.<name>.output, neversteps.<name>.with.*. Trigger event data isevent, nevertrigger.eventortriggers.event.Don't guess connector ids. Call
platform.workflows.get_connectors(Discovery-tools path) orGET kbn:/api/workflows/connectors(Schema path), or ask the user. Placeholders should be obviously fake.Handle failure deliberately. Add retry or fallback behavior where the user's requirements call for resilience. Do not add
continue: trueeverywhere: it can hide a failed action and allow the workflow to report false success.Surface gates, don't paper over them. If the API returns
403 ... not available, report the required license or privileges; do not silently retry or blame the UI setting.
Discovery-tools path
Use when platform.workflows.* tools are registered on the target Kibana. All calls go through
POST kbn:/api/agent_builder/tools/_execute with { "tool_id": "...", "tool_params": { ... } }. Response shape:
{ "results": [ { "type": "other", "data": { ... }, "tool_result_id": "..." } ] } — the payload you want is
.results[0].data. Send the request body from a file and write the response to a file (see Operations),
then jq against that file; do not inline python3 -c on multi-line JSON.
Keep context small; minimize round-trips. Do NOT front-load the whole step catalog — pull only the targeted details you need, keep large tool output in files (not the transcript), and author in as few turns as possible (measured rationale: references/path-performance.md).
Capture the user's intent before writing YAML. Identify, in order, the trigger (
manual/scheduled/alert), the inputs the workflow will receive at runtime, the data sources it must read, the actions it must take, and the desired output. If a required dependency is unknown (e.g. a Slack connector id), ask the user or use a clearly-marked placeholder.Look up only what you'll use. For the specific step types this workflow needs:
platform.workflows.get_step_definitionswith an exactstepType(e.g."http","elasticsearch.esql.query","slack2.sendMessage"), or withsearchto browse. The response includes input params, config params, anoutputSummarywhen you passincludeOutputSummary: true, and usage examples. PassincludeFullSchema: trueonly if the compact summary is insufficient.platform.workflows.get_trigger_definitionsfor the trigger event schema.platform.workflows.get_connectorsto resolve realconnector-idvalues for connector actions.platform.workflows.get_exampleswhen you need a working YAML shape for a pattern.
Write each response to a file and jq the field you need — don't let full tool output land in the transcript.
Draft the whole workflow in one pass. A workflow requires
name, at least one trigger, and a non-emptystepsarray. Use 2-space indentation. Reference outputs assteps.<name>.output.*. Build the complete YAML in a single edit rather than growing it across many turns.Validate once. Call
platform.workflows.validate_workflowwith{ "yaml": "..." }. On failure it returns errors + step definitions for referenced step types automatically, so you rarely need a secondget_step_definitionscall. Fix all reported issues in a single edit, then re-validate.Test, save, and run. See Test / save / run below. Use
platform.workflows.workflow_execute_stepto iterate on a single step (withconfirmation_bodyfor unsafe steps).
Schema path (last resort)
Only for Kibanas without the platform.workflows.* tools (see the probe above). Full recipe:
references/schema-path.md.
Test / save / run
Shared final phase for both paths.
Test only an execution-safe draft. Call
POST kbn:/api/workflows/testwith the YAML inline asworkflowYamland the run-timeinputs. For any workflow that writes / notifies / calls external services, replace those steps withconsolein the tested copy first, then restore them and save the workflow disabled.Poll the execution. The response carries a
workflowExecutionId. PollGET kbn:/api/workflows/executions/{executionId}untilstatusis one ofcompleted,failed,cancelled, ortimed_out; then fetchGET kbn:/api/workflows/executions/{executionId}/logsfor step-by-step output. Only treatstatus: completedas success.Save.
POST kbn:/api/workflows/workflowwith{ yaml, id? }. Save side-effecting workflows withenabled: falseuntil the user has authorized a real run. Subsequent edits usePUT kbn:/api/workflows/workflow/{id}and may updateyaml,enabled,name,tags, ordescription(partial updates supported).Run only when authorized. Enable the workflow, then call
POST kbn:/api/workflows/workflow/{id}/runwith the sameinputsshape used at test time. Inspect via the execution + logs endpoints.
Workflow YAML Quick Reference
version: "1"
name: Manual Hello Workflow
description: Logs a hello message from a manual workflow
enabled: true
tags: ["demo", "workflow"]
triggers:
- type: manual
inputs:
properties:
name:
type: string
description: Name to greet
default: "world"
steps:
- name: log_hello
type: console
with:
message: "Hello {{ inputs.name }}"An ordinary action step can use fields like these when its strict schema allows them:
- name: unique_step_name
type: step_type
with:
param: value
connector-id: connector-id-for-connector-actions # connector actions only
if: "steps.previous.output.ok: true"
timeout: "30s"
on-failure:
retry:
max-attempts: 3
delay: "5s"
fallback:
- name: handle_error
type: console
with:
message: "Step failed"Use {{ ... }} when rendering text. Use ${{ ... }} when an entire value must retain its native type, for example
documents: "${{ steps.search.output.hits.hits }}".
Common step types include:
| Step type | Use for |
|---|---|
console | Debug logging during tests |
elasticsearch.search | Query Elasticsearch with Query DSL |
elasticsearch.esql.query | Query Elasticsearch with ES|QL |
elasticsearch.bulk | Bulk indexing |
kibana.request | Call a Kibana API |
data.set | Set values under variables |
if | Branch on a KQL-style condition |
foreach | Loop over a collection |
wait | Pause execution |
http | Generic HTTP requests |
workflow.execute | Run another saved workflow |
This is not an exhaustive compatibility list. On the Discovery-tools path, platform.workflows.get_step_definitions
answers "does step X exist and what does it take". On the schema path, GET kbn:/api/workflows/schema?loose=false is
the source of truth, and GET kbn:/api/workflows/connectors lists configured connector instances.
data.set stores variables for the current execution; it does not persist durable data. Use an Elasticsearch or Kibana
write action when the user asks to retain data after the execution.
Examples
Manual hello (smallest possible draft): "Make a workflow that logs hello." → manual trigger + one console step
that prints Hello {{ inputs.name | default: "world" }}. Test with POST kbn:/api/workflows/test. See
Demo Test Loop.
Scheduled health check: "Every 5 minutes, ping https://api.example.com/health and log the response." → scheduled
trigger (every: 5m) + http step + console. Look up the exact with shape with get_step_definitions("http"). Add
bounded retry if requested.
Alert-triggered case + Slack notify: "When a Security alert fires, create a case and post to #soc-incidents." →
alert trigger + foreach over event.alerts + connector actions. Use get_step_definitions("cases.createCase") and
get_step_definitions(search: "slack") (current fixtures use cases.createCase and slack2.sendMessage), then
get_connectors for the real connector-ids. See Workflow Patterns.
For unfamiliar shapes on the schema path, read Workflow Patterns and Generation Tips before drafting.
Operations
The HTTP-shorthand references in the body above bind to the elastic CLI commands below. Multi-line YAML and JSON
payloads are easier to pass via --input-file <path> than as inline flags.
Workflows API (both paths).
| HTTP API (shorthand) | elastic CLI command |
|---|---|
GET / | elastic es info |
GET kbn:/api/workflows | elastic stack kb workflows get-workflows |
GET kbn:/api/workflows/workflow/{id} | elastic stack kb workflows get-workflows-workflow-id --id <id> |
POST kbn:/api/workflows/workflow | elastic stack kb workflows post-workflows-workflow --input-file <path> |
PUT kbn:/api/workflows/workflow/{id} | elastic stack kb workflows put-workflows-workflow-id --id <id> --input-file <path> |
DELETE kbn:/api/workflows/workflow/{id} | elastic stack kb workflows delete-workflows-workflow-id --id <id> |
DELETE kbn:/api/workflows/workflow/{id}?force=true | elastic stack kb workflows delete-workflows-workflow-id --id <id> --force true |
POST kbn:/api/workflows/test | elastic stack kb workflows post-workflows-test --input-file <path> |
POST kbn:/api/workflows/workflow/{id}/run | elastic stack kb workflows post-workflows-workflow-id-run --id <id> --inputs <json> |
POST kbn:/api/workflows/step/test | elastic stack kb workflows post-workflows-step-test --input-file <path> |
GET kbn:/api/workflows/executions/{executionId} | elastic stack kb workflows get-workflows-executions-executionid --execution-id <id> |
GET kbn:/api/workflows/executions/{executionId}/logs | elastic stack kb workflows get-workflows-executions-executionid-logs --execution-id <id> |
POST kbn:/api/workflows/executions/{executionId}/cancel | elastic stack kb workflows post-workflows-executions-executionid-cancel --execution-id <id> |
POST kbn:/api/workflows/executions/{executionId}/resume | elastic stack kb workflows post-workflows-executions-executionid-resume --execution-id <id> |
GET kbn:/api/workflows/workflow/{workflowId}/executions | elastic stack kb workflows get-workflows-workflow-workflowid-executions --workflow-id <id> |
GET kbn:/api/workflows/schema?loose=false | elastic stack kb workflows get-workflows-schema --loose false |
GET kbn:/api/workflows/connectors | elastic stack kb workflows get-workflows-connectors |
Agent Builder tools (Discovery-tools path).
Every tool below is invoked through the same execute endpoint. Pass --input-file a JSON file with
{ "tool_id": "...", "tool_params": { ... } }.
| HTTP API (shorthand) | elastic CLI command |
|---|---|
GET kbn:/api/agent_builder/tools | elastic stack kb agent-builder get-agent-builder-tools |
POST kbn:/api/agent_builder/tools/_execute | elastic stack kb agent-builder post-agent-builder-tools-execute --input-file <path> |
Workflow-relevant tool_ids:
tool_id | Purpose |
|---|---|
platform.workflows.validate_workflow | Validate a YAML string; failure response includes step definitions for referenced step types. |
platform.workflows.workflow_execute_step | Execute one step against the real environment (with user confirmation for unsafe steps). |
platform.workflows.get_step_definitions | Look up step type params, outputs, examples. stepType for exact match, search for keyword. |
platform.workflows.get_trigger_definitions | Look up a trigger's full event schema. |
platform.workflows.get_connectors | List connector instances configured on the target. |
platform.workflows.get_examples | Search the bundled example library for working YAML patterns. |
Notes.
For post-workflows-test, the input file is JSON of the form { "workflowYaml": "...", "inputs": {} } (or workflowId
in place of workflowYaml). For post-workflows-workflow, use { "yaml": "...", "id": "..." } — id is optional. For
put-workflows-workflow-id, include only the fields to update from name, enabled, tags, yaml, and
description. Deletion is soft by default. Use force=true only when permanent deletion and immediate ID reuse are
intended. The Kibana API version is 2023-10-31; the CLI sets it automatically.
When invoking read-only get- commands from a shell that leaves stdin open (some terminals and agent runtimes do this),
append </dev/null to avoid an EAGAIN: resource temporarily unavailable crash — e.g.
elastic stack kb workflows get-workflows-executions-executionid --execution-id "{id}" </dev/null.
Files
- ATTRIBUTION.mdAdded by AutoGineer957 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md18.6 KiB
- references/demo-test-loop.md2.9 KiB
- references/generation-tips.md5.0 KiB
- references/generator-path.md5.5 KiB
- references/path-performance.md1.9 KiB
- references/schema-path.md2.1 KiB
- references/workflow-patterns.md3.8 KiB
- references/workflow-yaml-reference.md11.2 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2026 Elasticsearch BV
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Python
The author says: Kibana 9.4 or later with matching Elasticsearch and an Enterprise license, or an Elastic Serverless project with Workflows available; requires the `elastic` CLI ≥ 0.2 with `stack kb workflows` support. When Agent Builder is enabled on the target Kibana, the `platform.core.generate_workflow` and `platform.workflows.*` tools are preferred over the raw schema.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- elastic
- Publisher
- Elastic (Official)
- Source
- elastic/agent-skills · skills/kibana/kibana-workflows · commit 09d879d
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- elastic/agent-skills
AutoGineer is not affiliated with or endorsed by elastic or Elastic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download kibana-workflows.zip