Skip to content
Skills Library
Data & analytics · Analysis

datasphere-explorer

/datasphere-explorer

SAP Datasphere exploration and discovery assistant. Guides users through understanding their Datasphere landscape — browsing spaces, discovering data assets in the catalog, inspecting table schemas, profiling data quality, tracing lineage, and building queries interactively. Use this skill whenever the user wants to explore, discover, understand, or get oriented in their SAP Datasphere environment. Also trigger when the user mentions "Datasphere", "spaces", "catalog", "data assets", "schema", "data profiling", "lineage", or asks questions like "what data do we have", "show me the tables", "wha

Licence
MIT
Last repository change
08.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 08.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

SAP Datasphere exploration and discovery assistant. Guides users through understanding their Datasphere landscape — browsing spaces, discovering data assets in the catalog, inspecting table schemas, profiling data quality, tracing lineage, and building queries interactively. Use this skill whenever the user wants to explore, discover, understand, or get oriented in their SAP Datasphere environment. Also trigger when the user mentions "Datasphere", "spaces", "catalog", "data assets", "schema", "data profiling", "lineage", or asks questions like "what data do we have", "show me the tables", "wha

Triggers from the description

Dataspherespacescatalogdata assetsschemadata profilinglineagewhat data do we have
Original author description

SAP Datasphere exploration and discovery assistant. Guides users through understanding their Datasphere landscape — browsing spaces, discovering data assets in the catalog, inspecting table schemas, profiling data quality, tracing lineage, and building queries interactively. Use this skill whenever the user wants to explore, discover, understand, or get oriented in their SAP Datasphere environment. Also trigger when the user mentions "Datasphere", "spaces", "catalog", "data assets", "schema", "data profiling", "lineage", or asks questions like "what data do we have", "show me the tables", "wha

How it works

  1. Before You Start
  2. Core Exploration Workflows
  3. Handling Common Situations
  4. MCP Tools Reference
  5. Presentation Guidelines
  6. What's New (2026.05)
  7. What's New (2026.10)
Original SKILL.md headings · 180 lines, 1,474 words
SKILL.md preview
---
name: datasphere-explorer
description: >
  SAP Datasphere exploration and discovery assistant. Guides users through understanding their
  Datasphere landscape — browsing spaces, discovering data assets in the catalog, inspecting table
  schemas, profiling data quality, tracing lineage, and building queries interactively.
  Use this skill whenever the user wants to explore, discover, understand, or get oriented in their
  SAP Datasphere environment. Also trigger when the user mentions "Datasphere", "spaces", "catalog",
  "data assets", "schema", "data profiling", "lineage", or asks questions like "what data do we have",
  "show me the tables", "what's in this space", or "help me find data". Even if the user just wants
  to browse or get a lay of the land, this skill should activate.
---

# SAP Datasphere Explorer

Guide users through discovering and understanding their SAP Datasphere environment. Think of yourself
as a knowledgeable data steward who helps people navigate their data landscape, find the right datasets,
understand what's available, and answer questions about their data — all without requiring them to know
SQL, OData, or Datasphere internals.

## Before You Start

Verify the MCP connection is live by calling `test_connection`. If it fails, help the user troubleshoot
their credentials before proceeding. See `references/exploration-workflows.md` for the connection
troubleshooting checklist.

## Core Exploration Workflows

There are several natural ways a user might want to explore. Rather than forcing a fixed path, recognize
what the user is trying to do and pick the right workflow.

### 1. Landscape Overview ("What do we have?")

When the user wants to understand the big picture:

1. Call `list_spaces` to get all available spaces
2. Summarize the spaces — group them by purpose if the naming makes it obvious (e.g., production vs.
   development, by department, by data domain)
3. For each space of interest, call `get_space_info` to show storage usage, member count, and status
4. Offer to drill into any space the user finds interesting

Present this conversationally. Instead of dumping a raw table, say something like "You have 12 spaces —
the largest is SALES_PROD at 45GB with 23 objects. There are a few that look like development environments
(DEV_ANALYTICS, SANDBOX_TEAM). Want me to explore any of these?"

### 2. Space Deep Dive ("What's in this space?")

When the user picks a specific space:

1. Call `get_space_assets` to list all assets in the space
2. Group assets by type (views, tables, data flows, analytic models, etc.)
3. Highlight key metrics: total assets, most recently modified, any that look like "golden" or
   curated datasets
4. Call `search_repository` with the space filter for additional object details and lineage info

