connector-standards
Load all OpenMetadata connector development standards into context.
Skill by open-metadata
Chalk Labs
Need help deploying connector-standards?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/open-metadata-connector-standards
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documentation, code-review
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/connector-standards
What's inside
- Skill name
connector-standards- Description
- Load all OpenMetadata connector development standards into context. Use before building or reviewing connectors to ensure consistent patterns.
- License
- Apache-2.0
- Instructions
- 67 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- allowed-tools: must be a space-separated string
Files (2)
- SKILL.md
- standards
SKILL.md (first lines)
# Load OpenMetadata Connector Standards
## When to Activate
When a user asks to "load standards", "show connector standards", or before starting any connector development or review work.
## Behavior
### Load All Standards
If no specific standard is requested, load all standards in this order:
1. `${CLAUDE_SKILL_DIR}/standards/main.md` — Architecture overview
2. `${CLAUDE_SKILL_DIR}/standards/patterns.md` — Error handling, logging, pagination
3. `${CLAUDE_SKILL_DIR}/standards/code_style.md` — Python and JSON Schema conventions
4. `${CLAUDE_SKILL_DIR}/standards/schema.md` — Connection schema patterns
5. `${CLAUDE_SKILL_DIR}/standards/connection.md` — Connection class patterns
6. `${CLAUDE_SKILL_DIR}/standards/service_spec.md` — ServiceSpec registration
7. `${CLAUDE_SKILL_DIR}/standards/testing.md` — Unit and integration test patterns
8. `${CLAUDE_SKILL_DIR}/standards/registration.md` — How to register a connector
9. `${CLAUDE_SKILL_DIR}/standards/performance.md` — Performance best practices
10. `${CLAUDE_SKILL_DIR}/standards/memory.md` — Memory management and OOM prevention
11. `${CLAUDE_SKILL_DIR}/standards/lineage.md` — Lineage extraction methods
12. `${CLAUDE_SKILL_DIR}/standards/sql.md` — SQLAlchemy patterns and URL building
Then read all source-type standards:
```
${CLAUDE_SKILL_DIR}/standards/source_types/*.md
```
### Load Specific Standard
If a specific standard or service type is requested:
| Request | File to Load |
|---------|-------------|
| "testing" | `standards/testing.md` |
| "patterns" | `standards/patterns.md` |
| "schema" | `standards/schema.md` |
| "lineage" | `standards/lineage.md` |
| "sql" | `standards/sql.md` |
| "memory" | `standards/memory.md` |
| "database" | `standards/source_types/database.md` |
| "sql databases" | `standards/source_types/sql_databases.md` |
| "data warehouses" | `standards/source_types/data_warehouses.md` |
| "nosql" | `standards/source_types/nosql_databases.md` |
| "dashboard" | `standards/source_types/dashboard.md` |
| "pipeline" | `standards/source_types/pipeline.md` |
| "messaging" | `standards/source_types/messaging.md` |
| "mlmodel" | `standards/source_types/mlmodel.md` |
| "storage" | `standards/source_types/storage.md` |
| "search" | `standards/source_types/search.md` |
| "api" | `standards/source_types/api.md` |
| etc. | `standards/source_types/{name}.md` |
### After Loading
Confirm to the user which standards were loaded and summarize the key points. Example:
> Loaded 12 core standards + 11 source-type standards. Key points:
> - Schema-first: one JSON Schema → Python, Java, TypeScript, UI forms
> - Use `BaseConnection` for SQLAlchemy, `get_connection()`/`test_connection()` for others
> - Use pytest with plain `assert`, no unittest.TestCase
> - Always include copyright header, use `ingestion_logger()`
> - Lineage via query logs (database), SQL parsing (dashboard), or task metadata (pipeline)From open-metadata/OpenMetadata, Apache-2.0.
More from open-metadata/OpenMetadata
- 0.862score
openmetadata-pr-review
open-metadata
Reviews OpenMetadata and Collate pull requests as a maintainer deciding whether to merge.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
pr-checklist
open-metadata
Use when opening or finalizing a GitHub PR for OpenMetadata.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
planning
open-metadata
Use when starting a non-trivial feature, refactor, or multi-file change.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
systematic-debugging
open-metadata
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
java-affected-tests
open-metadata
Use before opening or updating an OpenMetadata PR that changes Java, a JSON schema, an index mapping, a SQL migration, seed data or a pom — PR CI no longer…
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
tdd
open-metadata
Use when implementing new features or fixing bugs to enforce test-driven development.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
playwright-validation
open-metadata
Use when validating UI changes in a branch require Playwright E2E testing.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
openmetadata-workflow
open-metadata
Meta-skill loaded at session start.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
code-review
open-metadata
Use to review code changes with a two-stage process - first checking spec/requirements compliance, then code quality.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
verification
open-metadata
Use before claiming any task is complete.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
ui-pr-recording
open-metadata
Use during PR creation for a UI feature or feature task.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.857score
connector-audit
open-metadata
Deep reliability audit for OpenMetadata connectors — runs 7 investigation prompts (metadata, errors, auth, lineage, scale, synthesis, implementation) against…
SkillAFreshness: A★ 15.6KClaude Code +9
Signals
- Stars
- 15,567
- Forks
- 2,481
- Open issues
- 677
- Contributors
- 519
- Last commit (this folder)
- Mar 9, 2026 (7 months ago)
- Last release
- Oct 21, 2026 (10 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/open-metadata/OpenMetadata
- Website
- open-metadata.org
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from open-metadata
- 0.862score
openmetadata-pr-review
open-metadata
Reviews OpenMetadata and Collate pull requests as a maintainer deciding whether to merge.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
pr-checklist
open-metadata
Use when opening or finalizing a GitHub PR for OpenMetadata.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
systematic-debugging
open-metadata
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
tdd
open-metadata
Use when implementing new features or fixing bugs to enforce test-driven development.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
playwright-validation
open-metadata
Use when validating UI changes in a branch require Playwright E2E testing.
SkillAFreshness: A★ 15.6KClaude Code +9 - 0.860score
planning
open-metadata
Use when starting a non-trivial feature, refactor, or multi-file change.
SkillAFreshness: A★ 15.6KClaude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get connector-standards running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
connector-standards skill. Agent Mart. https://agentmart.dev/skills/open-metadata-connector-standards (last updated 2026-10-24)