What problem does it solve? Building Spark data engineering solutions in Microsoft Fabric requires juggling REST APIs, notebook cell authoring, lakehouse configuration, and job orchestration, with many pitfalls like duplicate job submissions, wrong token audiences, and malformed notebook payloads. ## Core Features & Use Cases - Notebook Code Authoring: Write PySpark, Scala, SparkR, and SQL code for Fabric Notebook cells with correct lakehouse access, notebookutils usage, and Spark session configuration. - Workspace & Lakehouse Management: Create workspaces, lakehouses with schema support, and notebooks through the Fabric control-plane REST API using az rest. - Materialized Lake View Authoring: Design Spark SQL MLVs with incremental refresh readiness, data quality constraints, and medallion layering patterns. - Use Case: A data engineer asks to build a bronze-to-silver pipeline: the skill provisions the lakehouse, authors the notebook cells with Delta Lake MERGE logic, and reviews an MLV for incremental refresh eligibility. ## Quick Start Ask the assistant to create a Fabric lakehouse and write a PySpark notebook that ingests a public dataset into a bronze Delta table.