open-metadata
@open-metadata Organization
Public Skills
openmetadata-pr-review
by open-metadata
Reviews OpenMetadata and Collate pull requests as a maintainer deciding whether to merge. Use WHENEVER the user asks to review a pull request — any phrasing ("review this PR", "PR review", "can you review #1234", "review my PR", a pasted github.com/open-metadata/OpenMetadata/pull/NN URL, or a batch of PR numbers). Default handler for every PR-review request on OpenMetadata (open-metadata/OpenMetadata, a fork, or a Collate repo). Also use when asked whether a PR should go into a release or backport branch, whether two PRs duplicate each other, or why a PR's CI is failing.
playwright-test
by open-metadata
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.
playwright-validation
by open-metadata
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.
writing-playwright-tests
by open-metadata
Redirect only — this skill was merged into playwright. Invoke playwright instead for Playwright E2E authoring guidance and the required lint gate.
openmetadata-workflow
by open-metadata
Meta-skill loaded at session start. Directs Claude to check for applicable OpenMetadata skills before starting any task. Ensures structured workflows are followed.
dev-setup
by open-metadata
Set up, verify, or repair a local OpenMetadata development environment on macOS or Linux. Installs the toolchain (Java 21, Maven, Node 22, Yarn 1.x, Python 3.10+, ANTLR 4.9.2, Docker), creates the Python venv, generates models, installs UI dependencies and pre-commit hooks. Use for a fresh clone, a new worktree, onboarding, or when a build fails with a missing/wrong tool.
vercel-composition-patterns
by open-metadata
React composition patterns that scale. Use when refactoring components with
vercel-react-best-practices
by open-metadata
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
web-design-guidelines
by open-metadata
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
java-checkstyle
by open-metadata
Run mvn spotless:apply to fix Java checkstyle / formatting failures and verify the result. Invoke after authoring or modifying any .java files, or when CI reports a "Java checkstyle failed" or "Fix Java checkstyle" issue on a PR.
ui-checkstyle
by open-metadata
Run the exact ESLint + Prettier + organize-imports sequence that CI's UI Checkstyle workflow runs — on just the files the PR changed — and fail the task if any file ends up with a diff. Invoke after authoring or modifying any .ts, .tsx, .js, .jsx, or .json file under openmetadata-ui/src/main/resources/ui/src/, .../playwright/, or openmetadata-ui-core-components/src/main/resources/ui/src/, or when CI reports a "UI Checkstyle" failure on the PR.
ui-core-components
by open-metadata
Use when writing or editing React/TSX in openmetadata-ui/src/main/resources/ui/src/ or openmetadata-ui-core-components/, before reaching for a raw + Tailwind utility classes to build layout (flex rows/columns, grids, bordered panels with header/body/footer, separators), and before writing any Tailwind color class (tw:bg-, tw:text-, tw:border-*) or hex color value. Applies whenever the change adds or restructures a layout container or touches color/dark-mode styling, not to every div.
code-review
by open-metadata
Use to review code changes with a two-stage process - first checking spec/requirements compliance, then code quality. Works on staged changes, branches, or PRs.
scaffold-connector
by open-metadata
Build a new OpenMetadata connector from scratch — scaffold JSON Schema, Python boilerplate, and AI context using schema-first architecture with code generation across Python, Java, TypeScript, and auto-rendered UI forms.
pr-checklist
by open-metadata
Use when opening or finalizing a GitHub PR for OpenMetadata. Walks through the repo PR template — linked issue, high-level design (for big PRs), unit/integration/Playwright tests + coverage, UI screen recording, and manual test steps — then drafts a fully-filled PR body and (optionally) creates the PR.
planning
by open-metadata
Use when starting a non-trivial feature, refactor, or multi-file change. Forces structured design thinking before writing any code - brainstorm approaches, get approval, then create a step-by-step implementation plan.
tdd
by open-metadata
Use when implementing new features or fixing bugs to enforce test-driven development. Guides the RED-GREEN-REFACTOR cycle for Java (JUnit), Python (pytest), and TypeScript (Jest/Playwright) in OpenMetadata.
verification
by open-metadata
Use before claiming any task is complete. Requires running actual verification commands and showing evidence — no "should work" claims without proof.
connector-audit
by open-metadata
Deep reliability audit for OpenMetadata connectors — runs 7 investigation prompts (metadata, errors, auth, lineage, scale, synthesis, implementation) against connector standards
connector-review
by open-metadata
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.
systematic-debugging
by open-metadata
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
test-enforcement
by open-metadata
Use after implementing any feature or fix to ensure comprehensive test coverage. Enforces 90% line coverage in openmetadata-service, integration tests for all API endpoints in openmetadata-integration-tests, and Playwright E2E tests for UI changes.
test-locally
by open-metadata
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.
connector-standards
by open-metadata
Load all OpenMetadata connector development standards into context. Use before building or reviewing connectors to ensure consistent patterns.
playwright-validation
by open-metadata
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.
writing-playwright-tests
by open-metadata
Use when writing new Playwright E2E tests or adding test cases. Provides testing philosophy, patterns, and best practices from the Playwright Developer Handbook.
playwright-test
by open-metadata
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.