docs: document the discover-data-analysis Agent Builder skill (#6684)#6715
Open
florent-leborgne wants to merge 5 commits into
Open
docs: document the discover-data-analysis Agent Builder skill (#6684)#6715florent-leborgne wants to merge 5 commits into
florent-leborgne wants to merge 5 commits into
Conversation
Add a new "Analyze your data with AI" section to the Discover get-started page covering the discover-data-analysis skill, its ES|QL-only scope, auto-launch behavior, and the shape-specific guidance derived from the active context-aware profile (logs, metrics, traces). Register the skill in the Agent Builder built-in skills reference under Platform skills. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
Contributor
Elastic Docs Style Checker (Vale)Summary: 2 suggestions found 💡 Suggestions (2): Optional style improvements. Apply when helpful.
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
stratoula
approved these changes
May 29, 2026
Contributor
stratoula
left a comment
There was a problem hiding this comment.
Thank you for adding this to the docs! It is not easily discoverable!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses #6684 with the following changes:
explore-analyze/discover/discover-get-started.md: Add a new## Analyze your data with AIsection covering thediscover-data-analysisskill, the {{esql}}-only scope, the auto-attached query context, and the shape-specific guidance the agent receives when a context-aware profile (logs, metrics, traces) is active. Add a one-line pointer in the existing "Context-aware data exploration" section so readers landing there discover that the active profile also tailors AI deep analysis.explore-analyze/ai-features/agent-builder/builtin-skills-reference.md: Adddiscover-data-analysisto the Platform skills list with its assigned tools and the activation note, cross-linked to the new Discover section.explore-analyze/discover/try-esql.md: Add a one-line tip after "Refine an ES|QL query by interacting with the results table" pointing to the new AI deep analysis section, so readers learning ES|QL in Discover discover the feature too.Sibling PRs incorporated
The issue links elastic/kibana#267454 (context-aware playbook contributions). Triangulating against the implementation file at HEAD surfaced two additional sibling PRs that materially affect the user-facing behavior:
discover-data-analysisskill (9.5.0).Related work
This PR is complementary to #6714, which documents AI assistance inside the {{esql}} editor (generating {{esql}} from a
//comment withcmd+J, and the ✨ Fix with AI action on validation errors). Together the two PRs cover the full AI-in-{{esql}} story: #6714 helps you write or fix the query, this PR helps you analyze the results.The two PRs introduce new anchors that don't exist on main yet, so bidirectional cross-links between them are deferred. Whichever PR merges second should add the cross-link in a small follow-up commit before merge.
Resolves
Closes #6684