Provide a navigable summary. Suggest next steps: "This space has 8 views and 15 tables. The views look
like they're consumption-ready analytics layers. Want me to inspect the schema of any specific one?"

### 3. Data Catalog Search ("Find me data about X")

When the user is looking for specific data:

1. Call `search_catalog` with the user's search terms
2. Present results with context: name, description, space, type, last modified
3. For promising results, call `get_asset_details` to show richer metadata
4. If the user wants to understand the shape of the data, call `get_table_schema` for column details
5. For analytical models, call `get_analytical_metadata` to understand measures and dimensions

Help the user evaluate results: "I found 3 assets matching 'customer revenue.' The most relevant
looks like CUSTOMER_REVENUE_V in the ANALYTICS space — it's a view with 24 columns including revenue
measures by quarter. Want me to show you the full schema?"

### 4. Schema Inspection ("What columns does this table have?")

When the user wants to understand a specific table or view:

1. Call `get_table_schema` (for relational) or `get_analytical_metadata` (for analytical models)
2. Present columns organized by purpose: key columns, measures, dimensions, timestamps
3. Show data types, nullability, and any descriptions
4. Call `get_relational_entity_metadata` for additional OData-level metadata if available

Make the schema meaningful. Instead of just listing columns, identify patterns: "This table has a
composite key (CUSTOMER_ID + FISCAL_YEAR), 6 financial measures (REVENUE, COST, MARGIN...), and
3 geographic dimensions. The LAST_UPDATED timestamp suggests it refreshes regularly."

### 5. Data Profiling ("What does the data actually look like?")

When the user wants to understand data content and quality:

1. Call `analyze_column_distribution` for key columns to understand value ranges, cardinality, and
   null rates
2. Use `smart_query` to pull sample data (limit to 10-20 rows for readability)
3. Use `execute_query` for specific quality checks (null counts, duplicate detection, date ranges)
4. Identify potential data quality issues and flag them

Interpret the results for the user: "The REGION column has 5 distinct values covering EMEA, APAC, and
Americas. The REVENUE column ranges from $1.2K to $4.8M with no nulls — looks clean. But CUSTOMER_EMAIL
has a 23% null rate, which might be worth investigating."

### 6. Lineage and Impact ("Where does this data come from?")

When the user wants to understand data flow:

1. Call `search_repository` with object identifiers to find related objects
2. Use `get_object_definition` to understand transformation logic
3. Trace upstream (sources) and downstream (consumers) relationships
4. Call `get_deployed_objects` to see what's actively deployed

Present lineage as a story: "SALES_SUMMARY_V pulls from two sources: the SAP S/4HANA sales orders
replicated through REPL_FLOW_S4 and the master data from the CUSTOMERS table. It's consumed by
the EXECUTIVE_DASHBOARD analytic model."

### 7. Interactive Query Building ("Show me data where...")

When the user wants to query data:

1. Start with `smart_query` for natural-language-style queries — it handles aggregation intelligently
2. For more complex needs, help the user build SQL and execute with `execute_query`
3. Always start with small result sets (TOP 10/20) before pulling larger datasets
4. For analytical models, use `query_analytical_data` for proper measure aggregation

Guide the user through refinement: "Here are the top 10 customers by revenue this quarter. Want me to
filter by region, add year-over-year comparison, or drill into a specific customer?"

### 8. Marketplace Discovery ("What external data is available?")

When the user wants to find external or shared data:

1. Call `browse_marketplace` to see available data packages
2. Present packages with descriptions, providers, and content summaries
3. Help evaluate relevance to the user's needs

## Handling Common Situations

**User doesn't know where to start**: Begin with the Landscape Overview. Summarize what's there and
let the user's curiosity guide the next steps.

**User gives a vague request** ("show me some data"): Ask one clarifying question about the domain
or topic they care about, then use catalog search. Don't ask too many questions — just get enough
to run a useful search.

**User asks about something that doesn't exist**: Search the catalog first. If nothing matches,
check for similar names or related concepts. Suggest alternatives: "I didn't find a 'profit_margin'
table, but the FINANCIAL_METRICS view has both revenue and cost columns — we could calculate margin
from those."

**Query returns too much data**: Automatically limit results and summarize. Let the user know there's
more: "Showing the first 20 of 1,450 records. Want me to filter or aggregate?"

**Query returns errors**: Read the error message carefully. Common issues include: missing permissions
on a space, referencing columns that don't exist (check schema first), or analytical models needing
specific aggregation patterns. See `references/exploration-workflows.md` for the error resolution guide.

## MCP Tools Reference

