Docs fix — frontmatter: path /explore-analyze/ai-features — 19 pages

Generated by `gh-aw-docs-frontmatter-sweep` for `elastic/docs-content` on 2026-W20.

Path /explore-analyze/ai-features · 75 total in scope · subtree corpus 75 pages.

## Findings (19)

```yaml
- file: explore-analyze/ai-features/agent-skills.md
line: 1
category: missing-products
severity: high
evidence: "frontmatter has no top-level `products` field"

- file: explore-analyze/ai-features/ai-chat-experiences.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Overview of AI chat experiences in Kibana, including AI Assistant and Agent Builder for answering questions, suggesting next steps, and automating tasks."

- file: explore-analyze/ai-features/ai-chat-experiences/ai-assistant.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Overview of AI assistants in Kibana for Stack and Serverless, covering knowledge base setup and usage for observability and security workflows."

- file: explore-analyze/ai-features/elastic-agent-builder.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Overview of Elastic Agent Builder, a platform for building and deploying AI agents that can search data, run workflows, and automate tasks in Kibana."

- file: explore-analyze/ai-features/llm-guides/connect-to-amazon-bedrock.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Connect Elastic to Amazon Bedrock to use AWS-hosted LLMs for AI features such as AI Assistant and Agent Builder."

- file: explore-analyze/ai-features/llm-guides/connect-to-azure-openai.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Connect Elastic to Azure OpenAI to use Azure-hosted language models for AI features such as AI Assistant and Agent Builder."

- file: explore-analyze/ai-features/llm-guides/connect-to-google-vertex.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Connect Elastic to Google Vertex AI to use Google-hosted language models for AI features such as AI Assistant and Agent Builder."

- file: explore-analyze/ai-features/llm-guides/connect-to-lmstudio-observability.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Connect Elastic Observability AI Assistant to a local LLM running in LM Studio for air-gapped or cost-sensitive deployments."

- file: explore-analyze/ai-features/llm-guides/connect-to-lmstudio-security.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Connect Elastic Security AI Assistant to a local LLM running in LM Studio for air-gapped or cost-sensitive deployments."

- file: explore-analyze/ai-features/llm-guides/connect-to-openai.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Connect Elastic to OpenAI to use GPT models for AI features such as AI Assistant and Agent Builder."

- file: explore-analyze/ai-features/llm-guides/connect-to-vLLM.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Connect Elastic Security AI Assistant to a self-hosted LLM using vLLM for air-gapped environments without sending data to external providers."

- file: explore-analyze/ai-features/llm-guides/llm-connectors.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure Kibana connectors to give Elastic AI features access to LLM providers including OpenAI, Azure OpenAI, Amazon Bedrock, Google Vertex, and local models."

- file: explore-analyze/ai-features/llm-guides/local-llms-overview.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Overview of options for connecting Elastic AI features to self-managed LLMs, including vLLM and LM Studio for air-gapped or cost-sensitive deployments."

- file: explore-analyze/ai-features/manage-access-to-ai-assistant.md
line: 1
category: missing-description
severity: high
evidence: "frontmatter has no `description` field"
suggested_fix: |
description: "Configure AI feature settings in Kibana to control available models, track token usage, install documentation, and manage access to AI Assistant and Agent Builder."

- file: explore-analyze/ai-features/agent-builder/builtin-skills-reference.md
line: 3
category: weak-description
severity: medium
evidence: "description 'Reference of all built-in skills available in Elastic Agent Builder.' is a noun-phrase label, not an action-oriented sentence"
suggested_fix: |
description: "Built-in skills reference for Elastic Agent Builder, listing each skill's purpose, inputs, and configuration."

- file: explore-analyze/ai-features/agent-builder/limitations-known-issues.md
line: 3
category: weak-description
severity: medium
evidence: "description 'Find limitations and known issues for Agent Builder.' is too brief and uses an imperative verb that adds no informational value"
suggested_fix: |
description: "Known limitations and open issues for Agent Builder, covering feature gaps, performance constraints, and available workarounds."

- file: explore-analyze/ai-features/agent-builder/skill-creation-guidelines.md
line: 3
category: weak-description
severity: medium
evidence: "description 'Guidelines for creating effective custom skills in Elastic Agent Builder.' is a noun-phrase label, not a complete sentence"
suggested_fix: |
description: "Best practices for writing effective custom skills in Elastic Agent Builder, covering structure, naming, and prompt instructions."

- file: explore-analyze/ai-features/agent-builder/tools/builtin-tools-reference.md
line: 3
category: weak-description
severity: medium
evidence: "description 'Reference of all built-in tools available in Elastic Agent Builder.' is a noun-phrase label, not an action-oriented sentence"
suggested_fix: |
description: "Built-in tools reference for Elastic Agent Builder, listing each tool's purpose, inputs, and configuration."

- file: explore-analyze/ai-features/ai-chat-experiences/ai-assistant-host-doc-artifacts.md
line: 10
category: description-too-long
severity: medium
evidence: "description is 201 characters, 1 over the 200-character limit"
suggested_fix: |
description: "Host AI Assistant knowledge base artifacts using S3-compatible storage, CDN, or local paths when Kibana cannot reach Elastic's public URL."
```

## Done when
- All listed pages have a non-empty, <=200-character `description` field and required frontmatter keys present per the repo's frontmatter schema.
- A PR addressing this issue is merged.

## Notes
- Snippet files under `_snippets/` were excluded as they are not standalone pages.

> Generated by [Docs frontmatter sweep agent](https://github.com/elastic/docs-content/actions/runs/25733943751/agentic_workflow) · ● 983.7K · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fdocs-content%2Fgh-aw-docs-frontmatter-sweep%22&type=issues)