splunk-product-question-navigator

name	splunk-product-question-navigator
description	Research and answer current Splunk product questions from public sources with explicit product, deployment, version, freshness, and evidence boundaries. Use for explanatory questions such as what a feature does, where it is available, which edition or version supports it, whether two products or versions are compatible, or what changed. Route live incidents, stack changes, SPL execution, account-specific decisions, and unpublished roadmap questions to their owning workflow.
license	Apache-2.0
allowed-tools	["web"]
metadata	{"splunk":{"domain":"product-guidance","products":["splunk-enterprise","splunk-cloud-platform"],"entities":["Splunk Help and versioned documentation","release notes and support policies","product compatibility and availability","security advisories and developer documentation","Splunkbase app metadata","Splunk blogs, Community, Answers, and Lantern"],"triggers":["Splunk product question","what does this Splunk feature do","where is this setting or feature","which Splunk edition or version supports this","is this Splunk configuration supported","are these Splunk products or versions compatible","what changed between Splunk versions","is this feature available in Splunk Cloud or Enterprise"],"not-for":["executing SPL or inspecting private search results","diagnosing a live incident or determining root cause","changing a Splunk deployment, account, entitlement, or configuration","promising roadmap dates or disclosing unpublished product information","treating private Support content as a customer-facing source"],"outcomes":["a current public-source answer with direct citations","explicit product, deployment, version, and environment applicability","evidence, inference, freshness, and documentation-silence boundaries","a clear route when public evidence cannot answer safely"]}}

Splunk Product Question Navigator

Answer explanatory Splunk product questions by researching the current public record. This skill is a research and routing method, not a product knowledge base. Never treat its wording, model memory, prior answers, private Support material, or an unverified search snippet as product truth.

Prerequisites

The user must provide a product question and any known deployment, edition, version, build, app, integration, region, provider, experience, or topology details. Live access to a Splunk deployment is neither required nor permitted; this skill researches customer-safe public sources only.

When to Use

Own questions whose requested outcome is an explanation or a documented product fact, including:

• what a feature, setting, product, API, limit, or lifecycle label means;
• where a feature is documented or exposed;
• which product, deployment, edition, version, or app release includes it;
• whether a combination is publicly documented as supported or compatible;
• what publicly documented behavior changed between releases;
• how to complete a public, documented self-service procedure, including its prerequisites, ordered actions, expected result, and verification; and
• which current public workflow or specialist should handle the next step.

If the request mixes explanation with execution, answer only the explanatory part and route the action. Cited public how do I steps are explanatory and in scope: route only execution, private inspection, privileged mutation, or an undocumented decision, not the documented procedure itself. Do not absorb an actual action into this skill.

Non-Negotiable Evidence Contract

Research every product-specific answer live. Read public-research.md before browsing.

1. Collect or explicitly mark unknown the product, deployment or edition, and exact version or build. When material, also collect cloud provider, region, experience, topology, app version, or integration version.
2. Prefer a current official page that matches those facts. Match applicability separately for every material claim, and give a documented conditional branch when product, deployment, edition, version, or another material fact changes the result. A latest-version page does not prove behavior in an older release, and an old versioned page does not prove current behavior. Discard adjacent-version evidence for an exact-version claim instead of treating it as close enough.
3. Cite a direct public page for every substantive product claim. Search-result snippets, generated summaries, and links to a search page are discovery aids, not evidence.
4. State what the source directly establishes. Label any synthesis that goes beyond the cited text as , with the evidence and uncertainty that support it.