What problem does it solve? Extending the WebRobot data platform requires knowledge of two distinct plugin architectures — Scala-based ETL stages loaded via Java ServiceLoader and Java JAX-RS REST API plugins — each with strict conventions for manifests, multi-tenancy, database access, and Spark serialization that are easy to get wrong. ## Core Features & Use Cases - ETL Plugin Development: Implement WTransformStage, WPartitionStage, WSinkStage, and other stage types in Scala with Gradle, including ServiceLoader registration, manifest.json authoring, and LLM-enabled per-row enrichment via WebroStageContext. - REST API Plugin Development: Build JAX-RS resources in Java with Maven, covering multi-tenant organization_id filtering, JDBC access patterns, kernel ORM services, and Flyway migrations. - Stage Catalog Discovery: Query the public stage catalog API before naming new stages to avoid collisions that silently override existing stages. - Use Case: A partner wants to add a sentiment analysis stage to their pipelines. The Skill guides them to implement a WPartitionStage using ctx.llm.infer, register it via ServiceLoader, declare it in manifest.json, and verify no name collision against the live catalog. ## Quick Start Ask the assistant to create a new WebRobot ETL plugin with a transform stage that scores rows, or a REST API plugin exposing endpoints for a new domain.