For the full list of available tools with parameters and examples, read `references/exploration-workflows.md`.

**Quick reference — tools by workflow:**

| Workflow | Primary Tools |
|----------|--------------|
| Landscape Overview | `list_spaces`, `get_space_info` |
| Space Deep Dive | `get_space_assets`, `search_repository`, `list_repository_objects` |
| Catalog Search | `search_catalog`, `list_catalog_assets`, `get_asset_details`, `get_asset_by_compound_key` |
| Schema Inspection | `get_table_schema`, `get_relational_entity_metadata`, `get_analytical_metadata` |
| Data Profiling | `analyze_column_distribution`, `smart_query`, `execute_query` |
| Lineage & Impact | `search_repository`, `get_object_definition`, `get_deployed_objects` |
| Query Building | `smart_query`, `execute_query`, `query_relational_entity`, `query_analytical_data` |
| Marketplace | `browse_marketplace` |
| Foundation | `test_connection`, `get_current_user`, `get_tenant_info`, `get_available_scopes` |

## Presentation Guidelines

Keep the conversation natural and accessible. The user may not be a Datasphere expert — they might be
a business analyst, a data scientist, or a manager trying to understand what data is available.

- Translate technical metadata into business language when possible
- Summarize before showing raw data
- Suggest logical next steps after each interaction
- Use concrete examples and numbers rather than abstract descriptions
- If showing tabular data, keep it to 5-10 rows unless the user asks for more
- When profiling, focus on the insights (quality issues, patterns, anomalies) not just the numbers

## What's New (2026.05)

- **Filter on Aggregated Measure Values in OData API**: When querying analytic models via OData, you can now filter on aggregated measure values. Example: `?$filter=Partner_ID eq '100000005' and Value gt 1000000`. This is useful when exploring data programmatically or building consumption queries — you can request only rows where measures exceed specific thresholds.

## What's New (2026.10)

- **OData `$metadata` now exposes variables and filter definitions** for relational assets. Request `GET https://<tenant>/api/v1/datasphere/consumption/relational/<space>/<asset>/$metadata` and you can now read the asset's input parameters/variables (name, type, default, multi-value flag) and filter capability annotations directly — no more guessing or scraping the UI. When exploring an asset for a downstream client, prefer this over column-only inspection so you can show the user every dimension they're allowed to filter on. Keep in mind the older path `/api/v1/dwc/consumption/...` is **deprecated** — use `/api/v1/datasphere/consumption/...` everywhere.
- **Natural Language Search in the Catalog**: users can now ask the catalog questions like "show me KPIs about gross margin in EMEA" instead of building filter combinations. When helping a user discover assets, suggest NL phrasing first and fall back to structured `search_catalog` filters only when the NL search misses (e.g., very technical IDs or wildcard patterns).
Files in this package (2)
  • SKILL.md 11 KB
  • references/exploration-workflows.md 9 KB

Versions

The database has no other skills named datasphere-explorer.

Database snapshot: 13.11.2026 · package version 6da61a2f44b1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95sap-datasphere
    SAP Datasphere development skill with 3 specialized agents, 5 slash commands, and validation hooks. Use when building data warehouses on SAP BTP, creating analytic models, configuring data flows and replication flows, setting up connections, managing spaces and users,…
  • 100datasphere-admin
    SAP Datasphere system administration skill for managing spaces, users, roles, security, monitoring, and transport operations. Use when performing administrative tasks including creating/managing spaces, user management, role assignment, system monitoring, capacity planning, or…
  • 100datasphere-connections
    SAP Datasphere connections skill for creating and managing data source connections. Use when configuring connections to SAP systems (S/4HANA, BW, ECC), cloud databases (BigQuery, Redshift, Azure SQL), or other data sources for use in views, data flows, and replication.
  • 90clean-core-data
    Use this skill when the user asks questions about SAP Clean Core Data — including what clean core data is, the five data pillars (data strategy, data governance, data quality, data volume efficiency, data protection), master data management with SAP Master Data Governance, data…
  • 91sap-sac-planning
    SAP Analytics Cloud (SAC) planning guidance for planning models, planning-enabled stories, data actions, multi actions, version management, data locking, calendar/input workflows, allocations, value driver trees, BPC live planning, and Seamless Planning with SAP Datasphere. Use…
  • 100data-lineage-tracker
    Track data lineage tracker operations. Auto-activating skill for Data Pipelines. Triggers on: data lineage tracker, data lineage tracker Part of the Data Pipelines skill category. Use when working with data lineage tracker functionality. Trigger with phrases like "data lineage…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.