Load OpenMetadata Connector Standards
SkillDev toolsA skill that loads OpenMetadata connector development standards into an AI agent's context before it builds or reviews connectors. It reads local markdown files covering architecture, code style, schemas, testing, performance, and source-type patterns, then confirms what was loaded and summarizes the key points. You can load all standards at once or ask for a specific one such as testing or database.
Then ask your AI: use the Load OpenMetadata Connector Standards skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Have the skill available in your agent environment with its standards markdown files present.
What your AI can do with it
- Load all OpenMetadata connector standards in a fixed order
- Load a single standard such as testing, patterns, schema, lineage, sql, or memory
- Load source-type standards like database, data warehouses, nosql, dashboard, pipeline
- Confirm which standards were loaded and summarize their key points
- Read local markdown files for architecture, code style, schemas, testing, performance
Getting started
- Have the skill available in your agent environment with its standards markdown files present.
- Ask the agent to load standards, or name a specific standard such as testing or database.
- Let the agent read the relevant files and report which standards were loaded.
- Review the summary of key points before starting connector development or review work.
What this skill tells your AI
The instructions your AI receives, as published by open-metadata/openmetadata in skills/connector-standards/SKILL.md and read by Ahel’s review.
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:
${CLAUDE_SKILL_DIR}/standards/main.md— Architecture overview${CLAUDE_SKILL_DIR}/standards/patterns.md— Error handling, logging, pagination${CLAUDE_SKILL_DIR}/standards/code_style.md— Python and JSON Schema conventions${CLAUDE_SKILL_DIR}/standards/schema.md— Connection schema patterns${CLAUDE_SKILL_DIR}/standards/connection.md— Connection class patterns${CLAUDE_SKILL_DIR}/standards/service_spec.md— ServiceSpec registration${CLAUDE_SKILL_DIR}/standards/testing.md— Unit and integration test patterns${CLAUDE_SKILL_DIR}/standards/registration.md— How to register a connector${CLAUDE_SKILL_DIR}/standards/performance.md— Performance best practices${CLAUDE_SKILL_DIR}/standards/memory.md— Memory management and OOM prevention${CLAUDE_SKILL_DIR}/standards/lineage.md— Lineage extraction methods${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
BaseConnectionfor 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)
Signals
- GitHub stars
- 15k
- Forks
- 2k
- Last commit
- Oct 2026
Questions
- What does the skill load when no specific standard is requested?
- It loads all standards in order: main, patterns, code_style, schema, connection, service_spec, testing, registration, performance, memory, lineage, and sql, then reads all source-type standards.
- Can I load just one standard instead of all of them?
- Yes. Name a standard such as testing, patterns, schema, lineage, sql, or memory, or a source type like database, and the skill loads that file.
Advanced
- Item type
- skill
- Key
connector-standards- Source
- github.com/open-metadata/openmetadata
github.com/open-metadata/openmetadata
Related picks
Skill · a5c-ai
The pick for Java110-java-maven-best-practices
Skill · jabrena
The pick for Javadbos-python
Skill · sickn33
The pick for Pythonpython-design-patterns
Skill · wshobson
The pick for Pythonsetup-ts-deep-modules
Skill · mattpocock
The pick for TypeScripttypescript-providers
Skill · composiohq
The pick for TypeScript