scaffold-connector
OpenMetadata Connector Building Skill
When to Activate
When a user asks to build, create, add, or scaffold a new connector, source, or integration for OpenMetadata.
Core Insight
One JSON Schema definition cascades through 6 layers: Python Pydantic models, Java models, UI forms (RJSF auto-render), API validation, test fixtures, and documentation. Define the schema once — everything else is generated or guided.
Workflow: 7 Phases
Phase 0: ENVIRONMENT — Set Up Python Dev Environment
Before any make or python commands, set up the environment from the repo root:
More from open-metadata/openmetadata
playwright-test
Generate robust, zero-flakiness Playwright E2E tests following OpenMetadata patterns. Creates comprehensive test files with proper waits, API validation, multi-role permissions, and complete entity lifecycle management.
60playwright-validation
Use when validating UI changes in a branch require Playwright E2E testing. Reviews branch changes, validates UI with Playwright MCP, and adds missing test cases.
56writing-playwright-tests
Use when writing new Playwright E2E tests or adding test cases. Provides testing philosophy, patterns, and best practices from the Playwright Developer Handbook.
54connector-review
Review an OpenMetadata connector against golden standards. Runs multi-agent analysis covering architecture, code quality, type safety, testing, and performance. When a PR number is given, automatically posts the quality summary to the PR description and a detailed review as a PR comment.
1test-locally
Build and deploy a full local OpenMetadata stack with Docker to test your connector in the UI. Handles code generation, build optimization, health checks, and guided testing.
1connector-standards
Load all OpenMetadata connector development standards into context. Use before building or reviewing connectors to ensure consistent patterns.
1